Security

Authentication

• Passwords are hashed and salted by our managed authentication provider. Nobody at EyeCreate can read your password.
• Sessions use short-lived tokens with automatic refresh and revocation on sign-out.
• Optional sign-in with Google, so you can avoid another password entirely.
• Password reset runs through an emailed, time-limited link.

Data in transit and at rest

• HTTPS everywhere. Traffic to EyeCreate is encrypted in transit.
• Database storage and file storage are encrypted at rest by our platform provider.
• Uploaded files (such as reflection audio and pet journals) live in private buckets, not public URLs.

Access control

• Every table holding personal content enforces row-level security scoped to the signed-in account.
• Roles are stored separately from profiles, so a user cannot escalate their own permissions.
• Privileged operations run server-side only, after verifying who is asking.

Operational controls

• Rate limiting on authentication and AI endpoints to slow abuse.
• Automated encrypted backups with point-in-time recovery on the database.
• Audit logging on privileged and administrative actions.
• Automated security scanning of our database policies and dependencies.
• Secrets are stored in a managed secret store, never in source code.

Shared responsibility

We secure the platform, the database rules, and the application code. Our hosting provider secures the underlying infrastructure. You help by using a strong, unique password, keeping your device updated, and signing out on shared computers.

Reporting a vulnerability

If you find a security issue, email eyecreatellc@outlook.com with the subject line “Security”. Please give us a reasonable window to fix it before disclosing publicly. We will acknowledge your report and keep you updated. We do not pursue legal action against good-faith researchers who avoid privacy violations and service disruption.