Privacy

This describes what the Selat website and the Selat gateway store, written against the database schema rather than around it. Last updated 23 August 2026. Selat is operated by the individual developer who operates Selat, in Indonesia.

What Selat never stores

The arguments an agent sends to a tool, and the data an upstream sends back. A call to read a file, list a mailbox or create an issue passes through the gateway and is not written down. What is recorded is that the call happened, described below.

There are two exceptions, both narrow and both time boxed to 24 hours.

A retried write. A call sent with an idempotency key has its result held for 24 hours, so a retry returns the original answer instead of performing the action twice. After that the row is deleted, because a result older than the retry window can no longer be served to anyone.

A file too large to hand to a model. Downloading a large document would otherwise mean pushing megabytes of it through your agent, so past 256 KB Selat keeps the bytes and answers with an id instead. You fetch them at GET /v1/files/{id} with the same credential that made the call, and nobody else can: the id is scoped to your workspace and belongs to no one outside it. They are deleted after 24 hours, and deleting your workspace deletes them immediately.

This is the one place Selat holds the content of a file at all, and it exists to keep that content out of a model rather than to keep it. A smaller download is passed straight through and never stored.

Your account

When you sign in, Selat stores the name, email address and avatar URL that the sign in provider returns, plus a session record. It stores which workspaces you belong to and your role in each. If you invite someone, their email address is stored until the invitation is accepted or expires.

Apps you connect

Connecting an app gives Selat an access token and usually a refresh token for that vendor. Both are encrypted with AES-256-GCM before they are written, and the encryption is bound to your workspace and that specific grant, so a row lifted into another workspace does not decrypt. The key lives outside the database and is not stored with the data it protects.

Selat holds the scopes you approved and whether the grant needs reconnecting. Disconnecting an app deletes the tokens for it.

Gateway credentials

A gateway credential is shown to you once, at the moment you create it. Only a hash of it is stored, so it cannot be recovered from the database, by us or by anyone who obtains a copy of it.

What is recorded about each call

One row per call, holding the provider, the tool name, whether it succeeded, how long it took, a request id and a timestamp. That is the whole record. It carries no arguments and no response, so it can show that a Drive file was read and never which file. These rows are what the usage page counts and what a bill would be based on, and they are queried over a rolling 30 day window.

A separate audit log records administrative actions such as connecting an app or revoking a credential: who did it, what they did, and to what.

Google user data

Selat’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

In plain terms, and without exception: data from Google APIs is used only to carry out the specific request your agent made. It is not used for advertising, it is not sold or transferred to anyone, and it is not used to train any model, ours or anybody else’s. No human reads it, except where you ask for support and grant access, or where the law requires it.

The same holds for every other upstream Selat connects to. Google states it as a policy, so it is stated here explicitly.

Which Google scopes Selat asks for, and why

Selat asks only for the scopes belonging to the apps you have actually connected. Connect Drive alone and the request covers Drive alone. Connecting a second app widens the same grant rather than replacing it, so nothing you already approved is quietly dropped.

Google Drive API, auth/drive. Lists and searches your files, reads a file’s contents, and on your instruction creates, renames, moves, copies, shares, trashes, deletes or replaces them. The narrower auth/drive.file is not enough for what Selat is for: it only sees files this app itself created or that you picked for it one at a time, so a listing of the Drive you already have would come back empty and every tool above it would have nothing to act on. Read-only Drive was what Selat used until August 2026, and it cannot do the second half of that list at all.

Gmail API, auth/gmail.readonly. Reads the account profile, lists messages, reads one message’s headers and snippet, and reads a label’s counts, so an agent can answer questions about the mailbox. No write scope is requested, so Selat cannot send, delete or alter mail even if asked to.

Google Calendar API, auth/calendar.readonly. Lists your calendars, lists events in a window, and reads one event. Read only for the same reason.

Whatever the scope permits, a Selat credential can be issued read-only, and a read-only credential is refused every write tool before the request reaches Google at all.

Where it runs

The website and its database run on Vercel and Neon. The gateway and its database run on a single virtual server in Jakarta, Indonesia. Backups of the gateway database are encrypted before they leave the machine, with a key that is not on that machine and not held by the hosting provider.

Beyond that, requests go to the upstream you connected, and to nobody else. Selat sends no analytics or tracking to third parties.

Deleting your data

Disconnecting an app deletes its tokens immediately. Deleting a workspace deletes everything keyed to it, including connections, credentials, usage rows and the audit log, by cascade rather than by a cleanup job that could be skipped. To delete an account entirely, write to privacy@selat.weekndlabs.com.

Changes

If this changes in a way that affects what is stored, the date at the top changes with it. See also the terms of service.

Contact

privacy@selat.weekndlabs.com