Legal
Privacy Policy
Effective October 10, 2026. CaliRecord is operated by Jason Chen, in California.
Questions: jason@calirecord.com
What CaliRecord does
CaliRecord holds a copy of the California Secretary of State business register and gives you three ways to use it.
Lists. You bring a farm sheet, the spreadsheet of properties you already work, whose owners are business names. We match those names to filings, follow businesses named in other businesses' filings, and return the people named there with their filed role and the evidence. Uncertain cases are flagged, not guessed.
Search. Look up any California business by name or file number and read its filings, its status and the people named in them.
Directory. Walk the chain around a business as an org chart: the entities named in its filings, the entities that name it, and the people at each step.
Search and Directory read only the public register. Nothing from your farm sheet is involved in either, and nothing you look up is recorded against you.
Google data we access
What. There is no sign-in, so we receive no Google account data unless you connect Google Drive. If you do: the single spreadsheet you pick in Google's own file picker, one file at a time.
How we use it. A sheet you pick from Drive is read once per run, and the result is written back to your Drive as a new file named after the original with "- enriched" on the end. We never modify the file we read.
Who we share it with. Nobody. The Google Drive connection is made directly between you, Google and CaliRecord. Our hosting and network providers carry traffic but receive no Google account data for their own purposes. There is no advertising or tracking code on this site or in the application. To count visits we use Vercel Web Analytics, a page-view counter run by our hosting provider: it records which pages are viewed and where the visit came from, does not identify you or follow you to other sites, and receives no Google account data.
Retention. If you connect Google Drive, we keep one thing: a Google refresh token for your account. It is encrypted in our database, and the key that decrypts it is held separately in the server's configuration, never in the database beside it and never in our code. We use it for exactly one purpose, to obtain short-lived access tokens of about an hour each, which are held in memory and never written down. That is what lets us read a sheet you picked and write the enriched one back without asking you to approve Google again every hour. Neither token is ever written to a log.
Turning it off. Settings, then the Google Drive switch. We revoke the connection with Google and delete what we hold, and you can also revoke it yourself at any time from your Google account's security page. If we ever cannot reach Google to revoke it, we say so rather than reporting success.
The Google Drive permission we ask for. If you choose to connect Google Drive, we request a single Google permission, drive.file. It reaches only the files you pick in Google's file picker and the files we create for you. It cannot see anything else in your Google Drive. We deliberately do not request Google's read-everything Drive permission. We ask for this permission only when you connect Google Drive, so someone who never uses Drive is never asked for it. The connection then stays until you switch it off, which is the point of it: the alternative is asking you to approve Google again every hour. If we ever need a different kind of data we will update this policy and ask your consent first.
We do not keep your file
An uploaded spreadsheet is read, enriched, and returned to your browser. It is never written to our disk. A Drive sheet is read from your Drive and the result written back to your Drive. Either way the only copy of the file is yours.
We do keep what was in it
The rows are stored in our database. For each property that is the parcel number, the property address, the owner name exactly as your sheet printed it, and the owner's mailing address. We say so plainly, because "we do not keep your spreadsheet" would be a word game if the rows lived on.
Four reasons, and they are the whole list.
- To match business names to filings. A name resolved once is resolved faster and more accurately afterwards, and the names that find no match tell us where our matching or our coverage is weak.
- To tell apart two businesses with the same name. When the address on a filing matches the mailing address on your sheet, that is evidence about which of several identically named businesses is the one you have. Without it we would be guessing between namesakes, and we would rather not guess.
- To reopen a past run without asking you to upload the sheet again.
- To show which properties a person is connected to, across your own sheets.
Your rows stay yours. A search that returns properties is scoped to the sheets you analysed, which we tell apart by a random identifier your browser creates. Another customer's search never reaches your rows, and yours never reaches theirs.
What we also keep
- A random identifier your browser creates, so we know which sheets are yours. It is not linked to your name or email.
- For a Drive sheet, its Google file ID, so you can reopen a past run without picking the file again.
Matched business names are shared. Once a business name is resolved to a filing, that result serves every customer who has the same name on their sheet. These are public company records, not information about you. It is the one thing that crosses between customers, and it crosses as a company record, never as a row from your sheet.
Anything you type into Send feedback, the email you give if you want an answer, and your browser's random identifier.
People named in filings
We report individuals whose names appear in public business filings, with the role the filing states. A filed role is not a claim of ownership or control.
We add no phone numbers and no email addresses, we do not skip trace, and we do not try to identify anyone not named in a filing. If you are named in a filing we report, email jason@calirecord.com. We cannot change the underlying public record, which is held by the State of California.
The California register
We hold a copy of California Secretary of State business filing data, refreshed weekly. It is public record published by the State. We did not collect it from the people named in it.
Anyone can search the register without an account, including the names of the people in a company’s filings, as the Secretary of State publishes them.
Cookies
No advertising or tracking cookies. Small interface preferences are stored in your browser, and a random identifier that keeps your sheets yours and tells a return visit from a first one.
Deletion and changes
Ask us to delete anything we hold from your sheets and we will, within 30 days. If we change this policy we will update the date above, and if a change means accessing a new kind of data from your Google account, we will ask your consent first.