Privacy Policy
Last updated: January 2026
Overview
Substratia ("we", "our", "us") is committed to protecting your privacy. This policy explains how we collect, use, and safeguard your information when you use our website (substratia.io) and services.
Information We Collect
Account Information
When you create an account, we collect your email address and name through our authentication provider (Clerk). This is necessary to provide you with our services.
User Content
If you use Substratia Cloud, we store the snapshots and memories you choose to sync. This data is encrypted in transit and at rest.
Usage Data
We collect anonymous usage data to improve our services, including page views and feature usage. We do not use third-party tracking cookies.
How We Use Your Information
- To provide and maintain our services
- To authenticate your identity
- To sync your data across devices (if you opt in)
- To send important service updates
- To improve our products and user experience
Data Security
We implement industry-standard security measures:
- All data is transmitted over HTTPS
- API keys are SHA-256 hashed before storage
- Authentication is handled by Clerk with secure session management
- User data is isolated and scoped per account
Third-Party Services
We use the following third-party services:
- Clerk - Authentication (see their privacy policy)
- Convex - Database hosting (see their privacy policy)
- Vercel - Website hosting (see their privacy policy)
Your Rights
You have the right to:
- Access your personal data
- Request deletion of your data
- Export your data
- Opt out of marketing communications
To exercise these rights, contact us through GitHub or your account settings.
Data Retention
We retain your data for as long as your account is active. If you delete your account, we will delete your personal data within 30 days, except where required by law.
Changes to This Policy
We may update this policy from time to time. We will notify you of significant changes via email or a notice on our website.
Contact
For privacy concerns, please open an issue on our GitHub repository.