Security and trust
How SEA protects your learning data.
Your goals, diagnostic results, evidence and skills record belong to you. Here is what the platform does to keep them private.
Current practices
Security built into how SEA works.
Authenticated accounts
Sign-in uses Supabase Authentication with email verification, or Google sign-in. Passwords are never stored by SEA's application code.
Row-level access control
Database row-level security policies limit each learner to their own records, and organization data to authorized members of that organization.
Role-based permissions
Learner, reviewer, trainer, training manager and administrator roles are checked on the server, not only in the browser.
Server-side AI calls
AI requests run on SEA's servers. AI provider keys are never sent to the browser, and AI output is validated before it is used.
Audit records
Important actions, such as evidence verification decisions, are recorded so they can be reviewed later.
No stored card data
SEA does not store raw payment-card data. Online payments are not open yet.
Skills you can trust
Verified means reviewed.
A skill enters your Skills Passport only after eligible evidence is reviewed and verified. Completing a resource or a diagnostic alone does not add a verified skill.
Certifications
What we do not claim.
SEA has not yet obtained independent security certifications, so we do not display any. We will only list a certification once it has been formally awarded.
To report a security concern or ask a question about how your data is handled, email info@seaaiacademy.io.