Privacy Policy
What Distrobell collects when you sign in and connect your Facebook, Instagram, and YouTube accounts, what we keep about visitors to these pages, who else receives any of it, and how to remove everything.
1. What this policy covers
This policy explains what Distrobell collects when you use Distrobell, why, who else sees it, and how to remove it. Distrobell plans, generates, reviews, and publishes content — images and captions, and music videos — to the Facebook Pages, Instagram accounts, and YouTube channels you connect yourself. It also covers visitors to our public pages, who are not signed in at all.
2. Information we collect
In summary: who you are, from signing in with Google; which destinations you connect, and the tokens needed to publish to them; the briefs, references, and generated content in your workspace; a record of every publishing attempt; the keys you supply for AI providers; and aggregated, pseudonymous statistics about visits to our pages. Each is described below. We do not collect payment details, we do not buy data about you, and we have no advertising or cross-site tracking of any kind.
3. Signing in
Signing in is done through Google, and it is the only way into the product — Facebook Login no longer signs anyone in. We ask for the sign-in scopes openid, email, and profile, which give us an account identifier, your email address, your name, and your profile picture. Your email address identifies your workspace and is how we would contact you about your account. Signing in gives us no access to Gmail, Drive, Calendar, contacts, any other Google service, or YouTube.
4. Connecting your social accounts
Each connection is a separate, optional step with its own consent screen, and you can decline any of them and still use the rest of Distrobell. For a YouTube channel we ask for two scopes: youtube.readonly, used solely to list the channels on your account so you can see where a video would go, and to read back the processing state, visibility, and thumbnail of a video we uploaded for you when you ask to check it; and youtube.upload, used solely to upload the videos you approve. For a TikTok account we ask for two scopes: user.info.basic, used solely to show you which account you connected (its display name and picture), and video.publish, used solely to post the videos you approve to that account. For Facebook and Instagram we ask for the Page and publishing permissions you approve, then read the list of Pages your Meta account manages and, for each Page, the Instagram Professional account linked to it. For every destination we store its identifier, name or title, handle, picture, and the permissions you hold on it — enough to show you where content would go and to send it there. We only ever reach accounts you connect, and only while the connection remains.
5. What we never read
Connecting an account does not open the rest of it to us. We do not read your YouTube watch history, subscriptions, comments, analytics, or any video we did not upload for you. We do not read your personal Facebook feed, your friends, or your messages. We do not request your Google contacts, mail, or files. The permissions listed on each consent screen are the whole of what we can do.
6. The platforms you connect to
Distrobell uses YouTube API Services to list your channels, upload videos, and check the status of the videos it uploaded, and Meta's Graph API to discover Pages and publish posts. Those platforms have their own terms and their own privacy practices, which govern the data you hold with them and which we cannot change. By connecting a YouTube channel you are also agreeing to the YouTube Terms of Service, at https://www.youtube.com/t/terms and you should read Google's Privacy Policy, at https://policies.google.com/privacy alongside this one. For Facebook and Instagram, the equivalent is Meta's Privacy Policy, at https://www.facebook.com/privacy/policy and the terms of the platform you publish to.
7. Access tokens and AI provider keys
Publishing needs credentials: access tokens from Meta for Pages and Instagram, from Google a refresh token that lets us mint short-lived upload tokens when a video is ready, and from TikTok a refresh token that lets us mint short-lived posting tokens when a video is ready. Generation needs the AI provider keys you supply — for images, and for music. All of these are encrypted before they are stored, using AES-256-GCM with a key held only on the server, and all are used solely on the server for requests belonging to your own workspace. They are never sent to your browser, never written to logs, and never returned by our API.
8. Content you create
We store the projects and campaigns you create, their names, descriptions, and briefs, the reference images you upload, and the content generated for you — images and captions, and for a music project the generated song, the poster drawn for it, the encoded video, and the title, description, and tags prepared for the upload — together with the prompts used to produce them and the schedule that triggered each run.
9. Publishing records
For every attempt to publish we record the destination, whether it succeeded, the identifier and link of the resulting post or video, and any error the platform returned. This is what lets you see per-destination results and retry a failure. Attempts made while an account is in dry-run mode are recorded without anything being sent to the platform.
10. Visitors to our public pages
We keep basic statistics about visits to our pages, including from people who are not signed in. Each visit contributes the page path, the language your browser asks for, whether you are on mobile, tablet, or desktop, your browser and operating system family, the hour, the site that referred you, and a country and city. These are stored only as daily totals, kept for forty days, and are used to understand traffic — never to build a profile of you, and never for advertising.
11. How visitors are counted without keeping addresses
Counting distinct visitors normally means storing IP addresses. We do not store them. Your address is used twice at the moment of the visit — once to derive a country and city, and once to compute a short pseudonym — and is then discarded. The pseudonym is a keyed hash under a salt that changes every day and is never written down, so the same visitor can be counted once within a day but cannot be recognised across days, and yesterday’s pseudonyms cannot be recomputed. Resolving the country sends your address to ipwho.is, an external lookup service; addresses on private or local networks never leave our server. This is done without cookies of any kind.
12. Cookies
Distrobell sets one cookie, to keep you signed in. It holds a signed reference to your account, is restricted to our own site, cannot be read by scripts in your browser, and expires after thirty days. We set no advertising, analytics, or tracking cookies, and we do not track you across other sites.
13. How we use information
Information is used only to run the service you asked for: to sign you in, to show your connected destinations, to generate and schedule content, to publish or upload where you approve, to report results back to you, to understand traffic in aggregate, and to diagnose failures. Distrobell's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, at https://developers.google.com/terms/api-services-user-data-policy including its Limited Use requirements; we apply the same standard to everything received from Meta. We do not sell your information, we do not use it for advertising, and we do not use your content, your credentials, or data obtained from any platform API to train AI models.
14. Who else receives data
Uploading to YouTube and listing channels happen through Google’s APIs, so the video, its title, description, and tags, and your channel selection are sent to Google. Publishing and Page discovery happen through Meta’s APIs, so the content and destinations you choose are sent to Meta. Posting to TikTok happens through TikTok’s Content Posting API, so the video, its caption, and the visibility, interaction, and disclosure choices you make are sent to TikTok. Image generation sends your briefs, reference images, and prompts to the AI provider whose key you connected. Video generation sends your prompt, and for models that start from a picture the first reference image you added, to Replicate, which runs the video model. If you switch the optional automation agent on, the instructions it researches are sent to our own research service, which runs separately and itself calls an AI provider. Visitor addresses are sent to ipwho.is for country lookup, as described above. Aggregated usage and traffic totals — never addresses, never your content — are served to our own internal reporting system over an authenticated connection. We do not share your data with anyone else, and none of these are advertising networks or data brokers.
15. How media is stored
Reference images you upload, and the images, audio, and video generated for you, are stored as files and served from our media paths. Anyone holding the direct link to a file can open it without signing in, so treat those links as you would any unlisted URL and avoid uploading material that must remain confidential.
16. Retention and deletion
Workspace information is kept while your account exists and for as long as it is needed to run the service. Visitor statistics are kept for forty days and then dropped. You can disconnect a Google or Meta account, switch off a single destination, remove an AI provider key, or archive a project at any time, and you can ask us to delete your account and everything we hold. Disconnecting revokes the token with the provider as well as clearing it here. Verified deletion requests are completed within 30 days. Step-by-step instructions are on our Data Deletion page.
17. Your choices and controls
You may ask for a copy of your data, ask for it to be corrected, withdraw a connection, or ask for deletion, by writing to mountainmediacontact@gmail.com. You can also remove our access yourself at any time, from the platform rather than from us: for Google and YouTube at https://myaccount.google.com/permissions and for Meta in Facebook’s Apps and Websites settings. Either takes effect immediately and invalidates the tokens we hold for that account.
18. Security
Tokens and provider keys are encrypted at rest, credentials are handled only on the server, and access to your workspace is limited to your own signed-in account. No service can promise perfect security, and we do not claim to; if we become aware of a breach affecting your data we will inform you.
19. Children and changes
Distrobell is not intended for children. We may update this policy as the product changes and will revise the date at the top when we do; material changes will be communicated in the product.
20. Contact
For questions about this policy or about your data, contact Distrobell at mountainmediacontact@gmail.com.