Skip to content
PoketProject

Security

Store where, never what.

PoketProject holds a map of your project, not your code and not your secrets. This page says how we protect what we do hold, and how to tell us when something is wrong. Last updated on 2026-09-27.

Hosting and encryption

The website runs on Vercel. Data lives in MongoDB Atlas. Both encrypt data at rest by default, and every connection uses TLS.

The full list of providers is on the subprocessors page.

Accounts and sessions

Passwords are hashed with scrypt. We never see or store them in plain text. Sign-in is rate-limited.

Sessions last 7 days and live in an HTTP-only cookie that page scripts cannot read. You can see every device you are signed in on and sign any of them out. Changing your password signs out your other devices.

Access keys

An access key is shown once. We store only its SHA-256 hash and a short prefix. Keys belong to one project, have a permission (read only, or read and propose drafts), an optional expiry and a limit of 60 requests per minute.

Every snippet we give you reads the key from an environment variable, so it never lands in your repo. Revoking a key cuts off the agent at once.

Secrets: references only

PoketProject stores where a secret lives (a vault path, an environment variable name), who owns it and which services use it. It never stores the value.

Every write, upload and agent call is scanned. A file that looks like it holds a key, a token or a password is refused, and the error never repeats the value. The activity log cannot contain a value by construction.

Agents write drafts

What an AI agent writes is Needs review until a person checks it. Rules, decisions and secret references always need an admin, because rules steer agents and a planted rule could do harm.

PoketProject runs no AI model on your code. Your own agent reads the code on your machine; the website receives only the .poket files you sync.

Access control

Workspaces have four roles: Owner, Admin, Member and Viewer. Every page and API route checks the role. People who are not members of a workspace get a 404, so a project's existence stays hidden.

Cross-site requests to the API are blocked. Security headers (HSTS, frame denial, a content security policy) are set on every response.

Report a problem

If you find a security problem, please tell us before you tell anyone else. Write to security@poketproject.example with what you found and how to reproduce it. We answer within 5 working days, fix confirmed problems as fast as we can, and credit you if you want. There are no paid rewards yet.

Please do not read other people's data, run denial-of-service tests, or send spam. Test against your own account and projects. The same details are in /.well-known/security.txt.

Placeholder: the owner must replace this address before launch.

Where we are honest about gaps

  • SOC 2: not yet. We are in early access.
  • Two-factor sign-in: not yet. Use a long password from a password manager, or sign in with GitHub or Google where it is on.
  • OAuth for claude.ai and ChatGPT: coming next. Today only clients that can send a bearer header can connect.
  • Backups: MongoDB Atlas keeps them. Deleted data leaves backups within 14 days.
  • Self-hosting: a community docker-compose install exists, with no support and no SLA.