Privacy Policy
The short version
- Bugle publishes and schedules posts to social media accounts that their owners connect themselves. We only post content that you, or an app you use, submit, and only when you say so.
- We store what we need to do that: your login, the accounts you connect (with encrypted access tokens), the posts you create and their results.
- We never sell personal data, never use platform data for advertising and never use it to train AI models.
- You can disconnect any account at any time. Its access tokens are deleted immediately. You can ask us to delete everything; see Data deletion.
- Bugle uses YouTube API Services. By connecting YouTube you also agree to the YouTube Terms of Service, and Google's processing is covered by the Google Privacy Policy.
- Who we are
- Who this policy covers
- What data we process
- Why we process it (legal bases)
- How we use data from each platform
- Google and YouTube
- Facebook, Instagram and Threads
- TikTok
- X, LinkedIn, Pinterest and Bluesky
- Who receives data
- Transfers outside the EU
- How long we keep data
- Security
- Your rights
- Cookies and device storage
- Children
- Changes to this policy
1. Who we are
Bugle is operated by Yasin Sen, a sole proprietor (Einzelunternehmer) in Germany. He is the controller responsible for your data under the EU General Data Protection Regulation (GDPR).
Yasin Sen, BugleUtestraße 7
53179 Bonn
Germany
Email: yasinsen.job@gmail.com
Phone: +49 155 68730584
We are not required to appoint a data protection officer. Send any privacy question or complaint to the email address above. We reply within one month at the latest, usually much sooner.
2. Who this policy covers
- Website visitors of bugle.pro.
- Bugle users: people and companies who sign up for Bugle, use the dashboard or call the Bugle API with an API key (we call API users "customers").
- Account owners: people who connect a social media account to Bugle, either in the Bugle dashboard or through an app that a customer built on Bugle.
When you connect an account in the Bugle dashboard, we are the controller. When you connect an account through a customer's app, that customer decides what is posted to your account and when. In that case we process your data on the customer's behalf as a processor (Art. 28 GDPR), and the customer's own privacy policy applies as well. We still follow every rule in this policy, the platforms' terms and the security measures described below.
3. What data we process
Website visitors
Our website is hosted by Vercel. When you open a page, Vercel's servers process your IP address, the date and time, the page requested, the referring page and your browser's user agent in order to deliver the page and protect it against abuse. We do not use analytics, advertising or tracking tools on the website, and fonts are served from our own domain.
Bugle users
- Sign-in data: email address, password (stored only as a hash by our authentication provider) and, if you choose to sign in with Google or GitHub, the name, email address and account ID that provider shares with us.
- Project data: project and profile names, the team members you invite, API keys (we store only a hash and a short prefix) and when a key was last used.
- Settings you provide: webhook URLs and their secrets, and, if you bring your own platform app (BYOK), its client ID and client secret. Secrets are encrypted.
- Messages you send us, for example support emails.
Connected social media accounts
- Account details received from the platform: your user or channel ID, username, display name and profile picture link, and for Facebook the Pages you choose to connect.
- Authorization data: the access and refresh tokens the platform issues, their expiry and the permissions you granted. Tokens are encrypted with AES-256-GCM and are never shown in the dashboard or returned by the API.
- Posting options that the platform provides when you create a post, for example the TikTok privacy options and maximum video length for your account, or your Pinterest boards.
Content you publish
- The text, links, images and videos you submit, the options you choose per platform (for example a YouTube title, tags and privacy setting) and the scheduled time and time zone.
- The result of each post: the platform's post ID and link, its status and any error message.
Content you publish may contain personal data about you or others. You decide what you publish and are responsible for having the right to publish it.
Technical logs
Our servers log requests (IP address, time, request path, response status and error details) to keep the service secure and to fix problems.
4. Why we process it (legal bases)
| Purpose | Legal basis |
|---|---|
| Creating and running your Bugle account, connecting social accounts, publishing and scheduling the posts you ask for, sending webhooks you set up | Contract (Art. 6(1)(b) GDPR) |
| Processing data of account owners who connect through a customer's app | On the customer's behalf, under our data processing terms (Art. 28 GDPR) |
| Delivering the website, security logs, preventing abuse and spam, keeping the service stable | Legitimate interests (Art. 6(1)(f) GDPR) in a secure and working service |
| Answering your messages | Contract or pre-contract steps (Art. 6(1)(b)), otherwise legitimate interests (Art. 6(1)(f)) |
| Keeping records we must keep by law, for example invoices once paid plans start | Legal obligation (Art. 6(1)(c) GDPR) |
We do not use automated decision-making or profiling that has legal or similarly significant effects on you.
5. How we use data from each platform
These rules apply to every platform:
- We use platform data only to provide the features you can see in Bugle: connecting an account, showing which account is connected, preparing a post with the options the platform allows, publishing or scheduling it, and showing its result.
- We publish only content that you or the app you use submit, to an account its owner connected, either right away or at the time you set. Bugle never posts, likes, follows, comments or sends messages on its own.
- Bugle is for publishing your own content or content you have the rights to. It does not search for, download or repost other people's content.
- We do not read your private messages, and we do not collect your followers, contacts or analytics.
- We never sell platform data, never use it for advertising or to build profiles, and never use it to train or improve AI or machine learning models.
- Our staff look at platform data only when you ask us to (for example in a support request), when it is needed for security or to investigate abuse, or when the law requires it.
The table on our home page lists every permission Bugle asks each platform for.
6. Google and YouTube
Bugle uses YouTube API Services. By connecting a YouTube channel you agree to the YouTube Terms of Service. Google processes data under the Google Privacy Policy.
What we access and why
youtube.readonly("View your YouTube account"): we read your channel ID, channel name and channel picture so the dashboard can show which channel is connected.youtube.upload("Manage your YouTube videos"): we upload the videos you choose to your channel, with the title, description, tags, category, "made for kids" setting and privacy status you select. We do not edit, delete or download your existing videos.
What we store and share
We store your channel ID, channel name, channel picture link, the encrypted tokens, the videos you submit until they are published, and the ID and link of each uploaded video. We do not share YouTube data with anyone except Google, our processors listed in section 10, and you.
When you connect YouTube in the Bugle dashboard, Bugle's own Google project is used and the data is used only within Bugle. Apps that customers build on the Bugle API connect YouTube with the customer's own Google project. For those connections, the customer's app is the API client, its own privacy policy applies, and we process the data only on its behalf.
Limited Use
Bugle's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular, we use Google user data only to provide or improve the user-facing features described above. We do not transfer it to others except as needed to provide those features, to comply with the law or as part of a merger or acquisition. We do not use it for advertising, and people do not read it except as described in section 5.
Storage limits and deletion
- Channel details we store are refreshed or deleted at least every 30 days.
- If you disconnect YouTube in Bugle, we revoke the token with Google straight away, delete the tokens immediately and delete the remaining YouTube data we hold within 7 days.
- You can also revoke Bugle's access at any time on the Google security settings page: https://security.google.com/settings/security/permissions. When we detect that access was revoked there, we delete the stored YouTube data within 30 days at the latest.
- To ask for deletion of all your data, see Data deletion or email us. We complete deletion requests within 7 days.
For privacy questions or complaints about how Bugle uses YouTube data, contact us at yasinsen.job@gmail.com.
7. Facebook, Instagram and Threads
- Facebook Pages (
pages_show_list,pages_read_engagement,pages_manage_posts): we read the list of Pages you manage, with their names, IDs and pictures, so you can choose which Pages to connect. We store a Page access token for each Page you connect and publish the posts you submit to it. We do not post to personal profiles or groups. - Instagram (
instagram_business_basic,instagram_business_content_publish): we read your professional account's ID, username and profile picture, and publish the photos, videos, carousels and stories you submit. Instagram fetches the media from a temporary link on our server. - Threads (
threads_basic,threads_content_publish): we read your Threads ID, username and profile picture, and publish the text, images and videos you submit.
You can remove Bugle's access in Facebook under Settings & privacy → Settings → Business integrations, in Instagram under Settings → Website permissions → Apps and websites, and in Threads under Settings → Account → Website permissions. How to delete your data is described on our data deletion page.
8. TikTok
user.info.basic: we read your TikTok open ID, nickname and avatar to show which account is connected.video.publishandvideo.upload: when you create a post, we load your current creator information from TikTok (nickname, the privacy levels you can choose from, whether comments, Duet and Stitch are allowed, and the maximum video length). We then publish the video or photos only after you have chosen who can see the post and confirmed it. If you choose "send to inbox", the post goes to your TikTok inbox as a draft that you finish in the TikTok app.
We do not download or collect your existing TikTok videos. You can remove Bugle's access in the TikTok app under Settings and privacy → Security and permissions → Manage app permissions.
9. X, LinkedIn, Pinterest and Bluesky
- X (
tweet.read,tweet.write,users.read,media.write,offline.access): we read your user ID, username, name and profile picture, and publish the posts and media you submit. X requires that customers use their own X developer app; the account is connected to that app. - LinkedIn (
openid,profile,w_member_social): we read your member ID, name and profile picture, and publish the posts you submit to your personal profile. - Pinterest (
user_accounts:read,boards:read,pins:read,pins:write): we read your username and profile picture and your board list so you can choose a board, and we create the Pins you submit. - Bluesky: you connect with an app password that you create in Bluesky. We store it encrypted, use it only to publish the posts you submit, and you can revoke it in Bluesky's settings at any time.
10. Who receives data
The platforms you publish to
When you publish, we send your content and options to the platform you chose. From then on the platform's own terms and privacy policy apply to the published content.
The app you connected through
If you connect an account through a customer's app, that customer can see the account's ID, platform, username, display name, profile picture and connection status, and the status and links of the posts it created. Customers never receive your access tokens or passwords.
Our processors
We use these service providers, bound by data processing agreements under Art. 28 GDPR:
| Provider | What they do for us | Where |
|---|---|---|
| one.com | Cloud server that runs the Bugle API and worker, stores uploaded media temporarily and keeps nightly backups | EU |
| Supabase | Main database, sign-in and sign-in emails | EU (Ireland); Supabase Inc. is a US company |
| Vercel | Hosting of this website and its technical logs | EU and USA; Vercel Inc. is a US company |
If you choose to sign in with Google or GitHub, that provider handles the sign-in under its own privacy policy.
Others
We disclose data to authorities only when the law requires it. We do not sell or rent personal data to anyone.
11. Transfers outside the EU
Some providers are US companies or process data in the USA. Where data leaves the EU or EEA, we rely on an adequacy decision, including the EU-US Data Privacy Framework where the provider is certified, or on the EU Standard Contractual Clauses. The social media platforms you publish to may process data worldwide under their own terms.
12. How long we keep data
| Data | How long |
|---|---|
| Access and refresh tokens | Until you disconnect the account or revoke access. Deleted immediately on disconnect. |
| Connected account details (ID, name, picture) | While the account is connected, refreshed at least every 30 days. Deleted within 7 days after you disconnect, or within 30 days after we detect that access was revoked on the platform. |
| Uploaded media files | Until the post is published or cancelled, then deleted within 30 days. |
| Posts and their results | Until you delete them, the profile or the project, or ask us to delete them. |
| Bugle account and project data | Until you delete your account. After that we delete it within 30 days, except records we must keep by law. |
| Server logs | Up to 30 days. |
| Backups | 14 days, then overwritten. |
| Invoices and other accounting records (once paid plans start) | As required by German tax law (up to 10 years). |
13. Security
- All traffic is encrypted with HTTPS (TLS).
- Platform tokens, app secrets and webhook secrets are encrypted with AES-256-GCM before they are stored. API keys are stored only as hashes.
- The database connection uses verified TLS. Access to servers is limited to the operator and protected with SSH keys.
- Webhooks are signed with HMAC-SHA256 so customers can verify they come from us.
If a data breach is likely to put your rights at risk, we will inform the competent authority and, where required, you.
14. Your rights
Under the GDPR you have the right to:
- access the data we hold about you (Art. 15) and receive a copy in a portable format (Art. 20);
- have incorrect data corrected (Art. 16) and have data deleted (Art. 17);
- restrict processing (Art. 18);
- object to processing based on legitimate interests (Art. 21);
- withdraw consent you gave, with effect for the future (Art. 7(3));
- lodge a complaint with a supervisory authority (Art. 77), for example the one responsible for us: Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW), Kavalleriestraße 2–4, 40213 Düsseldorf, Germany, www.ldi.nrw.de.
To use these rights, email yasinsen.job@gmail.com. If you connected through a customer's app, you can also contact that customer; we will help them answer your request.
15. Cookies and device storage
The website sets no cookies. It uses your browser's session storage only to remember that you closed a notice; this stays on your device. The dashboard stores your sign-in session in your browser's local storage so that you stay signed in. Both are strictly necessary for features you use, so no consent banner is needed. No third party serves content or ads on our website or dashboard.
16. Children
Bugle is not meant for children. You must be at least 16 years old, and old enough under the rules of each platform you connect, to use it.
17. Changes to this policy
We update this policy when our service or the law changes. The date at the top shows the latest version. If a change significantly affects how we use your data, we will tell signed-in users by email or in the dashboard before it takes effect.