Privacy Policy

The registered individual operating under the Card Intel trading name is the data controller for personal data handled to operate card-intel.com and app.card-intel.com. Privacy requests can be sent to [email protected]. This notice does not cover Sayframe, separate retail businesses or third-party websites you visit.

Account and sign-in data

Email address, internal account identifier, account and sign-in timestamps, hashed sign-in tokens, session records and any issued API-key hashes. We use these to authenticate access and secure accounts.

Technical and usage data

Request counts, plan and credential identifiers, access times, errors and security information. Network providers and server logs may process your IP address, browser information and requested URL to deliver the service, enforce limits and investigate abuse.

Support correspondence

The email address, message, transaction reference or other details you send when contacting us. Please do not send passwords, full payment-card details or unnecessary sensitive information.

Payment-related records

When paid plans open, Paddle customer, transaction and subscription identifiers, plan, payment status and relevant billing email or event metadata will be associated with your account for fulfilment, reconciliation and support. We do not receive or store your full payment-card number.

Planned collection data

Saved collections, persistent watchlists and alerts are planned workflows, not currently available paid features. If enabled, the holdings and preferences you choose to save will be associated with your account; this notice will be updated if that changes data handling.

If we offer Google or Apple sign-in and you choose it, we use the provider and its stable account identifier to recognise your Card Intel account. We check the verified email returned by the provider for account setup or linking checks. Apple may return an Apple private-relay email address instead of your personal address.

A matching email address does not connect a provider to an existing account. Sign in to that account first, then connect the provider from Account. This protects your saved work and subscription from an unwanted account merge.

We request identity and email access from Google, and email access from Apple. We do not request access to Gmail or Google Drive, collect your provider password, request offline access, or store provider refresh tokens. We use the authorisation code and signed identity token to verify the sign-in; we do not retain those codes or tokens as account records.

Google and Apple handle your provider account under their own notices: Google Privacy Policy and Apple Privacy Policy. Email-link recovery remains available if you cannot use a connected provider; contact support if you cannot access your account.

Where a legal basis is required, account access, fulfilment and requested support rely on performing our agreement with you or taking steps you request before it. Service security, rate limiting, debugging and abuse prevention rely on our legitimate interests in running a secure service, balanced against your rights. Records required by law rely on a legal obligation.

We do not sell personal data or use your private account data to trade against you. Sending a support or early-access email does not subscribe you to a marketing newsletter. If we introduce optional marketing messages, they will have the applicable consent and opt-out controls.

The app uses a first-party __Host-cardintel_auth cookie to recognise a signed-in session. The configured session expires after 30 days of inactivity and can renew while you use the app. Sign-in links expire separately. A temporary cardintel_signup_key cookie is used during the initial credential handoff and cleared afterward. These are functional authentication mechanisms, not advertising cookies.

During optional Google or Apple sign-in, we use a temporary browser-binding cookie to check that the returning sign-in attempt belongs to your browser. We keep hashes of the attempt’s state, browser binding and nonce with expiry and completion timestamps. Expiry prevents further use of the attempt; it does not promise immediate deletion of security records.

We do not install advertising pixels on the Card Intel marketing pages. Hosting and security providers may use technical mechanisms needed to serve and protect the website. Paddle’s own checkout and buyer support have separate data handling described in its notice. You can clear or block cookies in your browser, but signed-in functionality may stop working.

Cloudflare delivers and protects the public website and app connection. Amazon Web Services hosts the static marketing site through S3 and CloudFront. The app and database run on infrastructure managed by the service operator. Google Workspace handles our support mailbox. These providers process information needed for their respective functions, such as requests or messages.

When paid purchases open, Paddle acts as the reseller and merchant of record, and as an independent controller for its checkout, billing, tax and fraud-prevention records. See the Paddle Privacy Notice for its practices and your rights concerning those records.

Access by people administering the service is limited to operational needs. We may disclose information when legally required, to respond to a lawful authority request, or to protect the service and users from fraud or security threats. We do not publish your account email in market-research outputs.

Our international hosting, network and email providers may process information outside your country. Location depends on the provider and service. Contact us for information about processing locations and any applicable transfer safeguards relevant to your data. This notice does not claim that using a global provider alone establishes compliance with data-transfer rules.

Account records are kept while needed to provide the service. Session and token expiry prevents further use; expiry is not a promise of immediate database deletion. Security, usage and support records may be kept longer where needed to investigate incidents, resolve disputes or meet legal duties. Retention depends on those purposes, not a single blanket deadline.

You can request account deletion at [email protected]. We may need to verify that you control the account. We will delete or de-identify records no longer needed, while retaining records required for legal, payment-dispute or security purposes. Residual copies in backups may remain until those backups rotate and are not used as active account records. Paddle controls deletion and retention of its own payment records.

Public market observations and source evidence are separate from private account data. They may contain marketplace-provided information and one-way participant identifiers used for research. They are not a way to publish a subscriber’s private holdings; removing an account does not automatically erase independently sourced market evidence.

Depending on applicable law, you may request access, correction, deletion, a portable copy, restriction of processing, or object to processing based on legitimate interests. You may withdraw consent where processing relies on it, without affecting earlier lawful processing. You can make a complaint to the relevant data-protection authority. We will handle requests within the deadlines required by applicable law.

The service is not directed to children under 13. If you believe a child has provided personal data without the required permission, contact us. Privacy questions, correction requests and security concerns go to [email protected].

We will update the date when this notice changes and provide notice of material changes where required. New optional workflows or providers must be reflected here before they change how personal data is handled. For subscription cancellation and purchase remedies, see our Refund and Cancellation Policy.