Privacy Policy

• Account details: your name, email address, profile image and sign-in identifier. If you sign in with Apple or Google, Hubly receives the name and email address that provider shares — with Apple, this may be a private relay address.
• Workspace content you create or upload: posts, captions, scenes, media, tags, templates, tasks, comments and team roles.
• Social accounts you choose to connect, and the posts, messages, comments and performance data Hubly reads from them to show in the inbox and analytics.
• Technical records needed to keep sessions secure, diagnose errors and run the service.

Hubly does not track you across other companies' apps or websites, does not sell personal information, and does not use your workspace content for advertising.

To sign you in, keep each team's workspaces separate, save your work, publish or schedule the posts you ask it to, show your inbox and analytics, and run the features you use. Nothing is published to a social network unless you ask for it.

Hubly relies on these processors, each receiving only what it needs for its part of the service:

• Supabase — accounts, sign-in and the main database.
• Vercel — hosts the website and Hubly's server, including the scheduled publishing jobs.
• Cloudflare R2 — stores the media files you upload.
• Anthropic — generates AI replies when you use the assistant to read attached files. Your prompt, the attached files and the workspace name are sent to Anthropic, using the API key you add yourself, and only after you allow it. In the iPhone, iPad and Mac apps the request goes straight from the app to Anthropic; on the website it passes through Hubly's server, which does not store it. You can withdraw that permission in Settings → AI.
• Social networks — Instagram, Facebook and Threads (Meta), YouTube and Google Business Profile (Google), TikTok, X, LinkedIn and Pinterest receive the content you publish through their official APIs and return the data Hubly shows you. Their own privacy policies apply to what they hold.
• Apple and Google — only when you choose to sign in with them.

When you connect a social account, the network gives Hubly an access token limited to the permissions shown on its consent screen. Hubly keeps these tokens on its server, encrypted, rather than on your device, because scheduled posts have to be published at the time you chose even when none of your devices is switched on. Tokens are never shown in the app or the browser. Disconnecting an account asks the network to withdraw Hubly's access where the network supports that, and deletes the stored token; you can also remove Hubly in the network's own settings at any time.

You can delete your account at any time in Hubly under Settings → Account → Delete Account. Deletion disconnects every social account and asks each network to withdraw access, cancels your scheduled posts, deletes the workspaces only you belong to together with their content and uploads, removes you from shared workspaces (their other members keep their work), signs out your devices and deletes your sign-in. If you are the only owner of a workspace other people still use, Hubly asks you to make someone else an owner first. Backups held by our providers expire on their normal schedule.

Information is kept while your account or workspace needs it, and deleted when you delete it. A workspace owner can remove members and their access from Workspace settings.

You may ask for a copy of your information, ask for it to be corrected or deleted, or object to how it is used. Most of this you can do in the app; for anything else, write to us at the address below. If you are in the EU, you may also complain to your data-protection authority.

Hubly uses verified sessions, encrypted token storage, private file storage and workspace-level access rules. No online service can promise absolute security. Material changes to this policy will be posted here with a new date.

Questions, requests and complaints: support@hubly.cz.