Last updated: October 31, 2026. This policy explains how VCorp, operating DepthFeed, handles personal information when you use our website, account, API, applications, support, or billing. It does not govern market data about public markets or public blockchain activity that is part of the product.
Information we collect
- Account and contact details, such as your email address, account ID, authentication records, organization details you provide, and support correspondence.
- Service and API usage, including request time, endpoint, status, response size, duration, request ID, IP and security signals, plan, and a hash of an API key. Raw API keys are shown when created and are not stored in plaintext.
- Product inputs you submit to analysis, paper-trading, wallet, webhook, or support features, and the output needed to provide those features.
- Website and device information, such as pages viewed, referral source, approximate location derived from IP, browser/device type, and aggregate interaction data.
- Subscription records, such as plan, amount, dates, payment status, and the customer, subscription, invoice, or payment references supplied by our payment processor.
How we use information
We use information to authenticate accounts; provide and secure the service; meter usage and enforce plan controls; process subscriptions; detect fraud, scraping, and credential abuse; troubleshoot and improve performance; answer support requests; send transactional and legally required notices; and comply with law. We may use aggregated or de-identified information for analytics and service planning.
Payments
Stripe handles checkout and payment information for subscriptions sold by DepthFeed. Stripe's own privacy terms govern the information it collects. We receive transaction and subscription references needed to activate and manage access, but we do not receive or store your full card number.
How we share information
We do not sell personal information. We share it only with service providers needed to run DepthFeed, such as hosting, infrastructure, authentication, email, analytics, error monitoring, support, and payment providers; with professional advisers where necessary; in a corporate transaction; or when required to comply with law, protect rights and safety, or investigate abuse. Providers may process information in countries other than yours.
Cookies and similar technologies
This section is our cookie policy. It covers depthfeed.com, polymarketbacktesting.com, kalshibacktesting.com, and the sign-in pages on polymarketpricedata.com and kalshipricedata.com. Each of these hosts keeps its own choice. We use browser storage (localStorage and sessionStorage) in the same way as cookies, so both are listed.
Strictly necessary items and items you set yourself are always available. Analytics and marketing attribution are off until you opt in, you can change your mind at any time, and rejecting them does not limit the site. We keep your choice for 180 days, then ask again. We also ask again if this policy changes in a way that needs a new answer.
If your browser sends a Global Privacy Control signal, we treat it as a refusal of analytics and marketing attribution, do not show the banner, and keep both off. We do not sell personal information or share it for cross-context behavioral advertising, and we do not use advertising cookies or third-party trackers on these sites.
Strictly necessary
- depthfeed_consent (cookie, 180 days): your cookie choice, its policy version, and its date.
- __Host-depthfeed-access, __Host-depthfeed-refresh, df_access, df_refresh (cookies, for your sign-in session): keep you signed in.
- __Host-depthfeed-central-flow, __Host-depthfeed-signal-room-oauth (cookies, up to 10 minutes): protect a sign-in while it is in progress.
- df_bulk_return (cookie, short-lived): returns you to a bulk data checkout after sign-in.
- Cloudflare security cookies, such as __cf_bm and cf_clearance, may be set on depthfeed.com when Cloudflare checks traffic for bots or abuse (up to about 30 minutes for __cf_bm).
Set by your own actions
- NEXT_LOCALE (cookie, 1 year): the language you pick.
- df-auth-remember (localStorage): your email and sign-in method, only if you ask us to remember them.
- Tool settings and drafts (localStorage and sessionStorage, keys beginning df., df_, df:, depthfeed. or depthfeed:): for example terminal layout, favourites, strategy drafts, saved scripts, and dismissed promotions. These stay in your browser and are used only to run the feature you are using.
Analytics (optional)
- depthfeed:anonymous-id:v1 (localStorage, until removed): a random visitor ID.
- depthfeed:session-id:v1 (sessionStorage, until the tab closes): a random visit ID.
- depthfeed:landing:*, depthfeed:pricing-viewed:* (sessionStorage, until the tab closes): stop the same event being counted twice.
With these on, your browser sends us the pages you view and the buttons you use. This goes to our own servers only, not to a third-party analytics provider, and is linked to your account if you are signed in.
Marketing attribution (optional, needs analytics)
- depthfeed:first-touch:v1 (localStorage, until removed): the page, referring site, and campaign tags of your first visit.
- depthfeed:session-touch:v1 (sessionStorage, until the tab closes): the same details for this visit.
When you reject or withdraw consent, we delete these analytics and attribution items from your browser straight away. Events already received are kept under the retention terms below.
Retention and security
We retain account and subscription records while an account is active and afterward as needed for billing, tax, fraud prevention, disputes, and legal obligations. Detailed API usage is ordinarily retained for up to 180 days, though security events, aggregate records, invoices, and records required by law may be kept longer. Support messages and user-created product objects are kept until no longer operationally necessary or until valid deletion, subject to backups and legal obligations.
We use administrative and technical safeguards appropriate to the service, but no online system is completely secure. You are responsible for protecting your credentials and for promptly reporting suspected compromise.
Your choices and rights
You can manage subscription and account settings through the dashboard. Depending on where you live, you may have rights to access, correct, delete, restrict, or object to processing, or to receive a portable copy of certain information. You may also have the right to complain to a data-protection authority. We may verify your identity before acting on a request, and legal exceptions may apply.
Contact and changes
Email [email protected] to make a privacy request or ask a question. We may update this policy as the service or law changes; the date above shows the latest revision, and we will provide additional notice when required.
