Hey Tasky

Privacy Policy

Last updated: October 28, 2026

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

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:

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:

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].