Read-Only, Permission-Aware, and Plain About Its Gaps.
scri8e connects with read-only scopes, mirrors the permissions in Slack and Google Drive document by document, and keeps each workspace separate. This page also lists what it doesn’t have yet, starting with a SOC 2 report.
- Access
- Read-only
- Permissions
- Mirrored from each tool
- Isolation
- Per workspace
- Model training
- Never on your content
- SOC 2
- Not yet
- Public channelEveryone in the workspace
- Private channelMembers of that channel in Slack
- Google Drive filePeople on the file’s sharing list
- Page shared with scri8eEveryone in the workspace
- Upload, whole workspaceEveryone in the workspace, once approved
- Upload, restrictedThe people the uploader named
- Anything elseNobody
One filter, applied before anything reaches the model. A source that matches no rule is hidden from everyone.
Permissions Come From the Tool, Not From Us
scri8e never grants access to anything. It copies who can open what from the tool the document lives in.
- Re-read on every sync
- Channel membership and file sharing are refreshed each time a source syncs, and checked again on every question.
- Fails closed
- A Drive file shared only with a Google group or by link, or a person whose email can’t be matched, stays hidden rather than shown.
- Each Drive read by its owner
- Google only gives a file’s full sharing list to its owner, so each teammate connects their own Drive. That keeps per-file permissions accurate.
The same rule covers verified answers: one is shown only to someone who can open every source it cites.
Seven Services Touch Your Data. Here Is What Each One Sees.
Indexing runs on servers we rent from Contabo and run ourselves. Answering doesn’t: the passages needed for an answer go to a language-model provider at the moment someone asks.
Supabase
Hosts the database and sign-in
Sees: Everything scri8e has indexed, at rest
Contabo
Rents us the servers that run the API, workers and indexing model
Sees: All indexed content, while it is processed
Nango
Brokers the connections to Slack, Drive and Notion
Sees: Your content in transit, while it is fetched
Groq
Runs the language model that writes answers
Sees: The question, and the passages retrieved for it
Vercel
Hosts this website and counts page visits, without cookies
Sees: Which pages are visited, never your content
Dodo Payments
Processes payments as Merchant of Record
Sees: Billing details only, never your content
Google (Gmail)
Delivers contact form messages and our replies
Sees: What you send through the contact form, never your content
The full account, including how deletion works, is in the privacy policy.
It Reads. It Never Writes.
It can’t change anything in your tools. For Slack and Drive, the worst it can do is quote something back to someone who could already read it.
- Read-only scopes
- It can’t post, edit, move or delete anything in Slack, Drive or Notion. One visible exception: the Slack app joins a channel to read its history. It never sends a message.
- Roles and an audit log
- Owner, admin and member roles. Connecting, disconnecting, uploads, approvals, deletions and role changes are written to an append-only log.
- Deleting what it read
- Disconnect a source and choose deletion, and the indexed copy goes straight away. Removing a Drive folder or Notion page from the selection deletes what was indexed from it. Anyone can delete their own account from Settings, and an owner can delete the whole workspace there.
What We Don’t Have Yet
Better here than in week two.
Gaps, stated plainly
- No SOC 2 report. If you need one before you can sign, ask and we’ll tell you honestly where it stands.
- Notion is workspace-wide. Notion’s API can’t tell an integration who a page is shared with, so anything shared with scri8e is visible to your whole scri8e workspace. Share only pages the whole team may read.
- No self-hosted option, and no choice of data region yet.
Security questions
Does scri8e train AI models on our content?
No. We don’t use your content to train models and we don’t sell it. When someone asks a question, the passages needed for that answer are sent to Groq to write it. Groq never receives your whole index.
Can an admin see everything?
Not through answers. Owners and admins manage connections and settings, but when they ask a question the same permission filter applies to them as to everyone else.
What happens when someone loses access to a file?
scri8e re-reads permissions from Slack and Google Drive on every sync, daily or whenever an admin syncs by hand, and checks them on every question. Once the change has synced, the file stops appearing in that person’s answers.
Connect It Knowing Exactly What It Can See.
Read-only, permission-aware, and honest about the rest. Book 20 minutes and we’ll connect it with you, or write to us first.