Privacy Policy

We store your name and email address.

If you sign in with Google, Google confirms who you are and shares your name and email - we never see your Google password. If you sign up with email and password, the password is stored hashed (scrambled beyond recovery) by our authentication provider; nobody at Tublish can read it.

Sign-in events include your IP address, kept in our provider's security logs - that's standard protection against break-ins.

Your Spaces, pages, posts, articles, pictures, and settings are stored so we can show them to your visitors and deliver them where you send them. That's the product.

When you connect a platform to the poster, you give Tublish a key (a webhook address, a bot token, an app password - whatever that platform uses). We store it and use it for exactly one thing: delivering the posts you send.

We never ask for, and never store, your actual password to any other platform.

Disconnecting a platform deletes its key.

When a visitor subscribes on a creator's page, their email lands in that creator's subscriber list. The list belongs to the creator; Tublish stores it for them. Creators can download or delete their list at any time.

When a visitor submits a public form (subscribing, or sending a message to a creator), we record the sender's IP address alongside it. That's our spam and abuse defense, nothing more.

Just visiting a Tublish page? We don't set advertising cookies or run third-party analytics on you. Standard server logs at our hosting provider (Cloudflare) exist, as on virtually every website.

Tublish is currently in a testing phase with invited creators, and honesty matters more than polish, so here it is plainly:

While testing runs, we log which dashboard screens signed-in accounts open and when, plus a rough location (country level) taken from the connection. We use this to fix bugs, verify tester reports, and understand what needs work.

There is no keystroke logging and no screen recording - we see which screens were opened, not what you did on them.

These logs are cleared periodically, and this section will be updated when the testing phase ends.

Tublish sets the cookies needed to keep you signed in. That's it - no advertising cookies, no cross-site tracking.

Small conveniences (your pinned world-clock cities, your link-tagger history) live in your own browser's storage and never reach our servers.

Tublish runs on trusted providers, each seeing only what their job requires:

• Supabase - our database and sign-in infrastructure (where your data lives)
• Cloudflare - serves the websites and pages
• Google - only if you choose Google sign-in
• The platforms you connect - they receive only the posts you send them
• A payment processor, once paid plans launch - card details go to them directly and never touch Tublish's servers

No data brokers. No selling. No renting. Ever.

We'd hand over data only if the law genuinely compels it.

Your account and content: until you delete them. Deletion starts a 30-day window in which you can change your mind; after that it's gone for good.

Subscriber lists: controlled by their creator, deleted with the creator's Space or account.

Anti-abuse records (IPs on public submissions) and the testing-phase logs: cleared periodically.

You can see, correct, download, or delete your data. Most of it you can handle yourself right in the dashboard; for anything else, email us and we'll do it.

If you're in the EU or UK, this is your GDPR right; in California, your CCPA right. We honor the spirit of both everywhere: it's your data.

Tublish isn't for children under 13, and we don't knowingly collect their information. If you believe a child is using Tublish, tell us and we'll remove the account.

When this policy changes, the date at the top changes with it, and meaningful changes get announced by email or inside Tublish before they apply.