Legal · draft for review
Privacy Policy
Understand what we collect, who receives it and how to exercise your rights.
Read the privacy policyDraft revised 11 October 2026. Accepted terms version 2026-09-25 is unchanged. Operator, provider and retention details require confirmation before adoption.
1. What we collect
We collect the information needed to operate accounts and projects: your account details (name, email, password — stored as a hash, never in plain text), anything you add to your profile (headline, bio, rate, skills, availability, portfolio work), the content of project conversations and files you send or deliver in them, payment and payout details needed to move money (handled by our payment processor — see below), and basic technical/usage data (sign-in timestamps, session tokens, IP address at sign-in) needed for security and to keep you signed in.
- Account — name, email, hashed password, account status.
- Profile — headline, bio, hourly rate, skills, languages, availability windows, portfolio items you add.
- Project data — messages, delivered files, delivery records, reviews, dispute statements, scope-change and payment-request records.
- Payment data — amounts, ledger entries, and payout status; card and bank account numbers themselves are held by our payment processor, not by Actuallize (see "Payment processor").
- Technical data — session cookies, sign-in timestamps, and IP address at sign-in, used for authentication and security.
2. How we use it
We use this data to operate the product: matching clients and professionals, running project conversations, recording funding, release and settlement status, running the dispute-resolution process, sending notifications about activity that needs your attention, aggregating your public rating from published reviews, and detecting fraud, abuse, and attempts to move payment off-platform. We do not sell your personal data or use it to train our own models. Any Studio production-provider processing must be disclosed as described above.
3. Your rights
Depending on where you live, you may have rights to access the personal data we hold about you, correct it, export it, or request deletion of your account. You can update your profile in Settings and download your account record (JSON) or payment ledger (CSV) from Settings → Account. To exercise a right this policy does not yet cover in-product, email hello@actuallize.com.
4. How to delete your account and your data
Email hello@actuallize.com from the address on your account, with the subject "Delete my account". We reply to that address to confirm it is you, close the account, and delete the personal data described in this policy with a response about the action taken or any applicable extension within 30 days. The exceptions in "Data retention & deletion" (completed financial records, and a project record the other party still has an interest in) still apply, and our reply says what was kept and why.
Use the email route for account deletion; removing a connected social account alone does not delete your Actuallize record.
If you signed in with Google, Microsoft, Facebook or LinkedIn: we receive only your name, email address and profile picture from the provider, and we never post on your behalf. Removing Actuallize from that provider's list of connected apps stops future sign-ins but does not delete your Actuallize account; send the email above for that.
5. Cookies & session data
Actuallize uses a session cookie to keep you signed in — this is required for the product to function and isn't an optional tracking cookie. We may use basic, privacy-respecting analytics to understand overall product usage (e.g., which pages are visited); today we do not use third-party advertising cookies or cross-site ad tracking.
When you continue from a professional recruitment page to create an account, a first-party cookie carries your selected services through signup for up to seven days. It is cleared when you continue to profile setup. We record the campaign, source and message variant that brought you to signup and link them to a newly created account to measure email confirmation and profile completion. These records are private, included in your account export, and removed with your account. Joining does not subscribe you to recurring marketing emails.
6. Sharing with third parties
The application uses Neon for database storage and Cloudflare for application delivery and object storage. Account and project data may be processed by these services for those functions. Social sign-in shares authentication data with the provider you choose. The brief assistant and any Studio production require provider-specific data-handling disclosures. A Stripe integration in the codebase is not confirmation of an approved custody or payout arrangement; the actual payment provider and its terms must be identified before collection. We may also disclose information where legally required or to investigate abuse.
7. Payment processor
Actuallize does not directly store your full card number or bank account number. Before payment collection is enabled, the named provider and its data handling must be disclosed. Payment details should be supplied through that provider’s secure interface; no approved custody arrangement is established by this draft.
Actuallize stores the records needed to show you what happened with your money — amounts, timestamps, fee breakdowns, and status (Protected, Paid, or returned to the client) — as described in the Terms of Service's "Protected payments & fees" section.
8. Studio production and source material
Preparing a brief does not send your source files to an asset-generation or transcription provider. An enabled Studio package must disclose its actual production providers, purpose, relevant retention and deletion terms, and any international processing before purchase. The pilot does not yet have an enabled production-provider chain.
Studio operators access the material needed to fulfil and check your order. Delivery records retain source references, AI and human contributions, versions and checks alongside your project. A separately engaged professional receives only the context you choose to share. Do not upload source material you lack permission to use.
Provider-specific retention and training settings must be verified for the service used. The brief assistant’s routing or retention settings do not establish the policies of an image, video or transcription provider. Contact us to ask about access, correction or deletion of your project material, subject to required transaction records.
9. Message & file retention
Project conversations and delivered files are kept for the life of the project and afterward, because the completed conversation is the record both parties (and, if needed, an Actuallize operator resolving a dispute) can refer back to. We don't delete a project's record just because one party asks, since the other party has an equal interest in that record staying intact — see "Data retention & deletion" for what account deletion does instead.
10. Data retention & deletion
Deleting your account removes your ability to sign in and cascades the deletion of your personally-identifying account data (profile, session, notification preferences). Some records can't be fully deleted even on request: completed financial transactions and the ledger entries behind them (kept for accounting, tax, and fraud-prevention reasons, and because deleting one side of a shared payment record would corrupt the other party's own record), and a project's message/dispute record where the other party retains a legitimate interest in it (see "Message & file retention").
The retention schedule, legal basis and operator jurisdiction require confirmation before this draft is adopted. We cannot promise an exact financial-record deletion period without those facts. A deletion response must identify retained categories and the reason for keeping them. Operator: [legal operator name and registered address]. Retention schedule: [data categories, retention periods and legal bases]. Payment provider: [approved provider and privacy terms].
11. Children's privacy
Actuallize is not directed to, and does not knowingly collect personal data from, anyone under the age of 18 (see the Terms of Service's eligibility requirement).
12. Changes to this policy
We'll take reasonable steps to notify active users (for example, an in-app notice) before a materially-revised Privacy Policy takes effect. This policy is versioned "2026-09-25" — see your account's terms-acceptance record for which version you last accepted.