Security
How Waaypoint keeps your plans, code links and people’s data safe.
Waaypoint holds your plans, roadmaps and code links, so we treat keeping them safe as the job, not an extra. This page explains how. To report a security problem, write to security@waaypoint.com; we reply within two business days.
Your data stays yours
- Each company gets its own workspace. Every read and write in the app and the API checks which workspace you're in, and data never crosses between workspaces.
- Export whenever you like. The whole workspace downloads as CSV or JSON. If a plan lapses, the workspace turns read only and nothing is deleted.
- Deleting is careful. Deleted items wait in the trash for 30 days, and bulk edits can be undone.
Sign-in and access
- Sign-in through Clerk, a dedicated identity provider, with two-factor authentication for anyone who turns it on.
- Admins can require two-factor sign-in for every admin in the workspace.
- Roles and permissions: admins, members and view-only seats, with fine-grained permissions for planning, import, settings and more.
- API keys are shown once and stored only as a hash. Each key can be limited to certain teams and statuses, given a work-in-progress limit, and revoked at any time.
- AI agents and connected apps can't delete, and can be held to the teams and statuses you choose. Teams can require a person's approval before an agent's work counts as done.
Records of what happened
- Audit log: who changed settings, roles, API keys, integrations and automation rules, and when. When Waaypoint support opens your workspace to help you, that's recorded in your audit log too.
- History on every item, labelled by whether a person, an AI agent or an integration made the change, with an export of everything agents did.
Infrastructure
- Hosted on Vercel, with the database on Neon, both in the United States. Data is encrypted in transit (TLS, with HSTS) and at rest.
- Nightly backups, kept for 30 days in private storage.
- Files are private. Attachments are served only to members of the workspace, and never run as pages in your browser.
- Strict browser protections: a Content-Security-Policy that allows only the services we use, no framing by other sites, and no cookies beyond sign-in.
- Rate limits on the API protect against abuse, and errors are recorded for us to review.
How we build it
- Every change is reviewed and tested before it ships: type checks, unit tests, end-to-end browser tests and accessibility checks run on every pull request.
- Changes go to staging first, and reach production only through a release.
- Dependencies are kept up to date with automated pull requests, and we wait for new versions to settle before taking them.
Privacy
We don't sell personal data, and we use no advertising or cross-site tracking. See the Privacy Policy for what we collect and the Data Processing Agreement for business customers, including the full list of services that process data for us.
Questions
Security reviews and questionnaires are welcome: write to security@waaypoint.com.