Privacy Policy
How Blogton handles your data
Blogton is an early-stage startup project. This policy reflects what is actually implemented in the current version (1.0) — nothing is assumed or pre-emptive.
Overview
Blogton is a minimalist blogging platform. We collect only the data that is functionally necessary to run the service. We do not sell your data. We do not run ads. This policy describes exactly what data exists in the system today.
Authentication and database services are provided by Supabase, a third-party backend platform. Your data lives in Supabase's infrastructure.
Data We Collect
The following table covers every type of data currently stored by Blogton:
| Data | Why it's stored | Visibility |
|---|---|---|
| Email address | Required for account creation and login | Private |
| Username | Chosen at signup; identifies your profile and posts | Public |
| Blog posts title, content, cover image |
Published posts appear in the public feed | Public |
| Liked posts | Records which posts you have liked; like counts are public | Count is public |
| Starred posts | Your personal reading list, shown on your profile tab | Public on profile |
| Join date | Displayed on your public profile page | Public |
| Google account info if using Google sign-in |
Name and email provided by Google OAuth; used only for auth | Private |
Authentication
Blogton supports two sign-in methods:
Email & password — Your password is never stored in plaintext. It is hashed and managed entirely by Supabase Auth.
Google OAuth — If you choose "Continue with Google," your Google account name and email are passed to Supabase to create or identify your account. No other Google account data is accessed.
Authentication sessions are maintained via tokens managed by Supabase. Clearing your browser storage or signing out will end your session.
Public Content
Everything you publish on Blogton — your username, blog posts, and starred reading list — is publicly visible to anyone who visits the platform, including users who are not signed in.
Do not publish content you want to keep private. There is currently no draft or private post feature.
Third-Party Services
Supabase — All data (user accounts, posts, likes, stars) is stored in a Supabase project (PostgreSQL database). Supabase's own privacy policy governs how they handle the infrastructure. See supabase.com/privacy.
Fonts — The EB Garamond typeface is loaded from Google Fonts CDN. This may result in your IP address being logged by Google as part of a standard CDN request. No account data is shared.
No other third-party services, analytics providers, or advertising networks are currently integrated into Blogton.
What We Don't Do
As of version 1.0, Blogton does not:
| Run ads or sponsored content |
| Sell or share user data with third parties |
| Use tracking pixels or behavioral analytics |
| Build advertising profiles from your activity |
| Send marketing emails |
This section reflects only the current state of the project. Future features will be disclosed in updated versions of this policy.
Your Rights
Delete your posts — You can delete any post you've written from within the app.
Account deletion — You can delete your account directly from the app through the Settings page. This will permanently remove your account and all associated data.
Data questions — For any questions about what data is stored for your account, reach out through the Contact page. This is an early-stage project and the creator will respond personally.