basis1privacy
Privacy Policy
What we collect when you use basis1, why we collect it, where it lives, how long we keep it, and how to get it deleted.
The short version
- Your workbooks are yours. We store them to run the service and never use them to train AI models.
- A workbook you open in the spreadsheet while signed out is processed in your browser and isn’t uploaded to us.
- Workbooks sent to the parsing API are processed in memory and aren’t written to disk, apart from editing sessions, which are kept for at most about a day.
- We use PostHog for product analytics. It never sees your cell contents, and we hash file and sheet names before they reach it.
- We don’t sell your personal information or use it for advertising.
- We may send you occasional product emails. You can turn them off in Settings or with the unsubscribe link in any of them, and our analytics provider never gets your email address.
- You can delete your account yourself from Settings. That deletes your files, API keys and sign-in details.
Who we are
basis1 (“Basis”, “we”, “us”) is operated by Onigiri Capital, LLC, 2211 Michelson Dr., Irvine, CA 92612. This policy covers the website and spreadsheet at basis1.tech (the spreadsheet is at basis1.tech/app), the parsing API and its documentation at api.basis1.tech (including the hosted MCP endpoint), and the basis1 SDK and MCP packages when they talk to that API.
For privacy questions or requests, email basis@onigiricapital.com. Security reports go to security@onigiricapital.com.
What we collect and why
Your account
- Email address and, if you give one, your name. To identify your account, sign you in, and show who owns or commented on a shared file.
- Your password, as a one-way hash. We store a salted scrypt hash, never the password itself.
- If you sign in with Google: we ask Google only for the basic
openid email profilescopes. Google tells us your Google account ID, email address, whether that email is verified, and your name. We use the access token once to read those details and don’t keep it. We don’t get access to your Google Drive, Gmail, contacts or anything else. - Sign-in sessions. When you sign in we give your browser a random session token in a cookie and store only a hash of it, with the time it was created, when it expires, and roughly when it was last used. We don’t store your IP address or device with the session.
Emails we send
- Account emails, such as the link that confirms your email address. We send these because the service needs them, and they aren’t affected by your email preferences.
- Product emails, such as tips for getting started. If you created your account on or after November 7, 2026, these are on unless you turn them off; we tell you this when you sign up. Accounts created before then don’t get them unless you turn them on. We send them only to a confirmed email address, and never more than two in any 24 hours.
- Turning them off: use the setting in Settings or the unsubscribe link in any product email, which works without signing in. We stop straight away.
- What we keep: whether product emails are on for your account, when you turned them on or off, and a record of each product email we sent you (which one, when, and whether it was delivered to our email provider), so we don’t send the same one twice or too many.
- How the timing is decided: product emails are timed from activity in your account, not from analytics: when you confirmed your email, whether you’ve run an audit or saved a file to your Library, and whether you’ve created an API key (for example, a tip about the audit a few days after signing up if you haven’t tried it yet). To know whether you’ve run an audit, we record the time of your first one while you’re signed in; nothing from the workbook goes with it. Your analytics settings, including Do Not Track and Global Privacy Control, don’t change which of these emails you get.
Your files and collaboration
- Workbooks you save to your Library: the file contents of every version you save (including the original file you imported), the file name, folder names, version messages, whether you starred it, and when it was created, changed, opened, or moved to the trash. We keep this to store, open, version and share your work.
- Files you open stay on your device, even when you’re signed in. A file is added to your Library only when you choose Save to Library, and then we keep it, along with its version history, until you delete it. The spreadsheet engine runs on your device. The built-in formula audit also runs in your browser by default. If you switch the audit to the hosted API, the workbook is sent to our parsing API and handled as described under “Parsing API” below.
- Sharing. When you share a file we store the email address you shared it with, the role you gave (viewer, commenter or editor), who shared it, and when the invite was accepted. We don’t send email on your behalf; you pass the invite link on yourself.
- Comments. The text, the cell it’s attached to, the author, and timestamps. Comments live only in basis1 and are never written into the .xlsx files you download.
Parsing API, MCP and API keys
- API keys. For each key: an ID, a hash of the secret (never the secret itself), the name you gave it, its permissions and limits, the account it belongs to, and when it was created, last used and revoked.
- Connected apps. If you connect an app such as Claude to Basis by signing in (instead of pasting an API key), we keep a record of that connection: which account and app, the app’s name and the addresses it registered, when you connected it and when it was last used, and when it was disconnected. The app gets an access token that lasts an hour and a refresh token that lasts 30 days; we store only a hash of each, never the tokens themselves. Usage by all your connected apps is counted together, like one API key. You can see and disconnect your apps in Settings.
- Usage counts. Per key and per day or month: the number of requests, bytes received and cells returned. We use these to enforce limits and understand usage.
- Workbooks you send to the API are parsed in memory and not written to disk. Results of background jobs are held in memory for up to 15 minutes so you can fetch them, then discarded.
- Editing sessions (MCP). A session holds a copy of your workbook in memory while you work on it. So a session survives a server restart, we also save a copy (the workbook plus session details) to a private Google Cloud Storage bucket. See retention below. If you ask a session to save to your Library, that copy becomes a Library file.
- URLs and webhooks. If you give us a URL to fetch a workbook from, our server downloads it from that address. If you give us a webhook URL, we send it the job ID, its status, the number of records produced and any error message. Our logs may record the web address we fetched, without its query string.
Product analytics
We use PostHog to understand which features people use and where things break. It loads on the pages of basis1.tech, including the spreadsheet (basis1.tech/app) and this page, and on the API home and documentation pages at api.basis1.tech. It doesn’t load on invite links, whose address contains a private token. In your browser, events go to r.basis1.tech, an address on our domain that PostHog operates and that passes them on to PostHog.
- In the spreadsheet: page views, and named events for the actions you take (for example “opened a file”, “created a version”, “ran the audit”) with counts, sizes and timings. File, sheet and branch names are hashed before they’re sent. Cell contents, formulas and file contents are never sent. Click tracking (“autocapture”) and session recording are off.
- On the API home and docs pages: page views only. Click tracking and session recording are off.
- No cookies or stored identifiers before you sign in. While you’re signed out, analytics keeps nothing on your device, so each page load looks like a new visitor, and no profile is created for you. Once you sign in, we store an analytics identifier in your browser so your activity stays together between visits, and we remove it when you sign out.
- We don’t send your IP address with these events and we don’t send your email address or name. PostHog is set to discard the IP address of the connection. Before discarding it, PostHog uses it to estimate an approximate location (country, region and city), which is kept with the event. Events recorded before November 4, 2026 may also contain the IP address itself; they are deleted on the schedule below.
- Once you sign in, your analytics profile is linked only to your account ID, not to your email address. If we need to look up an account for support, we do that in our own records.
- From our servers: when you create an account or an API key, we record that it happened, with your account ID and how you signed up (password or Google).
- Your choice: if your browser sends Do Not Track or Global Privacy Control, we don’t track your activity. When you create an account or an API key, we only count that it happened, without linking the count to you or your account.
- From the API: events such as “workbook parsed”, tied to the account that owns the API key, with the key ID, sizes, counts, timings and error codes. When an AI assistant uses Basis through our MCP server, we also record which tool it called and whether the call worked, the name and version the assistant’s app reports for itself, its user agent and similar details the app sends about itself, and how long the call took. Before you sign in, these events are tied to a random session ID instead of an account. Never the workbook contents, what was sent to a tool or what it returned.
- When you ask for higher limits: we store the email address, project description and expected volume from that form in our database, with the API key you picked (if any), the page you sent it from, and, if you were signed in, your account. If you’re signed in we reply to your account’s email address. We also email the request (your address, description and volume) to our own inbox through Resend so we can reply to you. When we decide, we email our decision to you through Resend and keep a record of it with the request: whether we approved or declined it, the limits we set (if any) and any note we wrote to you. PostHog only gets a count that a request was sent, with the page and whether you were signed in (tied to your account if you were), never your email or description. This happens because you sent the form, so it isn’t affected by Do Not Track or Global Privacy Control.
- PostHog also records the standard details its library collects, such as browser, operating system, screen size, referring page and the page address.
Logs and abuse prevention
- Our hosting providers keep standard request logs, including your IP address, browser user agent, the address requested, the response status and timing.
- Our own application logs record what happened to a request (route, outcome, sizes, timings, job and key IDs, error messages). They don’t include your IP address or workbook contents.
- To enforce rate limits on the parsing API we keep a per-IP and per-key counter in memory for a few minutes. To limit sign-up, sign-in and API key creation attempts we store counters keyed by a keyed one-way hash of your IP address (and, for sign-in, the email address entered), never the address itself, and delete them within a day. Our network edge may block an IP address for 10 minutes if it sends too many requests.
What we don’t do
- We don’t train machine-learning or AI models on your workbooks, and we don’t send them to AI providers.
- We don’t sell your personal information, and we don’t use it for advertising or share it for cross-site tracking.
- We don’t use advertising cookies or third-party trackers.
Where your data is stored
Account data, file details, comments and requests for higher limits are stored in a Google Cloud SQL (PostgreSQL) database, and file contents in a private Google Cloud Storage bucket, both in Google Cloud’s us-east1 region in the United States. The parsing API runs on Google Cloud Run in the same region. The website and spreadsheet are served by Vercel. PostHog stores analytics in its US region.
Connections to the database are encrypted and require a client certificate. The file bucket blocks public access, and your browser uploads and downloads files through short-lived signed links.
If you are outside the United States, your data is transferred to and processed in the United States.
How long we keep it
| Data | Kept for |
|---|---|
| Account (email, name, password hash, Google ID) | Until your account is deleted. |
| Sign-in sessions | 30 days, or until you sign out. |
| Library files and all their versions | Until you delete them. Moving a file to the trash doesn’t delete it; “Delete forever” does. |
| Shares and comments on a file | Until you remove them or the file is deleted. Deleting a comment erases its text right away. If you delete your account, comments you left on other people’s files stay, shown as written by “Deleted user” without your name or email. |
| Workbooks sent to the parsing API | Only while the request is processed, in memory. |
| Background job results | Up to 15 minutes, in memory. |
| MCP editing sessions | In memory until 30 minutes after your last activity. The saved copy is deleted when the session expires, and any copy left behind is removed automatically once it’s a day old (Google may take up to another day to carry this out). |
| Requests for higher limits | Until we’ve decided on the request, then for one more year, after which a nightly cleanup deletes it. Deleting your account deletes the requests you sent while signed in, and any you sent signed out from the same email address once you’ve confirmed it. Copies of past requests that went to PostHog before we stopped sending them there are kept like other analytics events. The email we send ourselves about a request stays in our inbox. |
| API keys and usage counts | Until your account is deleted. Revoking a key disables it but keeps its record and usage history. |
| Connected apps and their tokens | Until you disconnect the app or delete your account. Expired tokens are deleted within a day of expiring, and a disconnected app’s record 30 days after you disconnect it. Deleting your account disconnects every app at once. |
| Request logs | 30 days in Google Cloud Logging, and for Vercel’s standard log period for the website. |
| Email preferences and the record of product emails sent | Until your account is deleted. |
| Analytics events (including MCP usage events) | 1 year, or until we delete them at your request. |
| File contents left without a file | If a save or a deletion stops partway, any file contents left in storage without a file pointing at them are removed by a nightly cleanup once they’re a day old. |
| Backups | Deleted data can remain in database backups and the storage provider’s recovery copies for up to about 7 days. |
Who processes data for us
We use these service providers. Each processes data only to provide its service to us.
| Provider | What it does for us |
|---|---|
| Google Cloud (Cloud Run, Cloud SQL, Cloud Storage, Secret Manager, Cloud Logging, load balancing) | Runs the parsing API, stores your account, files and API keys, keeps our credentials, and holds request logs. United States (us-east1). |
| Vercel | Hosts the website and spreadsheet, and runs its sign-in and Library requests. Sends the analytics events our servers record to PostHog. |
| Resend | Sends account emails, such as the link that confirms your email address, and product emails, delivers requests for higher limits to our own inbox, and sends you our decision on them. It receives your address and the message, only to deliver it. United States. |
| PostHog | Product analytics, as described above, including the address r.basis1.tech that receives browser events. It never receives your email address. United States. |
| Google (sign-in) | Only if you choose “Continue with Google”: confirms your identity and tells us your email and name. |
We publish the basis1 SDK and MCP packages through npm. Installing them downloads code from npm; we don’t send your data to npm.
Cookies and browser storage
We use only the cookies needed to sign you in:
basis_session: keeps you signed in. Lasts 30 days.basis_oauth: protects a Google sign-in while you’re on Google’s page. Lasts 10 minutes and is cleared when you return.
Your browser’s local storage keeps your preferences (theme, display options, which tips you’ve seen, audit source). PostHog keeps its anonymous visitor ID and settings in local storage too, not in cookies. Clearing your browser’s site data removes all of these.
Deleting your files or your account
- A file: move it to the trash in your Library, then choose “Delete forever”. That removes the file, every version, its shares and its comments.
- An API key: revoke it on the API keys page. It stops working immediately.
- Your account: go to Settings and choose Delete account. You confirm with your email address and your password (or a recent Google sign-in). That ends your sign-in on every device and permanently deletes your account, every file in your Library with all its versions, shares and comments, your API keys with their usage records, your connected apps, your email preferences and record of product emails, and your requests for higher limits. Files other people shared with you stay theirs; comments you left on them stay too, shown as written by “Deleted user”. If something fails partway, the deletion is finished automatically within a day.
- Your analytics data isn’t removed by deleting your account. It’s linked only to your account ID, which no longer points to anyone, and is deleted after a year. Email basis@onigiricapital.com if you’d like it removed sooner.
Your rights
Wherever you live, you can ask us for a copy of the personal information we hold about you, ask us to correct it, or ask us to delete it. You can download your own files from your Library at any time.
If you are in the EU, UK or a similar jurisdiction (GDPR): we process your account and file data to provide the service you signed up for (performance of a contract), and analytics, logs and abuse prevention on the basis of our legitimate interest in running and improving a reliable, secure service. We send product emails to account holders about our own service, as the rules for existing customers allow, telling you at sign-up and giving you a way to opt out in every email; you can object at any time by turning them off. You can object to other processing, ask us to restrict it, or ask for your data in a portable format, and you can complain to your local data protection authority.
If you are in California (CCPA/CPRA): you have the right to know, delete and correct your personal information, and we won’t treat you differently for using those rights. We don’t sell or share personal information as those laws define it.
To make any of these requests, email basis@onigiricapital.com. We may need to confirm that you control the account first. We don’t hold any privacy or security certification (such as SOC 2 or ISO 27001) at this time.
Children
basis1 is a work tool and isn’t meant for children. Don’t create an account if you’re under 16. If you think a child has given us personal information, email us and we’ll delete it.
Changes to this policy
We’ll update this page and the date at the top when our practices change. If a change is significant, we’ll tell signed-in users in the app or by email before it takes effect.