Privacy Policy

Mr Laith Al-Eissa operates CreatorCord and is responsible for how it handles personal information. For a privacy question or a deletion request, email laith.eissa4@gmail.com.

Visiting this site

These information pages have no tracking scripts, forms or advertising cookies. A website host receives your IP address and normal browser request information when it delivers a page. If you email support, your email address and message are used to answer you.

Using a creator workspace

Discord sign-in uses your Discord account ID to recognise you when you return. The dashboard uses a session cookie to keep you signed in. Connecting a Discord server is a separate choice. For the features you enable, CreatorCord uses server and channel IDs, selected roles, workspace permissions, counter settings and alert templates.

When you authorise a social account, the provider supplies account identifiers, granted permissions and credentials that let the service request updates while your dashboard is closed. Depending on the integration, the service records follower or subscriber counts, viewer or media statistics, collection times and public post details. Delivery records help prevent repeated announcements. Operational logs help diagnose failures.

What the TikTok test will read

If you join the sandbox and authorise access, CreatorCord will request your basic profile, follower count and list of public videos. Video IDs identify new uploads. Titles or descriptions and links can appear in the Discord channel you choose. Your existing videos provide a starting point for detecting new posts.

Who can see the information

The connected platform receives API requests for your account. Workspace members can use information available to their role. If you enable a Discord counter or alert, anyone with access to its destination channel can see it. Account credentials are used by the service and are separate from the statistics and messages it displays.

Why information is processed and kept

Account and workspace information is used to provide the features you request under the beta terms. Security and diagnostic records support the operator’s legitimate interest in protecting accounts and resolving failures. Historical measurements remain useful while you keep workspace history. Delivery records are needed while events may be retried. Support correspondence is kept as needed to resolve and follow up your request.

Disconnecting or deleting your data

You can stop future access through the provider’s account settings. Disconnecting an account, removing the Discord bot and deleting stored history are separate actions. To request deletion of your account or history, email laith.eissa4@gmail.com with your workspace name and the account concerned. We may ask you to verify ownership. Messages already delivered to Discord can be removed by someone with permission in that server.

Your choices and rights

You may ask to access, correct, delete or export your information, or restrict its use, where applicable. You may object to processing based on legitimate interests. Contact the operator about a concern or complain to your local data protection authority. In the UK you can contact the Information Commissioner’s Office.