creatent.
CREATENT / PRIVACY

Your workspace. Your information.

Last updated October 5, 2026. How information is handled in the current Creatent workspace.

Worker identity and US residency checks

Workers complete government ID, selfie, and residence evidence checks through Persona when connected. Persona processes identity documents and biometric data under its own notices and consent flow. The owner reviews results and current US residence evidence in the provider dashboard. Creatent stores provider inquiry identifiers, verification status, environment mode, reviewer decisions, and review timestamps, not ID images, selfies, ID numbers, or residential address details. A document’s issuing country does not establish residence. Workers can contact support for correction, review, or deletion requests without sending identity documents in messages.

Worker email and SMS tools

When MailSlurp is connected, Creatent stores each assignment’s inbox identifier, email address, phone identifier, number, and provisioning status. Received message text is fetched from MailSlurp when requested and is not saved in the Creatent database. The owner and the assigned worker can access messages during active or submitted work; worker access ends on approval. The owner retains access for handoff and account recovery. The provider has its own storage and retention practices.

What this workspace stores

Creatent stores your name, email, account role, region, password hash, login sessions, order estimates, service briefs, saved social-account links, support requests, and replies. Worker accounts can also store a payout email and work/payment records. Customer accounts do not have worker payout profiles.

How information is used

Information supports sign-in, order coordination, delivery review, support, and account security. The owner can review service and support records. Assigned workers can see the briefs and content links needed for their work. Other customers cannot read your private orders or support requests through the workspace.

Cookies and infrastructure

Essential cookies keep you signed in and protect sign-in flows. The workspace is hosted through Sites on Cloudflare infrastructure and stores application records in its database. Submitted content links are links to external services; opening them is subject to those services’ own privacy practices.

Worker PayPal payments

Workers can confirm a PayPal email and enroll in weekly payouts. Creatent stores enrollment, confirmation time, payout amounts, recipient snapshots, provider batch and item references, and payment statuses. PayPal processes payment information under its own policies. Payout history stays linked to the worker and visible to the owner. No PayPal passwords are collected. The earnings ledger tracks money owed; it does not create an escrow account or hold money.

Payments and connected services

When Stripe is connected, payment and card setup take place on Stripe-hosted pages. Creatent stores Stripe customer and session identifiers, order amounts, payment status, and refund amounts. It can display masked card details received from Stripe. Creatent does not store full card numbers or card security codes. Do not submit card numbers or banking credentials in briefs or support requests. The app does not currently connect directly to TikTok or Instagram to create accounts or publish posts.

Your requests

You can update your name and region in Profile settings. For access, correction, or deletion questions, send a private support request. Requests are reviewed manually; retention and deletion depend on the records involved and applicable requirements. There is no automatic account deletion feature yet.

Information to keep out of the workspace

Do not place social passwords, login codes, sensitive identity documents, or payment credentials in briefs or tickets. Only supply content you have permission to share for the service.

Ask a privacy question →