Em resumo
Guardamos o seu nome e o seu endereço de e-mail.
Se você entra com o Google, nunca vemos a sua senha do Google; se você cria uma senha aqui, ela fica guardada de forma embaralhada e irreversível, que ninguém no Tublish consegue ler.
O que você cria fica guardado para que possamos mostrar aos seus visitantes e entregar onde você mandar.
Esse é o produto.
Para convidar alguém para a equipe, você nos dá o e-mail da pessoa, que usamos só para enviar o convite.
Os membros da equipe veem os Espaços que você compartilha com eles, até onde as caixas que você marcar permitirem, o que pode incluir os seus assinantes e as mensagens que os seus visitantes enviam.
Se você entrar na equipe de outra conta, essa conta vê o seu nome, o seu e-mail e o que você fez nos Espaços dela.
Uma chave que você nos dá para outra plataforma (um webhook, um token de bot, uma senha de app) serve para uma coisa só, entregar o que você envia, e é apagada assim que você desconecta a plataforma.
Nunca pedimos a sua senha de outra plataforma.
O Tublish usa os Serviços de API do YouTube: lê os dados públicos do seu canal e os comentários dos seus vídeos, guarda deles só as tags de pedido e quantas pessoas pediram, e só envia os vídeos que você manda.
O que acontece do lado do Google é coberto pela política de privacidade do Google.
Você pode tirar o acesso na tela Plataformas ou na sua conta do Google, e pedir que a gente apague os seus dados do YouTube, o que fazemos em até 7 dias.
Um assistente que você conecta (Claude ou ChatGPT, por exemplo) pode ler a sua conta, inclusive os seus números, os pedidos que o seu público deixou nos seus comentários do YouTube, os seus assinantes e as mensagens dos seus visitantes; preparar publicações; pedir ao Tublish que leia os comentários dos seus vídeos do YouTube em busca de novos pedidos; enviar newsletters para a sua lista de e-mails e adicionar assinantes a ela pelo serviço de e-mail marketing que você conectou; escrever, publicar e mudar os artigos do seu blog; colocar a miniatura que falta num vídeo que você enviou ao YouTube; mudar o seu Piloto automático (as regras e a reserva de stories); e mudar o seu cartão de visita digital, o seu site, o seu mídia kit (nunca os números dele) e as configurações do seu Espaço.
O que ele lê é processado pela empresa que o fabrica, segundo a política dela.
Se a mensagem de um visitante parecer escrita para o assistente e não para você, ela fica escondida dele até você liberá-la na tela Mensagens.
Cada publicação ou newsletter que ele envia, cada artigo que ele escreve ou publica e cada mudança que ele faz no seu cartão, no seu site, no seu mídia kit ou nas configurações do seu Espaço leva o nome dele, e você pode desconectá-lo a qualquer momento na tela Assistentes.
Na equipe de outra conta, ele só lê e muda o que o seu lugar nessa equipe abre.
A lista de assinantes de quem cria no Tublish pertence a essa pessoa: ela pode baixá-la ou apagá-la quando quiser.
Nos formulários públicos (assinar, ou escrever para quem cria), registramos o endereço IP de quem envia.
É uma defesa contra spam, nada mais.
Registramos as telas do painel que uma conta abre e, de forma aproximada, o país da conexão, para podermos corrigir o que nos relatam.
Não registramos o que você digita nem gravamos a tela, e esses registros são apagados regularmente.
E quando uma página trava, o navegador nos manda um relatório curto (onde aconteceu, o erro, o navegador, o idioma da página e a conta conectada, se havia uma), apagado junto com o resto.
Os cookies mantêm a sua sessão aberta e guardam algumas escolhas que você faz no painel.
Nenhum cookie de publicidade, e nenhuma ferramenta de análise de terceiros observando você enquanto lê.
Nada de corretores de dados. Nada de venda. Nada de aluguel. Nunca.
Você pode ver, corrigir, baixar ou apagar os seus dados, a maioria por conta própria, no painel.
É o seu direito pelo GDPR (União Europeia e Reino Unido) e pela CCPA (Califórnia), e respeitamos isso em todo lugar, não só onde é obrigatório.
Quando você paga um plano, os dados do seu cartão vão direto para a Paddle, que vende nossos planos, e nunca chegam ao Tublish.
Isto é um resumo, para facilitar a leitura. A versão em inglês abaixo é a que vale.
1. When you create an account
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.
2. What you create
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.
If you invite teammates, you give us each one's email address, and we use it to send the invitation and nothing else. Once they join, they see what is in the Spaces you share with them, as far as the boxes you tick allow - which can include your subscribers' email addresses and the messages your visitors send you.
If you're on somebody else's team, they see your name and email address, and every log in their Spaces shows what you did there and when.
3. Platform connections
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.
Tublish uses YouTube API Services. When you give Tublish your YouTube channel, it reads the channel's public details through them: its name and picture, its videos and their titles, your subscriber, view, like and comment counts, and the comments under your videos. It reads those comments only to count the requests your audience leaves - it keeps the tag and how many people asked, never who asked or the rest of what they wrote.
If you connect YouTube so Tublish can upload for you, Google gives us a key. We use it only to learn which channel is yours and to upload the videos you send, with the title, description, picture and settings you chose. Some YouTube connections are made through our posting partner, Outstand, which then holds that key instead of us.
How Google itself handles this data is described in the Google Privacy Policy.
You can take Tublish's access away at any time: Disconnect on the Platforms screen deletes the key and tells Google, or our posting partner, to cancel it; or remove Tublish on your Google Account's security settings page.
To have the YouTube data we keep for you deleted, write to us through the contact page, and we'll delete it within 7 days.
4. Assistants you connect
On the plans that include it, you can connect an assistant such as Claude or ChatGPT to your Tublish account. You start it from the assistant and approve it on a Tublish page.
A connected assistant can read your account - your name and plan, your Spaces, the platforms connected to them, your posts and videos, your blog articles (drafts included), your Autopilot, your numbers, the requests your audience left in your YouTube comments, your calendar and to-do list, your subscribers' email addresses and the messages visitors send you - prepare new posts, have Tublish read the comments on your YouTube videos for new requests, send newsletters to your mailing list and add your subscribers to it through the mailing service you connected, write, publish and change your blog articles, put the picture you picked on a video you sent to YouTube that went up without it, change your Autopilot (its rules and its Story shelf), and change your E-Business card, your website, your media kit (what it says about you, how it looks, and whether it is online - never its numbers) and your Space's own settings (whether it is online, the language it speaks to visitors, and the phone number, WhatsApp number and email address its contact buttons show).
A visitor's message that reads as if it was written to the assistant rather than to you is kept from it until you let it through on the Messages screen.
If you're on somebody else's team, an assistant you connect reads and changes only what your place on that team opens, in the Spaces shared with you.
Whatever it reads, and whatever you ask it, is handled by the company that makes the assistant (Anthropic for Claude, OpenAI for ChatGPT) under that company's own privacy policy. We don't control what happens on their side.
We keep a record of each action an assistant takes in your account and when. Posts and articles it prepares are stored like any others, and every post or newsletter it sends, every article it writes or publishes and every change it makes to your card, your website, your media kit or your Space's settings is labeled with its name.
You can see every assistant you've connected, and disconnect any of them, on the Assistants screen.
5. Your subscribers and your visitors
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.
Internet addresses a creator adds to their own Not counted list are kept so visits from them are not counted, until the creator removes them.
6. Screen logs and crash reports
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, check the problems people report to us, 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.
When a page crashes - in the dashboard, or on a creator's page for one of their visitors - the browser sends Tublish a short report: the page's address with anything private taken out, the error's own message, the browser's name and version, the language the page was showing and whether a translation tool had changed it, and which account was signed in, if any. We use it only to find and fix the crash, and it is cleared with the screen log.
These logs are cleared periodically.
7. Cookies and your browser
Tublish sets the cookies needed to keep you signed in, and a few small ones that remember choices you make in the dashboard - your language, how a chart is drawn, how far back you last looked. No advertising cookies, no cross-site tracking.
If you switch off counting for your own browser (Analytics, then Not counted), a cookie in that browser tells us not to count its visits to your Space. It holds your Space's ID and nothing else, and switching counting back on removes it.
Small conveniences (your pinned world-clock cities, your link-tagger history) live in your own browser's storage and never reach our servers.
8. Who else touches the data
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
- Brevo - sends the email Tublish itself sends: sign-in links, notices to creators, and the invitations creators send their teammates
- Google - if you choose Google sign-in, and YouTube's own services if you give Tublish your YouTube channel
- Outstand - our posting partner, which connects some platforms (Instagram, Facebook, Threads, TikTok and some YouTube channels) and delivers what you send to them
- The platforms you connect - they receive only the posts you send them
- An assistant you connect yourself (Claude, made by Anthropic, or ChatGPT, made by OpenAI, for example) - it receives what it reads from your account, under its maker's own policy
- Paddle.com - sells our paid plans as the Merchant of Record; your card details go to Paddle directly, never touch Tublish's servers, and are handled under Paddle's own privacy policy
No data brokers. No selling. No renting. Ever.
We'd hand over data only if the law genuinely compels it.
9. How long we keep things
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), the screen logs and the crash reports: cleared periodically.
10. Your rights
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.
11. Children
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.
12. Changes to this policy
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.
Escreva para a gente
Dúvidas, pedidos, preocupações: mande tudo pela página de contato.
Uma pessoa de verdade lê cada mensagem.