Spider Social

Trust & transparency

Privacy Policy

What information we handle, why we need it, and the choices you have when using Spider Social.

Last updated September 30, 2026

1. Who this policy covers

This policy covers Spider Social at spidersocial.dev, including its website, publishing tools, workspaces, and API. It applies to visitors, account holders, and workspace collaborators. For account administration and website operations, the operator acts as the data controller. When a customer provides content containing other people’s information, we process that content to provide the service on the customer’s instructions.

Spider Social is operated by Engone Nze Davy.

For questions or requests about these terms, privacy, or data deletion, email davy@hackages.com. Include your account email and the relevant workspace or connected channel. Never send passwords or access tokens.

2. Information we handle

  • Account and access information: your name, email, profile image, sign-in identifier, waitlist status, workspace membership, roles, and invitations.
  • Connected channel information: platform account identifiers, names, profile images, granted permissions, access tokens, refresh tokens where provided, and token expiry information. Social account passwords are entered with the platform, not provided to Spider Social.
  • Content and collaboration: captions, images, videos, documents, brand information, prompts, generated assets, drafts, schedules, approval decisions, review comments, and publishing history.
  • Platform responses: post identifiers, links, publishing errors, and available engagement metrics such as views, likes, comments, and shares.
  • Technical information: request and error logs, browser and device information, network information such as IP addresses, and website usage statistics. We also retain messages you send us for support.

3. How and why we use information

We use information to authenticate you, manage access, connect your channels, store and create content, run approval workflows, publish and schedule posts, display analytics, send service notifications, and respond to requests.

Where applicable data protection law requires a legal basis, we rely on performance of our contract for requested services; legitimate interests for security, abuse prevention, troubleshooting, and improving reliability; consent where required for optional processing; and legal obligations where we must retain or disclose information. You can withdraw consent without affecting processing that occurred before withdrawal.

4. Who receives information

Content and channel information are shared with the social platforms you choose and with people granted access to your workspace. Public posts are visible according to the audience you select on the platform. Media delivery URLs let publishing platforms fetch attached files; anyone who obtains a working delivery URL may be able to access that file.

Service providers process information to operate Spider Social: Clerk for authentication, MongoDB for database storage, AWS and Vercel for hosting or media storage, Resend for email, and Vercel Analytics for website usage measurement. Enabled AI features may send prompts and selected assets to providers such as OpenAI or ElevenLabs. Connected GitHub features access the repositories you authorize. The information sent depends on the feature you use.

We may also disclose information when required by law, to protect users and the service, or as part of a business transfer subject to applicable protections. Service providers and platforms may process information outside your country. Where required, international transfers must be covered by an adequacy decision or appropriate contractual safeguards.

5. Connected platforms and YouTube

Spider Social uses YouTube API Services for its YouTube integration. Google’s handling of information is described in the Google Privacy Policy. You can revoke access through Google’s account permissions page. Other connected platforms also provide controls to remove an app’s access.

Revoking access at a platform prevents future authorized access but does not itself remove data already stored in Spider Social. Disconnect the channel in Spider Social or request deletion as described below. Removing a connection does not delete posts already published on the social platform.

6. Storage, retention, and security

We retain account and workspace information while needed to provide your account and collaboration features. Drafts, scheduled content, and publishing records are retained to support the workflow and history until removed. Retention also depends on outstanding support requests, security needs, legal obligations, and the applicable platform’s data rules.

Disconnecting a channel removes its stored credentials and associated post records, and removes attached media that is not referenced elsewhere. Assets shared with other posts or stored separately in a workspace may remain. Backups and service-provider logs may persist beyond deletion from the active application until their retention cycles expire.

Social access and refresh tokens are encrypted at rest. Access controls restrict workspace operations. No storage or transmission method is completely secure; protect your account, API keys, and workspace invitations.

7. Cookies and browser storage

Authentication uses cookies to maintain sessions and secure sign-in. Browser storage remembers preferences such as your selected theme. Vercel Analytics measures website usage. You can manage cookies and site storage through your browser; blocking authentication cookies may prevent sign-in.

8. Your choices and deletion requests

You can edit or delete content in Spider Social, disconnect channels, revoke platform permissions, and control workspace access according to your role. For account deletion or information not removable through the interface, contact the operator below. We may need to verify your identity and authority over a workspace before acting.

Depending on your location, you may have rights to access, correct, erase, or receive a portable copy of your personal information, restrict processing, object to processing based on legitimate interests, and withdraw consent. We respond within the deadlines required by applicable law. You may also complain to your local data protection authority. Shared workspace records and information required by law may be subject to exceptions.

Spider Social is operated by Engone Nze Davy.

For questions or requests about these terms, privacy, or data deletion, email davy@hackages.com. Include your account email and the relevant workspace or connected channel. Never send passwords or access tokens.

9. Children

Spider Social is intended for adults managing social content and is not directed to children under 18. If you believe a child has provided personal information, contact us so we can investigate and address it.

10. Changes to this policy

We will update this page when our practices change and revise the date above. Material changes will be brought to users’ attention through an appropriate service notice or email where required.