Studios trust GetEYT with their members' details, bookings and payments. This page says plainly what protects that data today and what is still being built. We do not hold a SOC 2 or ISO 27001 certification and do not claim to.
In place today
Payments
- Cards are handled by Stripe. Card numbers go straight to Stripe and are never stored on or passed through our servers.
- Each studio is paid through its own Stripe account.
Signing in
- No passwords to steal. You sign in with a one-time email link that expires after 15 minutes, or, where offered, with Google or Apple.
- Optional two-factor sign-in with an authenticator app for studio owners. The secret behind it is stored encrypted.
- Sign-in links are stored only in scrambled (hashed) form, and repeated attempts are rate-limited.
- Sign-in cookies hold a random token, cannot be read by page scripts, and only a scrambled (hashed) copy of the token is kept on our side.
Keeping studios apart
- Every request is tied to one studio, and every database query is limited to that studio's records. An automatic check runs over the code to catch any query that forgets this.
Messages
- Every email (and every text, once texting is available) passes through one gate that checks permission, opt-outs and quiet hours before sending. If something is missing, the message is not sent.
- Test studios can never message a real person.
Backups
- The database is backed up every day to a second server and each backup is kept for 14 days.
Records
- Sensitive actions, such as sign-ins, are written to an audit log.
In transit
- All traffic to geteyt.com and the app is encrypted (HTTPS).
Being built now
These are written down, owned, and scheduled. We will update this page as each one goes live.
| What | Why it matters | Target |
|---|---|---|
| Database-level separation of studios | A second wall, inside the database itself, so one studio can never see another's data even if the code has a mistake. It is built and tested, and is waiting to be switched on. | Before the first studio outside the pilot |
| Regular test restores of the backups | A backup only counts if it can be restored. A test restore on a schedule. | Before the first studio outside the pilot |
| Uptime and error monitoring with a public status page | We should know about a problem before you do. | Before the first studio outside the pilot |
| A security contact file (security.txt) and monitored inbox | Gives anyone who finds a problem a clear place to report it. | Before public launch, January 2027 |
| An independent security test | Someone outside the team tries to break in. | After public launch |
| A formal security certification (SOC 2) | Larger studio groups ask for it. We are not there yet. | Not yet scheduled |
If something goes wrong
If we confirm a breach that affects a studio's data, we will tell that studio within 72 hours, explain what happened and what we are doing, and help it notify members where the law requires.
Report a problem
Found a security issue? Email info@netryse.com. Please give us a reasonable chance to fix it before telling anyone else. We will not take action against anyone who reports in good faith and does not access more data than needed to show the problem.
Who we work with
The outside companies that help run GetEYT are listed on our subprocessors page.