This policy explains what information Hey Tasky collects, how we use and share it, and how you can manage it. It covers our website, app, and connections to ChatGPT, Codex, and other MCP clients.
Who we are
Hey Tasky (heytasky.com) is a social-media publishing and scheduling platform. It is a product of Red Brick Labs ("we", "us", "our"). Hey Tasky lets you write posts, schedule them, and publish them to the social networks you connect.
Information we collect
- Account information. When you sign up, our authentication provider collects your name, email address, and profile image. You can sign up with email and password or with Google sign-in.
- Workspace and social sets. We store your workspace name and timezone, and the names and channel membership of social sets you create. We use internal references to associate your workspace, channels, sets, and posts.
- Connected social accounts. When you connect an account, we store its platform, public handle, display name, avatar, connection status, and authorization tokens. Tokens are encrypted at rest using AES-256 GCM. We use them to publish your scheduled content, retrieve supported post metrics and public replies, and maintain your connection.
- Content you create. The posts, captions, media, and schedules you make in Hey Tasky.
- Published posts and performance. We collect post text, public post links, publication times, channel details, and available counts of impressions, likes, replies, reposts, and quotes. We use these to show results and calculate average engagement by weekday and hour.
- Public replies and their authors. We collect replies to your published posts, including reply text, authors' public names, handles and avatars, and reply times. We store the original post and channel details, whether a reply was read or handled, and classifications such as question, praise, or buying interest. We use this information to organize the reply feed.
- AI assistant. When you use the AI feature to draft a post, the text you provide is sent to our AI provider so it can generate the draft for you.
- Plugin connections. When you authorize an MCP client, we store the client registration, granted permissions, and connection records needed to authenticate it. We process the tool inputs it sends, such as post text, selected channels, dates, filters, and settings changes.
- Technical and usage data. Our infrastructure and analytics providers process page views, feature interactions, device and browser information, identifiers, timestamps, and error details to maintain the service. App analytics can associate events with your user and workspace references. When enabled, app session replay records interactions with input fields masked. Marketing analytics records page views and accepted waitlist submissions without session replay.
How we use your information
We use this information to authenticate you, manage your workspace, save drafts, schedule and publish posts, show results and public replies, recommend posting times, and run authorized plugin actions. We also use technical data to understand usage, investigate errors, and keep the service secure.
Data returned to ChatGPT, Codex, and other MCP clients
When you connect Hey Tasky to an MCP client, that client receives data from your authorized workspace. This happens when you request a tool action or use features such as the Post Queue, channel mentions, connection profile, or plugin settings. For ChatGPT and Codex, the recipient is OpenAI. Other clients receive the data through their own providers.
The returned data depends on the action:
- Workspace and connection identity. Workspace name and timezone. The connection profile also returns a stable workspace reference so the client can identify and distinguish connected accounts. It does not return the workspace owner's email or workspace slug.
- Channel selection and social sets. Social platform, display name, public handle, connection status, set names and membership, and channel or set references needed to target a draft or scheduled post. Channel mentions return those same public channel details and a resource link.
- Draft and scheduling confirmations. The saved post reference and draft status, or the post reference, selected channel references, and scheduled time. These confirm the action you requested.
- Post Queue. Post text, scheduled time, publishing status, and the target channel's platform, display name, and handle. The interactive queue receives the same fields, plus workspace name and timezone.
- Post results and best times. Published text, public post link, publication time, channel name, handle and platform, and available performance counts. Best-time results include timezone, weekday, hour, post count, and average engagement and impressions.
- Public replies. Reply text, author's public name and handle, reply time, platform, intent classification, high-signal flag, and whether the reply is handled. Each reply can include the original post's text and public link, plus channel name, handle, and platform. Reply avatars, read timestamps, handling timestamps, and internal reply or published-post references are omitted.
- Plugin settings. Workspace name and timezone, including values you change through the client.
Post text and public replies can contain personal information. These fields are returned when needed for the requested publishing, queue, results, or reply action. Tool responses, including nested fields and interactive view data, use only the fields described above. They do not include stored authentication secrets, raw logs, debug payloads, or internal analytics and request identifiers. Error responses use fixed messages rather than raw backend errors.
The receiving client's own privacy policy governs its processing of the data it receives. OpenAI's policy is available at openai.com/policies/privacy-policy. Connecting the plugin does not give Hey Tasky access to unrelated conversations in that client.
How we share it
We do not sell your personal data. We rely on a small set of service providers (subprocessors) to operate Hey Tasky:
- Clerk: authentication and account management.
- Railway: database hosting and backend infrastructure.
- Cloudflare: hosting, compute, and media storage.
- Anthropic: AI text generation for the assistant.
- PostHog: usage analytics, error tracking, and app session replay when enabled.
- OpenAI and other MCP client providers you authorize: the workspace data described in the plugin section above.
- The social networks you choose to publish to: we send your content to them on your instruction so it can be posted to your accounts.
Permissions and tokens
When you connect a social account, we request permissions for supported publishing, profile, performance, and public-reply features. We do not read your private messages or direct messages. You can disconnect a social account in Hey Tasky to stop using that connection.
MCP connections request permissions to read posts, write drafts and schedules, and read connected channels. Settings updates also require write permission. Review the consent screen before connecting. You can disconnect Hey Tasky in the client to stop using the plugin. Disconnecting it does not delete your workspace or cancel posts already scheduled in Hey Tasky; manage those posts in the Hey Tasky app.
Data retention and deletion
You stay in control of your data. You can delete your content, disconnect any account, or delete your entire account at any time. When you delete your account, we remove your data and your stored tokens. You can also email us to request deletion and we'll take care of it.
Security
Data is encrypted in transit over HTTPS, and the access tokens for your connected accounts are encrypted at rest. We work to protect your information, though no method of storage or transmission is ever completely secure.
Your rights
You have the right to access, correct, delete, and export your data. You can do most of this directly inside Hey Tasky, or contact us and we'll help. Depending on where you live, you may have additional rights under laws such as the GDPR or CCPA. We honor these requests.
Cookies
We use session and authentication cookies to keep you signed in. Analytics can also use cookies or local storage to recognize visits and associate app activity. Our analytics configuration respects the browser's Do Not Track setting. We do not use advertising cookies.
Children
Hey Tasky is not directed to anyone under the age of 16, and we do not knowingly collect information from children under 16.
Changes to this policy
We may update this policy from time to time. When we do, we'll revise the "Last updated" date above to reflect the latest version.
Contact
For questions or data requests, email [email protected].