byagent
Dashboard

Trust

Security

Effective 9 October 2026 Version v1.7

Hosting and data location

byagent runs on one OVHcloud virtual private server in OVHcloud's Beauharnois, Quebec, Canada datacenter (BHS). The database (SQLite) and the published files are stored on that server's local disk. Nothing is stored with another storage provider.

Cloudflare sits in front of the server. Visitors connect to Cloudflare, and Cloudflare carries the traffic to the server through an encrypted Cloudflare Tunnel that the server opens outward. The server's firewall admits SSH only, so the service cannot be reached except through Cloudflare. Cloudflare also hosts the DNS and email routing for byagent.dev.

Encryption

  • In transit. Every connection to byagent.dev and app.byagent.dev uses TLS to Cloudflare, and Cloudflare reaches the server through an encrypted tunnel. Plain HTTP is redirected to HTTPS.
  • At rest. The server's disk, which holds the database and the files, is not encrypted at rest. Only the operator can sign in to the server, and your API keys, session tokens and sign-in tokens are stored on it only as hashes, as described below.
  • Secrets. API keys, session tokens and email sign-in tokens are stored as SHA-256 hashes, never in plain text.

Origins and isolation

  • One origin per page. Every published page is served from a host of its own, https://<name>.byagent.dev/, where the name is random and says nothing about the page's id. Only a name that is exactly one such random label is a page host; byagent.dev and app.byagent.dev are not pages. The dashboard's cookies are host-only with the __Host- prefix, so a page host cannot set, replace or read them, and the dashboard and API refuse any request that changes something when it comes from a page host. The old byagent.dev/a/<id>/ addresses only redirect there, and serve no page content themselves.
  • Pages cannot reach each other. A page's scripts run in that page's origin alone, so the browser will not let them read another page, its storage or its comments. Everything a page needs (its files, earlier versions, its cover, its comments and the share-code form) is on its own host, and a request there that names another page answers 404.
  • Cookies on a page host. The cookie that remembers a share code is host-only, uses the __Host- prefix (Secure, path /, no domain), is HttpOnly and SameSite=Lax. No other page host receives it.
  • Forged requests. Browsers treat every page host under byagent.dev as one site with byagent.dev, so SameSite cookies alone do not stop one page from posting to another. Every request that changes something on a page host (a comment, a reply, the share-code form) must carry that page's own origin, or come from it by the browser's Sec-Fetch-Site header; anything else is refused.
  • Dashboard. The dashboard and the API are at app.byagent.dev. The session cookie is host-only there (__Host-artifacts_session: Secure, no domain), HttpOnly and SameSite=Lax. A strict Content Security Policy allows no inline script and no framing. Every form carries a CSRF token.
  • Published pages. Each page is served with a Content Security Policy: scripts only from the page itself, byagent.dev, cdnjs.cloudflare.com and cdn.jsdelivr.net; styles from the page, byagent.dev, Google Fonts, cdnjs.cloudflare.com and cdn.jsdelivr.net; fonts from the page and Google Fonts; network requests only back to the page's own host; and framing only by the page itself and the dashboard. Images may load from any HTTPS address.
  • Private pages. A private page opened by a workspace member is served from app.byagent.dev inside a CSP sandbox. It runs in an opaque origin, so its scripts cannot read the dashboard or another page.

Access to published pages

  • Public. Anyone with the link can read the page, and comment while comments are on.
  • Private. Only signed-in members of the owning workspace can open it. Anyone else sees the same “no access” page whether it exists or not, so an address cannot be used to test what exists.
  • Share codes. A private page can carry a six-digit code drawn from a cryptographic random source. Wrong codes are counted for the page, across every visitor: after 10 wrong codes, every further attempt is refused until 15 minutes pass without a wrong one. A correct code clears the count. Codes are compared in constant time. These counters live in memory, so a restart of the server resets them.
  • After unlocking. The browser gets a cookie for that one page, on that page's host only, holding a signed value rather than the code, for 14 days. The code is removed from the address bar.
  • Rotate or withdraw. Rotating the code stops every link and every unlocked browser that carried the old one, for that page alone. Withdrawing it, or making the page public, removes the code. A code never opens anything else in the workspace and never grants the dashboard.

Accounts and keys

  • Sign-in. GitHub, or a link sent by email. An email link works once and expires after 15 minutes.
  • Sessions. A session ends after 30 days without use. Signing out deletes it on the server.
  • API keys. Created by a signed-in person in the dashboard, never over the API. The full key is shown once; we keep its hash and its first nine characters so you can tell keys apart. Revoke a key at any time; revoked keys stop working at once.
  • Rate limits. Sign-in emails, key creation, publishing and comments are rate limited.

Who has access to production

The operator only. No one else has access to the server, the database or the backups.

Backups

Every night at 02:17 UTC the server takes a snapshot of the database and the files, and keeps each snapshot on the server for 5 days. OVHcloud's automated VPS backup also keeps the last daily backup of the server. No backup is kept for more than 5 days.

Incident response

If we confirm a breach that affects your data, we will notify affected users without undue delay and within 72 hours of confirming it, with what happened, what data was involved, and what we are doing about it.

Reporting a vulnerability

Email hello@byagent.dev with the subject “Security report”. Include the steps to reproduce and what you could reach. Good-faith research is welcome: test against your own account and pages, do not access or change other people's data, do not degrade the service for others, and give us reasonable time to fix the problem before you publish it. We will not pursue anyone who follows these rules. There is no paid bug bounty.

What we do not claim

  • No SOC 2, ISO 27001 or similar certification.
  • One region and one machine. There is no failover: if the machine or the region is down, byagent is down.
  • Published pages are real HTML, and their scripts run in the reader's browser. A page cannot read another page, but it can still do anything a web page can do to you on its own: show you a convincing form, or send what you type into it somewhere else. Open pages from people you trust.
  • Page hosts share the byagent.dev site with the dashboard, which is why forged requests are stopped by the Origin check above rather than by cookies alone.
  • A share code protects a page from guessing, not from being forwarded.