What scri8e does with your company’s knowledge.

Only the sources you connect, and within those, only what you explicitly scope. Slack, Google Drive and Notion each have a picker, and for Drive and Notion an empty selection means nothing is indexed at all. For Slack, an empty selection means every channel the bot can join.

• Slack: messages and threads in the channels you select (every channel it can join if you select none), plus member profiles so answers can attribute who said what.
• Google Drive: files in the folders you select, and each file’s sharing permissions, which is what lets scri8e keep private files private.
• Notion: the pages and databases you select, from those shared with the scri8e integration.
• Anything a workspace admin uploads directly, or a member uploads when an admin allows it, and the questions people ask.

scri8e connects with read-only scopes. It has no ability to post, edit, move or delete anything in Slack, Google Drive or Notion.

One honest exception: to read a Slack channel’s history, the scri8e bot has to join that channel, the same as adding any other app. That is a visible action in Slack and it is the only thing scri8e does that changes anything on your side. It never sends a message.

This is the section that matters. Indexing and answering are not the same thing, and they do not touch the same systems.

Indexing stays on our servers. The mathematical representation scri8e builds to search your documents is computed on servers we rent from Contabo and run ourselves. Your document text is not sent to a third-party embedding service.

Answering does not. When someone asks a question, the passages scri8e retrieved are sent to a language-model provider to write the answer. That means excerpts of your content leave our systems at the moment a question is asked. We would rather say this plainly than let “your data stays yours” imply otherwise.

The third parties involved, and what each one sees:

• Supabase hosts the database and handles sign-in. Sees everything scri8e has indexed, at rest.
• Contabo rents us the servers that run scri8e’s API, background workers, job queue and the model that indexes documents. Sees all indexed content while it is being processed.
• Nango brokers the OAuth connections and proxies the API calls to Slack, Drive and Notion. Sees your content in transit while it is being fetched.
• Groq runs the language model that writes answers. Sees the question, and the passages retrieved to answer it. It does not receive your whole corpus.
• Vercel hosts this website and counts page visits with Vercel Web Analytics, which sets no cookies. Sees which pages are visited, the referring site, and the browser, device and country, never your workspace’s content.
• Dodo Payments processes subscription payments as our Merchant of Record. Sees the payment and billing details you enter at checkout. It never sees your workspace’s content.
• Google (Gmail) delivers what you send through the contact form, and our confirmation and reply. Sees your name, email address, company and message, never your workspace’s content.

We do not sell your content, and scri8e does not use it to train models.

When you pay for scri8e, you enter your card details on Dodo Payments’ checkout, not on scri8e. Dodo Payments is our Merchant of Record: it is the seller of record for the charge, works out any sales tax, and processes the payment under its own privacy policy. We receive the result: whether the payment succeeded, the amount, and a transaction reference. We never see or store your full card number.

How cancellations and refunds work is on the cancellation and refunds page.

scri8e never grants access to anything. It copies the permissions that already exist in Slack and Google Drive each time it syncs (daily, or whenever someone syncs by hand) and checks every question against that copy. A change in the source tool reaches scri8e by the next sync, not the moment it is made.

Slack is mirrored per channel and Google Drive per file. Notion is coarser, and we would rather be exact about it: Notion’s API does not expose per-page sharing to an integration, so anything shared with the scri8e integration becomes visible to everyone in your scri8e workspace, regardless of how narrowly it is shared inside Notion. That is a limit of Notion’s API, not a setting we have chosen.

Each workspace is stored and queried separately. Your content is never pooled with another company’s.

Disconnecting a source gives you a choice. Choose deletion and that source’s documents and their search index are removed straight away and cannot be recovered. Answers already given that quote those documents stay in the conversations they were asked in until those conversations are deleted. Choose to keep it and it stays answerable until you delete it or remove the documents individually. Documents you uploaded by hand are not attached to a source, so disconnecting one never removes them; delete those from the admin screen. Narrowing what a source covers also deletes the indexed copy of anything you just excluded.

Workspace admins can also remove any individual document from the admin screen. Governance actions (connecting, disconnecting, uploading, approving, deleting, role changes) are recorded in an append-only log so a workspace can see what happened and who did it.

Anyone can delete their own account from Settings. That removes their sign-in, their conversations and question history, and their own Google Drive connection along with the files indexed through it. What they shared with the team, such as uploads and verified answers, stays, without their name on it. The workspace’s last owner first makes someone else an owner, or deletes the workspace.

An owner can delete the whole workspace from Settings once no subscription is set to renew (cancel it on the Billing page first). That removes everything at once: every document and its index, the connections (revoked with the provider), conversations, verified answers, the audit log, and every member’s account and sign-in. It cannot be undone.

No SOC 2 report. We are early, and we would rather tell you that than imply otherwise. If you need one before you can sign, say so and we will tell you honestly where it stands.

There is no self-hosted option yet either. We don’t have a signed data processing agreement yet. If you need one, write to us.

If this policy changes in a way that affects what we do with your content, we will say so rather than quietly update the date at the top.

scri8e is operated by Niket Shah, trading as scri8e, in Ahmedabad, Gujarat, India. There is no incorporated company behind it yet, and we would rather say so than name an entity that does not exist.

For any privacy question, including access, correction or deletion of your data, write to hello@scri8e.in.

Terms of Service