Privacy Policy

1. Who we are

• ContextHints Intel is operated by Context Hints Labs Inc.

For counsel: Add the registered address, the privacy contact, any EU/UK representative and the controller/processor roles.

2. Account information

• When you create an account we store your name, email address and a hashed password. Sign-in is handled by our authentication provider, Neon Managed Better Auth, and the records live in our Neon Postgres database.
• To keep you signed in we store session records, which may include the IP address and browser user agent recorded by the authentication provider.
• Verification codes and password-reset links are sent by email and expire after 15 minutes. You must verify your email address before you can use a workspace or accept an invitation.
• We record which version of the Terms and this policy you accepted, and when.
• To protect accounts from abuse we keep short-lived rate-limit counters keyed by a one-way hash of your IP address or email address, never the address itself. They are deleted when their window ends (at most 24 hours).

3. Workspace information

• Workspace name, members, roles and pending invitations.
• Items you save, capture batches you import, and an audit log of administrative actions (for example creating or revoking an ingestion key).
• Ingestion API keys are stored only as hashes. The full key is shown once, when it is created.

4. Ad data

• Captured ads contain advertiser content: advertiser name, ad title and body, display and landing domains, links with tracking parameters removed, and capture details such as engine, surface, country, device class, plan tier and time.
• We do not store the text of the conversation an ad appeared in. An analyst may pick a topic category and add a short note (at most 120 characters) in their own words.
• Ads your workspace captures or imports are private to your workspace: they are not added to the shared library, not shown to other customers and not sent for enrichment. Only workspaces operated by ContextHints contribute to the shared library that every customer sees.
• When you view shared-library records contributed by someone else, capture times are shown to the hour only, analyst notes are hidden and person-like tracking values are masked.
• To classify what an advertiser sells, we may fetch the advertiser's public landing page.

5. Managed ad-account data

• Performance data imported from an ad account your workspace manages is visible only to that workspace. It is never pooled with other workspaces or shown to anyone else.

6. Service providers

• Neon (database and authentication) and Vercel (hosting).
• TypeSafe, whose Jev model classifies shared-library ads. It receives advertiser content only (advertiser name, ad title and body, domains and excerpts of the advertiser's public landing page), never account, workspace or conversation information.
• We do not yet have a zero-data-retention agreement with TypeSafe, so it may retain request data under its own terms.

For counsel: Confirm the full processor list, transfer mechanisms and data processing terms (including zero data retention with TypeSafe).

7. Cookies

• We use strictly necessary cookies to keep you signed in, set through our authentication provider, and a short-lived cookie that remembers which email address is waiting for verification.
• We do not currently use advertising or analytics cookies in this application.

8. Deletion and what we keep

• You can ask us to delete your account. ContextHints staff then remove your sign-in records, sessions, memberships and terms acceptance records, remove your user id from capture and audit records, and delete the context notes you wrote.
• A workspace owner can delete the workspace's private data at any time from Settings. When a workspace itself is deleted, its private observations, managed-account data and samples are purged automatically, normally within a day.
• We keep the audit log of administrative actions (with the link to a deleted workspace or user removed) and capture-batch history, as a record of where data came from. Ads in the shared library stay in the library, without your user id or notes.

9. Takedown requests

• An advertiser can ask us to remove or suppress its ads from the library. We review each request and suppress the advertiser when it is valid.

For counsel: Add the takedown contact address and the response time we commit to.

10. Retention, your rights and security

• You can ask us to access, correct, export or delete your account information.

For counsel: Write retention periods, the rights available by jurisdiction (GDPR, UK GDPR, CCPA/CPRA), how to exercise them, security measures, breach notification and children's data.

11. Changes to this policy

• We will post the effective date and a summary of changes here.

For counsel: Define the notice period and how material changes are communicated.