Privacy Policy
Last updated: 2026-02-24
1. What We Collect
When you sign in with Google, we receive and store:
- ·Email address
- ·Profile picture URL (from Google)
When you use the service, we store:
- ·Memo text you save (up to 2 KB each)
- ·Memo metadata: group name, visibility, timestamps
- ·API keys — only the SHA-256 hash is stored, never the plaintext key
2. How We Use It
We use the data solely to provide the memopaper service:
- ·Identifying your account and linking memos to it
- ·Authenticating API requests via your API key
- ·Displaying your memos in the dashboard and CLI
We do not sell your data, run ads, or use your memos to train models.
3. Public Memos
Memos saved with visibility: public are visible to anyone on the public feed, including your profile picture. Mark memos as private (the default) if you do not want them shown publicly.
4. Third Parties
- ·Clerk — handles authentication (sign-in, session management). See clerk.com/privacy.
- ·Supabase — stores all user and memo data (PostgreSQL, hosted in AWS us-east-1). See supabase.com/privacy.
- ·Vercel — hosts the web application and API. See vercel.com/legal/privacy-policy.
5. Data Retention
Your data is retained as long as your account exists. You can delete individual memos at any time via the dashboard, CLI (memopaper delete), or API.
To delete your account and all associated data, contact us at memopaper@memopaper.dev.
6. Contact
Questions or requests: memopaper@memopaper.dev