Privacy policy

Last updated 22 October 2026

This policy explains what personal information Sendhour collects, why, who it is shared with, how long it is kept, and the rights and choices you have. It covers the Sendhour website, the web app and the Sendhour API. Sendhour is a paid tool that schedules and publishes posts to social networks you connect (currently TikTok, YouTube, Instagram, Threads, Bluesky, X and LinkedIn).

In short: we collect only what we need to run the service, we use it only to run the service, we never sell it or use it for advertising, and you can delete everything at any time from Settings or by emailing [email protected].

Contents

1. Who we are
2. Information we collect
3. Information from social networks
4. How we use information
5. Legal bases (EEA and UK)
6. Google and YouTube
7. TikTok
8. Instagram and Threads (Meta)
9. Bluesky
10. X (Twitter)
11. LinkedIn
12. Reddit
13. Sharing and service providers
14. Requests from public authorities
15. International transfers
16. How long we keep information
17. Product analytics
18. Deleting your data
19. Your rights
20. Cookies
21. Children
22. Security
23. Changes to this policy
24. Contact

Who we are

Sendhour is operated by an individual developer. The operator is the "data controller" (under the GDPR and UK GDPR) and the "data fiduciary" (under India's Digital Personal Data Protection Act, 2023) for the personal information described here, except where we say another company is responsible.

Contact for anything in this policy, including privacy requests and complaints: [email protected].

Information we collect

We collect information from four sources: you, the social networks you connect, our payment provider, and your browser.

When you sign up and sign in

• Email address. Used as your login and to send you sign-in links and service messages. You can sign in with a one-time link sent to your email, Google or TikTok. We don't use passwords.
• Email sign-in links. Each link works once and expires after 15 minutes. We store only a one-way hash of the link, never the link itself, and delete the record a day after it expires.
• Google sign-in. If you choose "Continue with Google", Google tells us your Google account identifier and your verified email address, and we store both. Google's standard sign-in permission also shows us your name and profile picture; we don't store them.
• TikTok sign-in. If you sign in with TikTok, we receive your TikTok account's identifier (open_id), display name and avatar, and that account is connected to your workspace for posting.

When you set up your workspace

• Your answers: your first name, the website, app store page or public profile you give us, what you're growing, your first goal, what gets in the way and, if you tell us, how you heard about Sendhour.
• What your page says about itself: we read that public page once with a plain web request and keep its title, description, preview image, icon and theme colour, to tailor Sendhour to you. We don't run its scripts or follow you across the web.
• Your brand profile: after you subscribe, the page's text and your answers are used to write a short profile of your brand (description, audience, tone, content topics and colours) and your first post ideas. You can see it and read your site again in Settings.

When you connect a social network

• Account details that you approve on the network's own page: the account's identifier, name or username, and profile picture, so you can recognise the account in Sendhour. What each network shares is listed under Information from social networks.
• Access credentials that let Sendhour publish on your behalf: access and refresh tokens, or for Bluesky, your handle and an app password you create. They are encrypted with AES-256-GCM before they are stored.

When you create posts

• Your content: the videos, photos, text, captions and titles you upload or write.
• Post settings: the accounts and networks you choose, the scheduled time, and each network's options (such as privacy level, comment settings or content disclosures).
• Post records: status, error messages, and the post identifiers and links each network returns after publishing.
• API keys: if you create a Sendhour API key, we store only a hash of it and its first characters so you can recognise it.

When you subscribe

• Billing records: your plan, billing interval, subscription status and renewal date, and the customer and subscription identifiers from Dodo Payments. You give your card or other payment details directly to Dodo Payments; we never see or store them.

When you chat with us

• Chat messages: if you open the live chat, the messages you send and our replies are kept by Hailbell, our own chat service, which runs on Cloudflare. Our team reads and answers them in Discord, so Discord also holds a copy. If you are signed in, the chat also tells us your email address, your first name, your workspace identifier and your plan, so we know who is writing, and it notes the page you opened it from. The chat loads only when you open it.

From your browser

• Cookies that keep you signed in and protect sign-in (see Cookies).
• Technical data such as your IP address, browser type and the pages requested. Our hosting and network providers process this to deliver the site and block attacks. We don't build profiles from it.
• Usage information for product analytics: which of our public pages are visited (with the referring site and campaign tags), and which features are used in the app, such as signing up, connecting an account on a network, scheduling a post and whether it was published. These records use internal identifiers only, never your email, name or content. See Product analytics.

We do not collect sensitive personal information (such as health, religion or government ID numbers), and we don't buy data about you from anyone.

Information from social networks

Sendhour uses each network's official API and asks only for the permissions it needs to publish your posts and show you how your accounts and posts are doing. You approve them on the network's own page, and you can remove them there at any time.

For analytics we store numbers: counts such as views, likes, comment and share counts, followers and watch time, by day and by post. For TikTok we also store the caption, link and cover image of your public videos from the last 90 days, including ones you didn't publish with Sendhour, so you can see how all of them are doing; we delete them when a video is no longer public, is more than 90 days old, or you disconnect the account. We do not read or store who your followers are, your messages, the text of comments, or any other content of posts you didn't publish with Sendhour, and we do not post anything that you, or a tool you connected with your Sendhour API key, haven't scheduled. Tools and AI apps you connect, with an API key or by signing in to Sendhour from the app, can only see and manage your Sendhour posts and accounts, and you can disconnect them in Settings at any time. When you use an AI app such as Claude or ChatGPT, the account names, post text, media links and post statuses that Sendhour returns to it are processed by that app's provider under its own privacy policy. Sendhour receives only what the app sends to its tools, such as the post you asked it to schedule, not your conversations.

How we use information

• To create and secure your account and workspace, and sign you in.
• To connect your social accounts and publish each post, at the time you choose, only to the accounts you select for it.
• To show you your calendar, post history and each post's status, and tell you when something needs your attention.
• To show you analytics for the accounts you connect and the posts you publish with us.
• To make images, videos and post plans in the studio when you ask for them, and to keep track of your AI credits.
• To manage your subscription with our payment provider.
• To answer your support requests and send service messages such as sign-in links. We don't send marketing emails.
• To keep the service secure and working: preventing abuse, fixing errors and enforcing our terms.
• To understand how the service is used (for example, how many people sign up, which networks they connect and how often posts publish successfully) so we can improve it.
• To comply with legal obligations.

We do not use your information or your content for advertising, we do not sell it, and we do not use it to train artificial intelligence or machine learning models. Sendhour does not use automated decision-making that has legal or similarly significant effects on you.

Legal bases (EEA and UK)

If you are in the European Economic Area or the United Kingdom, we rely on these legal bases:

• Performance of a contract: to provide the service you signed up for, including sign-in, connecting accounts, publishing posts and billing.
• Legitimate interests: to keep the service secure, prevent fraud and abuse, fix problems, and measure how the service is used through privacy-friendly product analytics. These interests do not override your rights; you can object (see Your rights).
• Consent: when you connect a social account and approve its permissions. You can withdraw consent at any time by disconnecting the account.
• Legal obligation: where the law requires us to keep or disclose information.

For users in India, we process personal data on the basis of the consent you give when you sign up and connect accounts, and for the legitimate uses the Digital Personal Data Protection Act allows.

Google and YouTube

• Continue with Google reads only your Google account identifier and verified email address, to sign you in. We do not read your contacts, files or anything else in your Google account.
• YouTube: when you connect a channel we receive its identifier, name and picture so you can choose it in the composer, and access tokens that let Sendhour upload the videos you schedule to that channel with the title, description and visibility you choose. We use the YouTube permissions only to upload those videos, list your own channels, and show you analytics: your channel's subscriber count and daily views, watch time, likes, comments, shares and subscribers gained or lost (yt-analytics.readonly), and the view, like and comment counts of videos you published with Sendhour. We don't read your comments, subscriber list or other videos. Analytics data from YouTube is refreshed at least every 30 days or deleted, and is deleted when you disconnect the channel.
• Sendhour uses YouTube API Services. By connecting YouTube you agree to be bound by the YouTube Terms of Service, and Google's handling of your data is described in the Google Privacy Policy (https://policies.google.com/privacy).
• No third party serves content or advertisements through Sendhour, and Sendhour does not place cookies or similar technology for third parties.
• You can revoke Sendhour's access at any time from your Google account's third-party connections (also reachable at security.google.com/settings/security/permissions) or by disconnecting the channel in Sendhour. Disconnecting in Sendhour revokes our token with Google and deletes it immediately. See Deleting your data for what happens to the rest.
• Sendhour's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not sell this data, use it for advertising, or use it to train AI models, and people at Sendhour do not read it except with your permission, for security, or where the law requires.

TikTok

• Sendhour uses TikTok's official Login Kit and Content Posting API. The data we receive from TikTok, and what we use it for, is listed under Information from social networks.
• Before anything is posted you see a preview, choose the privacy level yourself, choose whether comments, Duet and Stitch are allowed, declare any commercial content, and confirm. Sendhour never posts to TikTok without that confirmation.
• TikTok data is used only to publish your content and show you its status and analytics (follower, view, like, comment and share counts). It is never sold, shared with anyone else, or used for advertising or profiling.
• TikTok's own handling of your data is described in the TikTok Privacy Policy.
• You can remove Sendhour's access in the TikTok app under Settings and privacy → Security and permissions → Manage app permissions, or by disconnecting the account in Sendhour, which also revokes our access token with TikTok.

Instagram and Threads (Meta)

• Sendhour uses the Instagram API with Instagram Login and the Threads API, provided by Meta. The data we receive, and what we use it for, is listed under Information from social networks.
• Instagram allows publishing only to professional (Business or Creator) accounts.
• We use this data only to publish your posts and show you their status and analytics (counts such as views, reach, likes, comments, shares and followers). We do not sell, license or buy Meta platform data, use it for advertising, or share it with anyone except as described in this policy.
• To publish media, Instagram and Threads fetch your uploaded files from Sendhour through private, unguessable links (see Sharing).
• You can remove Sendhour from Instagram (Settings → Website permissions → Apps and websites) or Threads (Settings → Account → Website permissions). When you do, Meta tells us, and we delete the access token and disconnect the account automatically. Meta's own handling of your data is described in the Meta Privacy Policy and the Threads Supplemental Privacy Policy.

Bluesky

• Bluesky connects with an app password you create in Bluesky's settings, never your main password. We encrypt it before storing it and use it only to sign in to your Bluesky server and publish the posts you schedule.
• Posts on Bluesky are public and are distributed across the AT Protocol network, so copies may be held by other servers and apps that Sendhour does not control. Deleting a post on Bluesky is handled by Bluesky.
• You can revoke access at any time by deleting the app password in Bluesky (Settings → Privacy and security → App passwords) or by disconnecting the account in Sendhour. Bluesky's own practices are described in the Bluesky Privacy Policy.

X (Twitter)

• Sendhour uses the X API v2 with OAuth 2.0. You sign in on X's own page and approve these permissions: tweet.read and users.read (read your profile and the public numbers of posts you published with Sendhour), tweet.write (publish the posts and threads you schedule), media.write (upload their photos and videos) and offline.access (stay connected until you revoke access).
• We store your X account identifier, name, username and profile picture, and encrypted access and refresh tokens. We don't read your timeline, followers list, likes, bookmarks or direct messages.
• X data is used only to publish your posts and show you their status and analytics. It is never sold, shared with anyone else, or used for advertising or profiling.
• You can remove Sendhour's access on X under Settings and privacy → Security and account access → Apps and sessions → Connected apps, or by disconnecting the account in Sendhour, which also revokes our tokens with X. X's own handling of your data is described in the X Privacy Policy.

LinkedIn

• Sendhour uses LinkedIn's official APIs: "Sign In with LinkedIn using OpenID Connect" and "Share on LinkedIn". You sign in on LinkedIn's own page and approve these permissions: openid and profile (your member identifier, name and picture, to show the account), email (LinkedIn includes your email address; we don't store it) and w_member_social (publish the posts you schedule).
• We store your LinkedIn member identifier, name and profile picture and encrypted access tokens. LinkedIn access tokens last 60 days; after that Sendhour asks you to reconnect. We don't read your connections, feed, messages, or posts you didn't publish with Sendhour.
• LinkedIn data is used only to publish your posts and show you their status. It is never sold, shared with anyone else, or used for advertising or profiling.
• You can remove Sendhour's access on LinkedIn under Settings → Data privacy → Permitted services, or by disconnecting the account in Sendhour, which deletes our tokens at once (LinkedIn offers no way for apps to revoke them). LinkedIn's own handling of your data is described in the LinkedIn Privacy Policy.

Reddit

• Sendhour uses Reddit's official Data API with OAuth 2.0. You sign in on Reddit's own page and approve these permissions: identity (your username, account identifier and avatar, to show the account), submit (publish the posts you schedule), read (look up subreddits and the score and comment count of posts you published with Sendhour), flair (the flair options a subreddit offers or requires) and mysubreddits (the subreddits you have joined). Reddit issues a long-lasting refresh token so the connection keeps working until you revoke it.
• We store your Reddit username, account identifier and avatar, encrypted access and refresh tokens, and for each post you publish, the subreddit, its Reddit identifier and link, and its score and comment count. Subreddit details (rules, allowed post types and flair options) are fetched when you write a post and kept for at most 24 hours.
• Sendhour only reads what it needs to publish your own posts. We don't collect or store other people's posts or comments, and we don't read your messages, votes, saved items, feed or browsing history. Sendhour never votes, comments or sends messages on Reddit, and never posts to an account you haven't connected.
• Reddit data is used only to publish your posts and show you their status and numbers. It is never sold, licensed or shared with anyone else, never used for advertising or profiling, and never used to train artificial intelligence or machine learning models. If you schedule a Reddit post from a connected AI app, Sendhour gives that app only what the post needs, such as a subreddit's rules and flair options, and the status of your own posts.
• If a post you published is deleted on Reddit, we remove its stored numbers when we next check it. You can remove Sendhour's access on Reddit at reddit.com/prefs/apps (under authorized applications, choose "revoke access"), or by disconnecting the account in Sendhour, which also revokes our tokens with Reddit. Reddit's own handling of your data is described in the Reddit Privacy Policy.

Sharing and service providers

We share personal information only as needed to run Sendhour, with:

To let networks fetch your media for publishing, uploaded files are reachable through long, random, unguessable links that are not listed or indexed anywhere and stop working when the file is deleted.

We may also disclose information when the law requires it, to protect the rights, safety or property of our users or others, or as part of a sale or reorganisation of the service (in which case this policy will continue to apply). We do not sell or share personal information for money or for cross-context behavioural advertising.

Requests from public authorities

If a court, police force, regulator or other public authority asks us for personal information about a user:

• We review each request to check that it is legally valid, comes from an authority entitled to make it, and is properly limited in scope.
• We challenge or refuse requests that we consider unlawful, overly broad or not properly issued.
• Where we must comply, we disclose only the minimum information the request legally requires.
• We keep a record of every request, our response, the legal reasoning and who was involved.
• We tell the affected user before disclosing, unless the law or a court order prohibits it or doing so would put someone at risk.

This applies equally to information we receive from the social networks you connect.

International transfers

Our servers are in Germany. Some providers above process data in the United States and other countries. Where personal data from the EEA or UK is transferred to a country without an adequacy decision, we rely on the safeguards our providers offer, such as the European Commission's Standard Contractual Clauses and the UK addendum, or the EU-US Data Privacy Framework where a provider is certified. Some providers above are described by the kind of service they provide; you can ask us at [email protected] for the names of the specific companies, or for more information.

How long we keep information

Encrypted backups of our database are kept for up to 30 days and then deleted, so data you delete disappears from backups within 30 days. Backups are used only to restore the service after a failure.

Product analytics

• We record product events, such as "signed up", "connected an account" or "a post was published", to understand how Sendhour is used and where it fails. Each event holds the network, plan or post type involved and an internal identifier for your workspace or user, never your email, name, captions, media or access tokens.
• These events are stored in our own database and sent to PostHog, our analytics provider. Analytics run on our server: there is no analytics script in your browser, no analytics cookies, and no tracking across other websites.
• Visits to our public pages (home, pricing, docs, legal pages, sign-in) are counted without identifying you: the visitor identifier is a one-way hash of your IP address and browser that changes every day, and it is not linked to your account. Your IP address is used to estimate an approximate location (such as the country), along with the referring site and campaign tags in the link.
• When you delete your workspace, the events in our database lose the link to your workspace and user and remain only as anonymous counts. You can ask us at [email protected] to delete the related PostHog records as well.

Deleting your data

You can delete your data at any time, in any of these ways:

• Delete your workspace: in Sendhour, open Settings → Delete workspace. This immediately disconnects every account (revoking our access with networks that support it), cancels any active subscription so you are not charged again, and permanently deletes your email, connected accounts, tokens, posts, media and API key (copies in our encrypted backups are gone within 30 days). It cannot be undone.
• Disconnect one account: open Accounts and choose Disconnect. We delete that account's tokens or app password immediately and revoke our access with TikTok, Google, X and Reddit, delete its name, username and picture, and cancel its scheduled posts. Your post history stays, labelled with the network's name, until you delete the workspace.
• Remove Sendhour on the network: TikTok (Settings and privacy → Security and permissions → Manage app permissions), Google (security.google.com/settings/security/permissions), Instagram (Settings → Website permissions → Apps and websites), Threads (Settings → Account → Website permissions), Bluesky (delete the app password), X (Settings and privacy → Security and account access → Apps and sessions), LinkedIn (Settings → Data privacy → Permitted services) or Reddit (reddit.com/prefs/apps). Sendhour then can no longer post to that account.
• Email us: write to [email protected] from the email address on your workspace and tell us what you want deleted. We will confirm and complete the deletion within 30 days, and usually much sooner.

Requests sent through Instagram and Threads. If you remove Sendhour from Instagram and Threads or ask Meta to delete the data Sendhour received, Meta sends us a deletion request and gives you a confirmation code. We act on it automatically: the account's access token, name, username and picture are deleted at once and the account is disconnected, so nothing more can be published or read. To also remove the related post history from your workspace, or to check the status of a request, email [email protected] with your confirmation code. If we cannot delete something (for example, because the law requires us to keep it), we will tell you why.

Deleting data in Sendhour does not delete posts already published on a network. Remove those on the network itself. Dodo Payments keeps the payment records it needs by law.

Your rights

Wherever you live, you can ask us to:

• tell you what personal information we hold about you and give you a copy, in a portable format where applicable;
• correct information that is inaccurate or incomplete;
• delete your information;
• restrict or object to how we use it, and withdraw consent you have given (for example, by disconnecting an account);
• not be discriminated against for using these rights.

Email [email protected]. We may need to confirm that the request comes from you, for example by replying from the email address on your workspace. We respond within 30 days. You can also use an authorised agent, who must show us your written permission.

EEA and UK. You have the rights above under the GDPR and UK GDPR, and you may complain to your local data protection authority (list of EU authorities) or, in the UK, the Information Commissioner's Office. We'd appreciate the chance to resolve your concern first.

California and other US states. In the past 12 months we collected identifiers (such as email and account identifiers), commercial information (subscription records), internet activity (IP address, requests and product usage, for security and product analytics) and the content you upload, for the purposes in How we use information, and disclosed them only to the service providers in Sharing. We do not sell or share personal information, as those terms are defined in the CCPA/CPRA, and we do not use or disclose sensitive personal information. Because we don't sell or share, no opt-out is needed, and we treat Global Privacy Control signals as a valid opt-out request anyway.

India. Under the Digital Personal Data Protection Act, 2023 you may access a summary of your data and how it is processed, have it corrected, completed, updated or erased, nominate someone to exercise your rights if you die or become incapacitated, and seek grievance redressal. Grievance officer: the operator of Sendhour, [email protected]. We acknowledge grievances within 2 business days and resolve them within 30 days. If you are not satisfied, you may complain to the Data Protection Board of India.

Cookies

Sendhour uses only cookies that are strictly necessary for the service. We use no advertising, analytics or tracking cookies, and no third-party scripts except our live chat, which loads only when you open it. Our product analytics (see Product analytics) run on our server and set no cookies.

If you open the live chat, it keeps a random identifier in your browser's local storage (hailbell.install.*), not a cookie, so your conversation carries on across pages and visits. It is stored only after you open the chat and stays until you clear your browser's site data.

Cloudflare, which protects our site, may set its own strictly necessary security cookies to tell people apart from malicious bots. Profile pictures of connected accounts are loaded from the network's own servers when you view them in the app. Because these cookies are strictly necessary, we don't ask for consent; you can block cookies in your browser, but you won't be able to sign in.

Children

Sendhour is for people aged 18 and over and is not directed at children. We do not knowingly collect information from anyone under 18. If you believe a child has given us information, email [email protected] and we will delete it.

Security

All traffic to Sendhour is encrypted with TLS (HTTPS). Access and refresh tokens and app passwords are encrypted at rest with AES-256-GCM, email sign-in links and API keys are stored only as hashes, and access to production systems is limited to the operator. Uploaded media is reachable only through unguessable links. No method of storage or transmission is completely secure, but if a breach affects your personal information we will notify you and the authorities as the law requires.

Changes to this policy

We will update this page and the "Last updated" date when this policy changes. If a change is material, we will tell active users by email or in the app before it takes effect. If we ever want to use your information for a new purpose, we will ask first where the law requires it.

Contact

Questions, requests or complaints about privacy: [email protected].