Security at Restart
How your account, your builds and what you publish are protected, and what Restart does not claim yet.
Founders from
What is protected, and how
Security for teams
Roles, confirmed invites and publish approval come with every company. Enterprise plans add reviews, contracts and an SLA.
Learn more about Restart for enterpriseRoles
Owner, admin and member on every company. Members build and approve publishes, admins manage people, and only the owner handles billing or deletes the company.
Teams
Up to 25 people per company on Pro and 100 on Autonomous. An invite is only claimed by a confirmed email address.
Separate companies
Each company has its own workspaces, inbox, tasks and connected apps. Who you are and which company you are in is checked on every request.
Publish approval
Nothing goes live until someone on the company approves the exact version going out, with the file count and the cost in front of them.
Security reviews
Enterprise plans include security and compliance reviews, custom contracts and an SLA, and a named team to answer your questionnaire.
Sign-in
Email and password with a confirmed address, or Google. Single sign-on and directory sync are not available yet; ask about them on an Enterprise plan.
Secure on all fronts
Four fronts, each a rule you can see and check in the app.
Every workspace builds in its own machine, away from your browser and from your live site.
One machine per workspace
Each build runs in its own cloud machine. It sleeps between turns and is restored with your files when it wakes.
Separate from the live site
Your published site is deployed on its own, which is why it keeps serving while the build machine sleeps.
Sample data first
A first version carries no customer accounts, payments or third-party services, so there is nothing sensitive in it.
Reserved names
Some site names are permanently reserved, so a published site cannot impersonate a Restart surface or intercept mail.
A confirmed address, private companies, and encrypted connections.
Confirmed addresses
An email sign-up is not signed in until the address is confirmed with the six-digit code or the link in the mail.
Private by default
Your companies and workspaces are checked on every request; one you cannot access is reported as not found.
Encrypted connections
Every connection to Restart, its database and its file storage runs over TLS, and the providers encrypt what they store.
Payments by Stripe
Plans and credits are charged through Stripe. Restart never sees or stores your card number.
Your own sign-in with each tool, scoped skills, no deletes, no unattended sends.
Your own sign-in
Connecting an app goes through that tool’s own sign-in, scoped to the skills listed on the Apps page.
One step at a time
The coach reads when you ask and acts one action at a time. It never deletes anything in a connected app.
Automations never send
Scheduled work reads your inbox and apps and drafts replies for your approval. It never sends, posts or deletes on its own.
Switch off any time
Turn a skill off, uninstall the app from the Apps page, or revoke access from the tool’s side.
Material is material, not instructions, and neither agent can reach your account.
Pasted text is content
Documents, emails and pages an agent reads are treated as material for your product, never as commands, even when they address the AI directly.
No reach into your account
Neither the coach nor the Builder can change settings, buy credits, or see your plan or billing. Only you can.
Published sites are walled off
A site you publish cannot affect your Restart session or read your account.
You approve the handoff
Nothing is built until you accept the coach’s handoff, and nothing goes live until you approve the exact version.
Founders
Building your first company? You’re already covered.
The same rules apply to every Restart company from day one, on the Free plan too. There is nothing to switch on.
-
Your address is confirmed before your company opens.
-
Builds run in their own machine, away from your browser and your live site.
-
Nothing publishes without your approval of the exact version.
-
Connected apps and automations never send, post or delete on their own.
Compliance, in progress
No certification is held yet. These are the programs under way, published here the day they are.
Learn more about our compliance progress
SOC 2 Type II and ISO 27001 programs are underway and not yet held; GDPR and California privacy rights are handled as the Privacy Policy describes.
Frequently asked questions
Where does my company’s data live?
In Restart’s hosted database and file storage, run by cloud providers that encrypt what they store, over connections that are encrypted in transit. Your companies, workspaces, files and mail are private to your account and the people you add, and access is checked on every request.
How is my company isolated from other customers?
Every request checks who you are and which company you are in; a workspace you cannot access is reported as not found rather than forbidden. Each build runs in its own cloud machine, separate from other founders’ builds and from your published site.
How are secrets and API credentials handled?
Restart connects to your tools through each tool’s own sign-in, scoped to the skills listed on the Apps page, and you can switch a skill off or revoke the connection at any time. The agents never see your account, plan or billing. Do not paste credentials into a build: first versions run on sample data, and anything you paste may end up in what you publish.
Does Restart scan my apps for vulnerabilities?
Not yet. There is no automated vulnerability scanning of built sites today. A first build carries no customer accounts, no payments and no third-party services inside the product, which keeps its surface small; review anything you add before you approve a publish.
What keeps development changes away from production?
Builds happen in a workspace with a live preview that only you can see. The published site is a separate deployment, and it changes only when you approve a new version.
Who controls what gets published?
You do. Nothing publishes without your approval of the exact version going out, shown with its file count and cost before you confirm. On a team, members and admins can approve a publish; only the owner handles billing or deletes the company.
What happens if something goes wrong?
The version you published stays up until you approve another one, so a build that goes wrong never reaches your live site on its own. Ask the Builder to undo the change in the workspace, then approve a publish again.
Is Restart SOC 2, GDPR, or ISO 27001 certified?
No certification is held yet. SOC 2 Type II and ISO 27001 programs are underway, and we publish certifications here when they are held, not before. Privacy rights under GDPR and California law are handled as the Privacy Policy describes. Questions for a security review are welcome at simon@restart.new.
How is the platform itself tested?
By the team, with automated tests on every change, and by treating everything an agent reads (pasted text, email, pages from connected apps) as material rather than instructions. There is no public bug bounty yet; reports are welcome at simon@restart.new, as /.well-known/security.txt says.