Version 1.1Effective September 20, 2026
Cadrin Privacy Policy · Version 1.1 · Effective September 20, 2026
1. Who we are. [Cadrin LLC], Illinois, USA. Contact: hello@getcadrin.com. This policy covers getcadrin.com and app.getcadrin.com.
2. Information we collect. (a) Account: your work email, your company's name, your role on the account and its seat assignments, and — only when you sign in with Google — the basic profile Google supplies with that sign-in, which our database stores and which includes your name, the address of your Google profile picture, the identifier Google uses for your account, and whether Google has confirmed your address; of that profile, only your name is shown anywhere in the Service. Signing up does not ask for your name, and we never see your password: you send it to Supabase Auth, our authentication provider, which stores only a one-way hash of it in our database and verifies it there. Our application code never reads it, and it never appears in our logs. (b) Billing: none. The Service is free at this version, no payment processor is engaged, and we hold no card, invoice or subscription data of any kind. (c) Usage: product analytics inside the app only — never on the marketing site — recording pages visited and interactions with the interface, together with device and browser data, your IP address, and cookies as our Cookie Policy describes. Every input is masked, in interaction capture and in session replay alike. Error and performance diagnostics are a separate collection, and they run on every page — the marketing site included. When something fails, and for a sample of page loads, the error-monitoring provider named in §8 receives the address of the page, your browser and operating system, the technical detail of the fault and page-timing data. We do not send your IP address with those reports, and we do not send the contents of your requests. Your IP address and browser user-agent are also recorded on the row that evidences your acceptance of these documents, and your IP address is used to rate-limit requests. There are no searches to record at this version, because search is not built. (d) Support: if you email hello@getcadrin.com, that message sits in our own mailbox. There is no ticketing system and no support@ address at this version. (e) User content: your company account's name and the email addresses an owner invites. Pipelines, notes, my-book lists and saved searches do not exist at this version. (f) Extension: there is no Cadrin browser extension at this version, so nothing is collected by one.
3. The Cadrin dataset. We hold a dataset of information about employers, benefit plans, insurance carriers, and brokers derived from public government records (U.S. DOL Form 5500 filings). No screen in the Service displays it at this version, and we license no business-contact data from any provider. This information is not collected from you and is processed under our legitimate business purpose of providing market intelligence. Professionals appearing in the dataset may contact hello@getcadrin.com regarding their business-contact information; see §7.
4. How we use information. Provide and secure the Service; send the transactional mail the Service needs, which is an address confirmation, a password reset and an account invitation and nothing else; measure and improve the product; prevent fraud and abuse; comply with law. We process no payments, because the Service takes none. We do not sell your account information and we do not run third-party advertising.
5. Sharing. Only with the subprocessors named in §8, professional advisors, and where required by law or in a business transfer with notice. There is no integration to connect at this version, so nothing is pushed to a third-party service on your instruction.
6. Retention. No automatic deletion runs at this version. What we hold, we hold until a request to hello@getcadrin.com is acted on by hand. Two things do not follow that rule and both are structural: an acceptance record is immutable and is not deleted, because it is the evidence of what you agreed to and when; and an unaccepted invitation expires on its own date and stops working, though its row remains. We hold no billing or tax records, no administrative audit log and no support tickets, because none of them exists yet — the periods that will apply to them appear in the version of this policy that introduces them. Aggregated/de-identified data may be retained.
7. Your rights. From inside the Service you can read your own sign-in address, change your own password, read your account's name and members, and — as an owner — rename the account and revoke an invitation. Everything else is a request handled by hand: there is no self-serve export, no self-serve correction and no self-serve deletion at this version. Send an access, export, correction or deletion request to hello@getcadrin.com; we act on it as quickly as we can and no later than 30 days, subject to §6. California and other applicable states: rights to know, delete, correct, and opt out of sale/sharing — [conditional section: if enrichment "sale" analysis (01 §B5) concludes registration/opt-out duties apply, insert Do-Not-Sell mechanism + data-broker disclosures here]. We do not discriminate for exercising rights.
8. Subprocessors. Engaged today: Supabase (database and authentication, US), Vercel (hosting, US), Resend (email delivery), Upstash (rate limiting), PostHog (product analytics, US cloud), Sentry (error monitoring). Configured but not yet processing anything: Trigger.dev (scheduled job processing), which has no deployment at this version. Not engaged at all: no payment processor, no AI or LLM provider, and no enrichment provider. A change to this list is published as a new version of this policy, and a new subprocessor is published at least 30 days before it begins processing.
9. Security. Traffic is encrypted in transit and data is encrypted at rest by our database and hosting providers. Every query that reads an account's data is scoped to that account in the query itself, and that isolation is exercised by a test suite on every change; the database also carries row-level security policies, which would take effect only for a future, more restricted connection role and are not part of today's separation. Your password reaches Supabase Auth directly from your browser and is stored only as a one-way hash, which our application never reads and never logs. Access to the production database and hosting accounts is limited to the people who operate the Service. There is no administrative audit log at this version. No method is 100% secure; report concerns to hello@getcadrin.com.
10. Children. Not directed to anyone under 18; we do not knowingly collect children's data.
11. International. Operated from and hosted in the United States; by using the Service you consent to US processing. Not directed to the EU/UK.
12. Changes. We publish a change as a new version of this policy, carrying its own version number, effective date and content fingerprint. At this version there is no in-app or email notice mechanism, so the published page is the notice; advance notice of a material change arrives with the version that adds the mechanism for it. Earlier versions are available on request.