Privacy Policy
PayDossier — operated by Introgy LLC
Effective date: 8 August 2026 Last updated: 8 August 2026
The short version
PayDossier rates your trading. That means, once you buy a season pass and connect a brokerage account, we hold something genuinely sensitive: a record of what you traded, when, at what size, and what it did to your account. This policy is written on the assumption that you would like to know exactly what happens to that.
The free estimate never leaves your device. The six questions on the landing page are answered by a script running in your browser. Your answers are not sent to us, not stored by us, and not written to your device after you close the tab. If you afterward join the founding-season list, the one-word archetype label the estimator produced goes along with your email address — not your answers.
The founding-season list holds one thing: your email address (plus that archetype label and the date). It is used for one purpose: to tell you once when the founding season opens. We do not sell it, rent it, or run a drip campaign on it. Ask and we delete it.
Brokerage access is read-only, and we never see your broker login. You authorize the connection through SnapTrade, a specialist brokerage-connectivity provider. Your brokerage username, password, and multi-factor codes are never entered with us and never reach us. Through that read-only connection we receive your holdings, balances, and transaction history — which is what the rating is computed from.
We do not sell your trading data. Not to anyone, not ever, not in aggregate, not "anonymized." It is used to compute your rating and for nothing else.
No AI model receives your trading data. The rating engine is ordinary deterministic software with a version number. Nothing about your account is sent to a language model or any generative AI service.
Advertising measurement never touches any of it. We use the Meta Pixel and Conversions API to tell whether an ad led to a visit, a signup, or a purchase. Meta receives browser and ad identifiers, IP address, user agent, page URL, and — for a completed purchase only — a one-way hash of the checkout email. Meta never receives your holdings, your trades, your account values, your rating, your tier, or your estimator answers. You can switch it off at /privacy-choices, and we honor Global Privacy Control.
The honest caveats, stated up front rather than buried:
- Cloudflare, which serves and stores this website, processes your IP address and request metadata as any host must, and holds our database.
- Stripe collects and keeps your email address and payment details when you buy, under its own privacy policy and its own retention obligations. We never see your card number.
- SnapTrade sits between us and your broker and holds the credentials and tokens we deliberately do not.
- Meta receives the limited advertising-measurement signals described above.
- We do not sell personal information for money. Under some US privacy laws, providing those advertising-measurement signals to Meta may count as "sharing" for cross-context behavioral advertising; the opt-out above stops it.
The rest of this document says all of that precisely.
A note on timing. Today the Service is a landing page, a browser-only estimator, and the founding-season list. The paid rating, the brokerage connection, and everything they involve begin when the founding season opens. This policy describes both, and labels which is which, so that nothing about the paid product arrives as a surprise after you have paid for it.
1. Who we are and how to reach us
PayDossier is operated by Introgy LLC, a Delaware limited liability company ("Introgy," "we," "us," "our"). Introgy is the business responsible for the personal information described here — the "controller" or "business," in the language of privacy statutes.
For every privacy matter — questions, requests, complaints, appeals — write to:
That address is monitored by us and is the single contact point for the entire service. We will respond within the time the applicable law requires, and promptly in any event.
This Policy covers paydossier.com and its subdomains, and the emails we send in connection with the service (together, the "Service"). It is incorporated into, and forms part of, our Terms of Use.
2. Who this Service is for
The Service is intended solely for United States residents aged 18 or over, with accounts at United States brokers. It is not directed to children, and it is not offered in or directed to the European Economic Area, the United Kingdom, Switzerland, or any other jurisdiction outside the United States. All processing takes place on infrastructure operated in and by United States providers, and information you submit is processed in the United States.
3. What we collect, and when
3.1 The free estimate — collected by nobody
The six-question estimate on the landing page runs entirely in your browser. The questions, the scoring, and the archetype are all written into the page itself. There is no network request, no server call, and no storage: your answers exist only in the memory of that tab, and they are gone when you close it.
We therefore have no record of what you answered — not an anonymized one, not an aggregated one, none.
The one exception, stated plainly: the sign-up form below the estimate carries a
hidden field holding the archetype label the estimator produced (one of six fixed
strings, for example THE TAPE CHASER). If you choose to join the founding-season list
after running the estimate, that label is submitted with your email address so we can
see what kind of trader is signing up. Your individual answers are not submitted, and
the label is dropped unless it matches one of the six we wrote.
3.2 The founding-season list
If you submit the form, we store:
| Field | What it is |
|---|---|
| Email address | The address you typed, stored as you typed it |
| Archetype label | One of six fixed strings, or nothing if you skipped the estimate |
| Timestamp | When you joined |
The record is filed under a keyed, unreadable hash of your email address so that signing up twice updates one record instead of creating two.
We store the email address itself, unhashed, because we have to be able to send you the launch message. It is used for that and for replying to you. It is not sold, rented, shared, or added to any advertising audience, and it is not sent to Meta.
Retention: we keep it until the founding season opens and the launch message has been sent, or until you ask us to delete it — whichever comes first. There is no automatic expiry on this record, which is why the request route matters: write to support@introgy.ai and it goes.
We also apply a per-connection signup cap. To do that we store a keyed hash derived from your IP address and a small counter, for 24 hours. The IP address itself is not stored in that record and the hash cannot be reversed to it.
The owner of the business gets an alert email when someone signs up. That alert contains the archetype and a running total. It does not contain the email address.
3.3 Your email address at checkout (begins with the paid season)
Payments are processed by Stripe, Inc., which collects your email address as part of
processing the payment and issuing a receipt, and holds it under its own privacy policy.
We read it from the completed checkout session in order to: send your purchase
confirmation and season emails; identify your pass so your rating can be shown to you
across devices; and, unless you have opted out, create a one-way SHA-256 hash used on
the Meta Purchase event. Beyond what is necessary to run your season, we keep the
address only in the form needed to deliver the Service to you.
3.4 Payment information — collected by Stripe, not by us
Card numbers, security codes, billing addresses, and any other payment credentials are collected directly by Stripe and are never transmitted to, seen by, processed by, or stored by us. We receive from Stripe only whether a session was paid, our own opaque reference, the checkout session identifier, the amount, and the email address described above.
We deliberately send Stripe nothing about your trading. No holdings, no trades, no account values, no rating.
3.5 Brokerage data, through SnapTrade (begins when you connect an account)
This is the sensitive part, so it gets the most detail.
How the connection works. Brokerage connections are established and maintained by SnapTrade (Passiv Technologies Inc.), a third-party provider that specializes in read-only brokerage connectivity. You authorize the connection in SnapTrade's flow, at your broker or through SnapTrade, and you accept SnapTrade's own end-user terms as part of it. Your brokerage username, password, and multi-factor codes are entered there, never with us, and never reach our systems. SnapTrade holds the resulting access tokens; we hold an identifier and a secret that lets us ask SnapTrade for your data, and that secret is encrypted at rest.
The access is read-only. It permits reading account, balance, holdings, and transaction data. It does not permit placing, cancelling, or modifying orders; moving, withdrawing, or transferring cash or securities; or changing anything at your broker.
What we receive and store:
| Category | Specifically |
|---|---|
| Connection metadata | Which brokerage institution, connection status, when it was last synced, whether it has broken |
| Account metadata | An account identifier used to distinguish your connected accounts, the account type (for example margin or cash), and its nickname or masked reference where the broker provides one |
| Balances | Cash and total account value, over time |
| Holdings / positions | Symbol, quantity, cost basis, market value, and for options the underlying, contract type, strike, and expiry |
| Transactions / activity | Buys, sells, option opens and closes, dividends, interest, fees, deposits, withdrawals, and transfers — each with its date, quantity, price, and amount, and for options the full contract detail |
| Derived records | Your reconstructed equity curve, weekly rating snapshots, tier, category scores, decomposition, percentile, engine version, and season archives |
What we do not want and do not keep. We do not need, and do not use, your full brokerage account number; where a connection returns one, we keep at most a masked or truncated reference sufficient to tell your accounts apart. We do not collect your name, address, date of birth, Social Security number, or any other identity document from your broker, and we do not ask your broker for them.
How long we keep it. Trading history, derived ratings, and season archives are kept for as long as you have an active or recent season, so that later seasons can be computed against your history and your streak, and so that a returning customer is not starting from zero. If you have not held a pass for 12 months, we delete your brokerage-derived data. You do not have to wait: disconnect and ask us to delete it, and we delete it (section 8).
The free preview is time-boxed. Connecting a brokerage before you buy a season opens a 7-day preview: you get a redacted look at your evidence — trade count, observation window, benchmark — while your rating computes. If you have not purchased a season by the time the preview expires, we delete your SnapTrade user and everything synced from that connection — the same deletion described above, run automatically rather than waited on. Purchasing before the preview expires cancels this automatic deletion; your data then follows the ordinary retention above.
To prevent repeated free previews after that deletion, we retain a keyed, one-way hash of the normalized email address for 12 months. It cannot be reversed into the address, contains no brokerage data, and is used only to decide whether that address has already received a free preview. It expires automatically after 12 months.
Broker limits we do not control. How far back your history reaches, what your broker classifies an event as, whether a given account type reports transactions at all, and whether connecting a different tool breaks our connection are all determined by your broker, not by us. The Terms of Use describe the consequences for the rating.
3.6 Market data — no personal information involved
We fetch end-of-day market prices from Tiingo to build the benchmark and the risk measures. Those requests are for symbols and dates. Nothing about you, your account, your positions, or your identity is sent to the market-data provider.
3.7 Technical information collected automatically
The Service is served by Cloudflare. As a matter of how the internet works, and as part of delivering, securing, and rate-limiting the site, Cloudflare processes:
- your IP address;
- your browser user-agent string and other request headers;
- the URL requested, the response status, and timing;
- coarse network and geographic information derived from the IP address; and
- security signals used for bot mitigation and abuse prevention.
Some of this is retained for a limited period in Cloudflare's platform logs and in our Worker's operational logs, which we use for debugging, security, and abuse prevention. For Meta advertising measurement, the IP address, user agent, Meta browser and click identifiers, and page URL are kept in a short-lived record for no more than 24 hours, so that a completed purchase can be attributed without any trading data being sent to Meta.
Our own application error logs record only an opaque identifier and a scrubbed error code or message. They never contain your trading data, your holdings, your account values, your rating, or your email address. This is an explicit rule in the code.
3.8 Funnel analytics — deliberately anonymous
We record a small number of product events so we can tell whether the product works — for example a page view, a signup, a checkout start, a completed purchase.
Each row contains a timestamp, the event name, and at most two short tags: a
channel tag recording which tagged launch link brought you to the site (for example
a link ending in ?src=reddit), which can only be one of a short fixed list of names
written into the code, never a value your browser or anyone else invents; and an
experiment arm where a presentation test is running. That is all. No IP address.
No device identifier. No session identifier. No user identifier of any kind. No email
address. No trading data, no rating, no dollar value. The rows cannot be tied to a
person or a device, and they are not personal information. The restriction is enforced
by the function's type signature, not by good intentions.
To make those two tags work, we set two first-party cookies: pd_src holds the
channel tag (30 days, so a later purchase still credits the channel that brought you)
and pd_ab holds the experiment arm (30 days, set only while a test is running). Each
contains only one short word from a fixed list — never an identifier — and neither is
sent to anyone but us. You can delete both at any time through your browser's site-data
controls; the site works identically without them.
We also record payment-processor webhook event identifiers so that a repeated delivery cannot cause a duplicate receipt or a duplicate analytics row.
3.9 Browser recognition (begins after email verification)
After you use a one-time email verification link, we set a signed, HttpOnly, Secure, SameSite=Lax session
cookie so the same browser can see your rating without signing in again, plus a
non-identifying flag used only to change a label in the header. Browser JavaScript
cannot read the session cookie. Logging out or clearing site data removes them. We do
not fingerprint your device, and we do not combine IP address, fonts, canvas,
hardware signals, or similar attributes to recreate a cleared session.
3.10 Meta advertising measurement, cookies, and tracking
On paydossier.com, Meta's browser Pixel records a page view and a small number of standard events (for example a content view, a lead when you join the founding-season list, a checkout start, and a purchase). Our server sends matching copies through Meta's Conversions API. A shared random event id lets Meta deduplicate the browser and server copies instead of counting them twice.
Meta may set the first-party _fbp browser identifier and _fbc ad-click identifier
cookies. We forward those values together with IP address, user agent, and the event
page URL. For a purchase, we also send the value and currency, the checkout session id
as the order id, and a SHA-256 hash of the checkout email. We send Meta no email on
earlier events, and on no event do we send trading data, holdings, account values,
ratings, tiers, percentiles, or estimator answers.
The Pixel does not load on development or preview hosts. It does not load when your
browser sends Global Privacy Control, or when the pd_meta_optout cookie records your
choice at /privacy-choices. Opting out also deletes _fbp and
_fbc from our domain. We use no tag manager, session replay tool, heatmap, external
font, or device fingerprinting.
3.11 What we never collect
We do not collect, and the Service has no means of collecting: your brokerage username, password, or multi-factor codes; your bank login; your Social Security or other government identification number; your date of birth; your postal address; your phone number; your precise geolocation; your race, ethnicity, religion, sexual orientation, health or genetic information, biometric data, union membership, or immigration status; the contents of your messages; or your login credentials for anything.
In the language of the California Consumer Privacy Act, we do not collect "sensitive personal information," and so the right to limit its use does not arise. Do not send us any of the above; if you do, we will delete it.
4. Where the information goes and how long it lives
| What we store | Where | Contains | Retention |
|---|---|---|---|
| Founding-season list entry | Cloudflare KV | Email address, archetype label, timestamp, filed under a keyed hash of the email (a separate key domain from account records) | 180 days, enforced by a time-to-live on the record — or sooner, once the launch message is sent or you ask us to delete it |
| Signup rate-limit counter | Cloudflare KV | Keyed hash derived from IP address, and a count; no IP address, no email | 24 hours |
| Meta attribution record | Cloudflare KV | Meta browser and click ids, IP, user agent, page URL, under an opaque reference | 24 hours, then auto-deleted |
| Pass / entitlement record | Cloudflare | Which season you hold, purchase reference, purchase time, amount, currency | Life of the season plus our accounting record |
| Brokerage connection | Cloudflare | SnapTrade user id and encrypted secret, institution, connection status | Until you disconnect or delete; 12 months after your last active season; 7-day preview, auto-deleted at expiry if you have not purchased |
| Trading history and derived ratings | Cloudflare D1 | Transactions, holdings, balances, equity curve, weekly ratings, decomposition, season archives (§3.5) | Until you ask us to delete; 12 months after your last active season; 7-day preview, auto-deleted at expiry if you have not purchased |
| Preview suppression record | Cloudflare D1 | Keyed, non-reversible hash of normalized email; first-preview timestamp; no email or brokerage data | 12 months, then expires |
| Browser session cookies | Your browser | Signed session; non-identifying recognition flag | Until logout, expiry, or you clear site data |
| Channel / experiment cookies | Your browser | pd_src and pd_ab — one short word from a fixed list each; no identifier |
30 days, or until you delete them |
| Meta opt-out cookie | Your browser | pd_meta_optout |
1 year, or until you delete it |
| Funnel events | Cloudflare D1 | Timestamp, event name, channel tag, experiment arm — nothing else (§3.8) | Retained; not personal information |
| Webhook event ids | Cloudflare D1 | Event id, type, status, time | Retained; not personal information |
| Application logs | Cloudflare | Opaque id + scrubbed code; never trading data or email | Cloudflare's log retention period |
| Network / edge logs | Cloudflare | IP, user agent, request metadata | Cloudflare's retention period |
| Brokerage credentials and tokens | SnapTrade | Your broker login and access tokens — held by SnapTrade, not by us | SnapTrade's retention under its own policy |
| Payment records | Stripe | Email, card data, transaction record | Stripe's retention, including legal and tax obligations (commonly ~7 years) |
| Advertising events | Meta | Event, time, URL, event/order id, IP, user agent, _fbp/_fbc; hashed email and value on purchase |
Meta's retention under its Business Tools Terms and privacy policy |
Two consequences worth stating plainly.
Deletion is a request away, and we honor it. Unlike the retention windows, which are generous by design so that your rating history survives between seasons, deletion is immediate on request. Write to support@introgy.ai and we remove your brokerage connection, your synced trading history, and your derived ratings. What we cannot delete is what our payment processor must keep for its own legal and tax obligations, and what your broker and SnapTrade hold under their own policies.
Disconnecting is not deleting. Disconnecting at your broker or in SnapTrade stops future syncing. It does not by itself remove the history we have already synced. Ask us, and it goes.
5. Why we process this information
| Purpose | What it uses |
|---|---|
| Tell you once when the founding season opens | Your email address on the list |
| Understand what kind of trader is signing up | The estimator archetype label |
| Prevent signup spam | Keyed hash derived from IP, and a counter |
| Take payment and prevent double-charging | Stripe session data, opaque reference |
| Send your receipt and season emails | Email address from Stripe, via Resend |
| Connect your brokerage account, read-only | SnapTrade user id and encrypted secret |
| Compute your rating, tier, category scores, and decomposition | Your synced transactions, holdings, balances, and market prices |
| Recompute it weekly and archive each season | The same, plus prior rating snapshots |
| Detect and report a broken connection | Connection status and webhooks from SnapTrade |
| Show you your rating across devices | Session cookie, pass record |
| Deliver, secure, and rate-limit the site | Technical data via Cloudflare |
| Detect and prevent fraud and abuse | Technical data, counters, payment signals |
| Understand whether the product works | Anonymous funnel events |
| Measure and optimize Meta advertising | The Pixel and Conversions API data in §3.10 |
| Handle refunds, disputes, and support | Payment records, opaque ids, your correspondence |
| Comply with law, tax, and accounting obligations | Payment transaction records |
| Debug and fix failures | Scrubbed logs |
We do not send trading, holdings, or rating information for advertising; train machine learning models on your information; sell or license your trading data to anyone; contribute it to any market-data, order-flow, sentiment, or research product; enrich a data broker's dataset; or make any decision about you other than computing the rating you asked for.
Automated processing. The rating, the tier, the category scores, and the decomposition are produced by an automated, deterministic, versioned engine. No AI or language model is involved, and your trading data is never sent to an AI provider. This automated processing is the product itself, not a hidden decision about you: it produces descriptive analytics, and it does not determine your eligibility for anything, does not affect your legal rights, and has no effect outside the documents you receive. No profiling is used to make decisions about you.
6. Who receives your information
We use a small number of service providers, each for one job. We do not sell to them, and each is bound to use the information only to provide the service to us.
| Provider | Role | What it receives | Its policy |
|---|---|---|---|
| Cloudflare, Inc. | Hosting, edge network, key-value storage, database, logs | Everything transiting or stored by the Service, including your synced trading data at rest and your IP address in transit | cloudflare.com/privacypolicy |
| SnapTrade / Passiv Technologies Inc. | Read-only brokerage connectivity | Your brokerage authorization, and the credentials or tokens we deliberately never hold; it relays your account, holdings, and transaction data to us | snaptrade.com — see its privacy policy and end-user terms |
| Stripe, Inc. | Payment processing, receipts, refunds, disputes | Your email address, payment details, transaction records, and an opaque reference. No trading data | stripe.com/privacy |
| Tiingo, Inc. | End-of-day market prices | Symbols and dates. Nothing about you | tiingo.com — see its terms |
| Resend, Inc. | Transactional and launch email delivery | The recipient address and the message | resend.com/legal/privacy-policy |
| Meta Platforms, Inc. | Advertising measurement and optimization | Event, time, URL, event/order id, IP, user agent, _fbp/_fbc; hashed email and purchase value on purchase. No trading data, no rating |
facebook.com/privacy/policy; facebook.com/legal/technology_terms |
No AI provider is on this list, and that is deliberate. The rating path contains no generative model, so no such provider receives your trading data. If we ever introduce a feature that would send anything about you to one, we will name the provider here and say exactly what it receives before that feature ships.
We disclose your information to no one else, except:
- Legal compulsion. Where we are required to by law — a subpoena, court order, warrant, or other lawful process — or where disclosure is necessary to establish or defend legal claims, protect our rights, or prevent imminent harm.
- Business transfer. If Introgy is involved in a merger, acquisition, financing, reorganization, or sale of assets, information may transfer as part of that transaction, subject to this Policy or a successor policy at least as protective. We will post notice in the Service if that happens.
- With your direction. If you ask us to send something somewhere.
We have never sold personal information for money and do not do so, and we will not sell, license, or otherwise commercialize trading data in any form. Disclosure to Meta for advertising measurement may legally be "sharing" for cross-context behavioral advertising. We provide a sitewide opt-out, honor Global Privacy Control, and disclose no trading, holdings, or rating information to Meta. We receive no payment for personal information and do not disclose it to data brokers or run affiliate tracking.
7. Security
We take the security of a record of someone's trading seriously.
- All traffic is served over HTTPS/TLS.
- We never hold your brokerage credentials. There is no broker password in our systems to steal, reuse, or phish, because the credential flow happens at SnapTrade or your broker.
- The brokerage scope we request is read-only. Even a total compromise of our systems could not place a trade or move money in your account.
- The SnapTrade secret that lets us request your data is encrypted at rest and held as a platform secret, never in source code.
- Sign-in is passwordless. Email sign-in codes expire quickly, are single-use, and lock after a small number of wrong attempts.
- Trading data is never written to logs; error logs carry an opaque id and a scrubbed code.
- Access to your rating is granted by signed, time-limited tokens and
HttpOnlysession cookies.
One thing you control: a signed link or an open session is a credential. Anyone holding it can see your rating. Do not forward links, and log out on devices you do not control.
No system is perfectly secure. We cannot warrant that unauthorized access will never occur. If a breach affecting your personal information does occur, we will notify affected individuals and the appropriate authorities as required by applicable state breach-notification law, without unreasonable delay, and we will notify our brokerage-connectivity provider within the period our agreement with it requires.
8. Your choices
- Don't provide it. Every field is voluntary. The estimate needs nothing from you at all; the list needs only an email address.
- Leave the list. Write to support@introgy.ai and you are off it, with the record deleted.
- Use a masked or alias email at checkout if you prefer. The receipt and your season emails will still reach you.
- Disconnect your brokerage account at any time, in the Service, at SnapTrade, or at your broker. Syncing stops immediately.
- Ask us to delete everything. Disconnecting stops the future; deletion removes the past. One email does it.
- Log out or clear site data. This removes browser recognition and our first-party cookies.
- Opt out of Meta measurement at /privacy-choices, or enable Global Privacy Control in a supporting browser. The product and price do not change.
- Do not share the card. The tier card is generated for you and posted only if you post it. It carries no dollar figures by design, but it is yours to keep private.
9. Your privacy rights
Residents of United States states with comprehensive privacy laws — California, Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, Delaware, Iowa, Nebraska, New Hampshire, New Jersey, Minnesota, Maryland, Tennessee, Indiana, Kentucky, Rhode Island and others as their laws come into force — have the rights described below. We extend all of these rights to every user of the Service, regardless of where you live. It is simpler, and it is right.
9.1 The rights.
- Know / access. Ask what personal information we have collected about you, the categories, the sources, the purposes, the categories of recipients, and the specific pieces we hold.
- Delete. Ask us to delete personal information we hold about you, including your synced trading history and derived ratings.
- Correct. Ask us to correct inaccurate personal information. Note that trading data comes from your broker: where the source record is wrong, the correction has to start there, and we will re-sync.
- Portability. Receive a copy in a portable, machine-readable format where technically feasible.
- Opt out of sale or sharing. We do not sell personal information. You may opt out of Meta advertising measurement and any legally defined "sharing" at /privacy-choices.
- Opt out of targeted advertising. The same control stops Pixel and Conversions API events.
- Opt out of profiling producing legal or similarly significant effects. We conduct none: the rating has no effect on your eligibility for anything.
- Limit use of sensitive personal information. We collect none.
- Non-discrimination / non-retaliation. We will never deny you service, charge you a different price, or give you a lesser product because you exercised a privacy right. We offer no financial incentives for personal information.
- Appeal. If we decline a request, you may appeal (section 9.5).
9.2 How to exercise them. Email support@introgy.ai stating what you want. We will acknowledge promptly and respond within 45 days, extendable once by a further 45 days where the law allows and we tell you why. There is no charge, unless a request is manifestly unfounded or excessive, in which case we will tell you before doing anything.
9.3 Verifying you. Trading history is exactly the sort of thing we should not hand to a stranger. Write from the email address associated with your pass, or from the address you gave the founding-season list, and we can locate your record. Where a request would disclose the contents of your trading data, we may additionally ask you to complete a one-time email sign-in, which proves control of that address. We will not ask you for identity documents — collecting more information about you in order to answer a privacy request would defeat the point.
Where we cannot verify a request, we will explain why and treat the request as a request to opt out where that distinction matters, as the law requires.
9.4 Authorized agents. An authorized agent may submit a request on your behalf with written proof of authorization; we may contact you to confirm the authorization directly. In California, a valid power of attorney may be used instead.
9.5 Appeals. If we refuse a request in whole or in part, you may appeal by replying to our decision with the word "Appeal." A different person at Introgy will review it, and we will respond in writing within 45 days (or the shorter period your state's law requires) explaining the outcome and, if we still decline, how to contact your state Attorney General.
9.6 Complaints. You may complain to your state Attorney General at any time. California residents may also contact the California Privacy Protection Agency. We would rather you told us first — support@introgy.ai — but that is your choice, not a precondition.
10. California notice at collection
Provided under the California Consumer Privacy Act as amended by the CPRA. It restates what is above in the statute's categories.
| CCPA category | Do we collect it? | What, specifically | Source | Purpose | Disclosed to | Sold or shared? | Retention |
|---|---|---|---|---|---|---|---|
| A. Identifiers | Limited | Email address (list, and at checkout via Stripe); IP address; _fbp/_fbc; signed browser session; brokerage connection and account identifiers |
You; your device; Stripe; SnapTrade | Launch notice; receipts; access; delivery and security; ad attribution | Cloudflare, Stripe, Resend, SnapTrade, Meta | Shared with Meta unless opted out; never sold | See §4 |
| B. Cal. Civ. Code § 1798.80 customer records | Yes | Financial information: account balances, holdings, transaction history, payment via Stripe | Your broker via SnapTrade; you; Stripe | Compute your rating; take payment | Cloudflare, SnapTrade, Stripe | No | Until deletion; 12 months after last season |
| C. Protected classifications | No | — | — | — | — | No | — |
| D. Commercial information | Yes | That a purchase occurred; season, value, currency; refunds | You; Stripe | Fulfil and support the purchase; ad attribution | Stripe, Cloudflare, Meta | Purchase shared with Meta unless opted out; not sold | See §4 |
| E. Biometric information | No | — | — | — | — | No | — |
| F. Internet or network activity | Yes | Request metadata, Pixel events, _fbp/_fbc, page URL; first-party pd_src/pd_ab/pd_meta_optout cookies |
Your device | Delivery, security, advertising measurement, channel measurement, your opt-out choice | Cloudflare, Meta (our own cookies go only to us) | Pixel data shared with Meta unless opted out; not sold. Our own cookies neither sold nor shared | Meta record 24 hours; cookies 30 days–1 year; providers' retention |
| G. Geolocation | Coarse only | Coarse region derived from IP | Your device | Security and delivery | Cloudflare | No | Providers' retention |
| H. Audio, video, sensory | No | — | — | — | — | No | — |
| I. Professional or employment information | No | — | — | — | — | No | — |
| J. Education information | No | — | — | — | — | No | — |
| K. Inferences | Yes | The estimator archetype label if you submit it with the list form; your rating, tier, category scores, decomposition, and percentile | Derived by us | Understand signups; the product itself | Cloudflare | No | See §4 |
| L. Sensitive personal information | No | — | — | — | — | No | — |
We have not sold personal information in the preceding twelve months. We disclose the categories identified above to Meta for advertising measurement; privacy laws may define that disclosure as "sharing." We have not knowingly sold or shared the personal information of anyone under 16 — the Service is 18-and-over.
11. Universal opt-out signals and Do Not Track
We honor the Global Privacy Control (Sec-GPC: 1 / browser GPC signal) as an opt-out
of Meta Pixel and Conversions API measurement. You can make the same choice at
/privacy-choices; we keep it in the first-party pd_meta_optout
cookie for one year and delete Meta's _fbp and _fbc cookies from our domain. There is
no industry standard for the older "Do Not Track" header; use GPC or our site control for
an enforceable choice.
12. Children
The Service is for adults aged 18 and over. It is not directed to children, we do not knowingly collect information from anyone under 18, and we do not knowingly sell or share the personal information of minors under 16 (we sell or share no one's). If you believe a person under 18 has provided us information, write to support@introgy.ai and we will delete it.
13. Visitors from outside the United States
The Service is offered only in the United States, and all information is processed in the United States by United States providers. We do not target, offer the Service to, or monitor the behavior of individuals in the European Economic Area, the United Kingdom, or Switzerland. If you access the Service from outside the United States, you do so on your own initiative and you understand that your information will be processed in the United States under United States law, which may not provide the same protections as your own.
14. Changes to this Policy
We may update this Policy. When we do, we will change the "Last updated" date at the top and post the new version here. Material changes take effect no earlier than the date posted and apply prospectively. Where the law requires it, we will seek your consent or give you advance notice. Where a change materially affects how we handle brokerage or trading data, we will notify pass holders by email rather than relying on you to check this page. Your continued use of the Service after a change takes effect signifies acceptance of the updated Policy.
A note on the previous version. Until 8 August 2026 this policy described a compensation-benchmarking product that was offered at this domain and is now discontinued. Records created under that product expired automatically under the retention windows published at the time.
15. Contact
Introgy LLC Privacy requests, appeals, questions, and complaints: support@introgy.ai
Please put "Privacy" in the subject line so it reaches the right place quickly.
PayDossier is analytics about your past trading, not investment advice or a recommendation. Brokerage access is read-only. We do not sell your trading data.