Privacy Notice

1. Notice at collection

Data collected at registration: email or Apple account identifier, authentication records, country, age or date of birth, optional gender, device model, languages, equipment, household capabilities, and legal-document acceptance records.

Why: create and secure the account, confirm 18+ eligibility, match assignments, operate the service, prevent abuse, and keep evidence of the agreement.

Task data: task choices, answers, photos, videos, audio, file metadata, review decisions, rewards, and payout records. The task brief and license identify the permitted use before collection.

Sale or sharing: Datafolks does not sell profile or contact data for cross-context behavioural advertising. Optional sharing of advertising events with Meta is explained in section 12 and requires separate consent. Only accepted task deliverables may be licensed or supplied to customers for the purpose stated in the task brief and accepted license; that transfer may be treated as a sale or disclosure under some laws. The applicable task notice gives additional information before the participant starts.

Retention: account and profile data is generally kept while the account is active. Other server records are kept while needed to carry out the applicable contractual obligations and for one year after that need ends, where lawful, to handle disputes, prevent abuse, and establish or defend claims. A legal obligation may require a longer period; a valid deletion request may require earlier deletion. Section 7 explains how this rule applies to different records.

2. Information we collect

Account and authentication

Email address, Apple relay address or provider identifier, account ID, confirmation and session information, and account creation and sign-in timestamps. Passwords are handled by the authentication provider and are not available to Datafolks in readable form.

Profile and screening

Country, an estimated date of birth derived from the age supplied at registration, optional gender, phone model, languages and proficiency, instruction language, video and audio equipment, quiet-room availability, household appliances, and activities.

Tasks and submissions

Assignment status, task interactions, survey and form answers, uploaded or captured photos, video and audio, file type and size, submission revisions, timestamps, review notes, acceptance decisions, reward entries, and payout requests.

Legal and support records

Records of which legal documents and task licenses you accepted or acknowledged, when and how you did so, and communications with support.

Technical information

Basic request, security, and error information generated by the app, hosting providers, authentication service, and storage service. Invitation and optional advertising measurement are explained in section 12.

3. Purposes and legal bases

• Contract: create the account, provide assignments, receive submissions, conduct review, calculate task credits, and administer payouts.
• Legitimate interests: secure the service, prevent duplicate accounts and fraud, troubleshoot failures, keep necessary audit records, handle disputes, and establish or defend legal claims, balanced against participant rights.
• Legal obligations: tax, accounting, sanctions, lawful requests, worker or platform reporting, and other duties that apply to Datafolks.
• Consent: optional Meta advertising measurement, and where a task or optional feature specifically says processing relies on consent, such as certain sensitive or biometric uses. Consent can be withdrawn prospectively without affecting processing already lawful before withdrawal.

Acknowledging this Privacy Notice is not general consent to every use of personal information.

4. How task data is used

Datafolks receives a license to submitted material when the participant accepts the applicable task license and submits the material. That license is separate from Datafolks' decision to accept or reject the work and from any task credit or payout. Datafolks reviews all submitted material for quality and may retain rejected material for review, disputes, security, and fraud prevention. Only accepted task deliverables are licensed or supplied to customers. Accepted material may be cleaned, labelled, annotated, transformed, combined, analysed, used to train or evaluate technology, and supplied to a customer only as described in the task brief, data-use notice, and accepted license. A materially different use requires an appropriate new notice or agreement before it begins.

Do not include another person or their personal data unless the task expressly provides a valid release workflow. Datafolks currently prohibits tasks requiring third-party model releases, property-owner signatures, biometric identification, health records, or other sensitive categories without a separate approved process.

5. Recipients and service providers

Information may be disclosed to:

• Datafolks personnel and reviewers who need it to operate the service and review tasks;
• Supabase, which provides account authentication, the application database, private file storage, and backend functions;
• Vercel, which hosts the public website and operator administration interface;
• Meta, only when optional app advertising measurement is enabled and you separately consent as described in section 12;
• Apple, when Sign in with Apple, iOS push notifications, or other Apple platform services are used;
• Resend, which delivers task messages and website download invitations, and may deliver account messages if configured for that purpose;
• customers and their processors, only for accepted task deliverables and the purpose disclosed before the task was accepted;
• professional advisers, auditors, insurers, and payment or tax providers where their services are used; and
• authorities or counterparties where disclosure is required by law or necessary for a corporate transaction, subject to appropriate protections.

Service providers must process information under contractual restrictions appropriate to their role. A customer receiving an accepted task deliverable may act as an independent controller; the task notice identifies the customer or customer category and its role where required. Datafolks' retention rule does not automatically control copies held by an independent customer.

6. International transfers

The primary Supabase project is hosted in the European Union. Providers, reviewers, and customers may process information in other countries. Where transfer law requires it, Datafolks will use an adequacy decision, contractual safeguards, or another lawful transfer mechanism. Email support@datafolks.space to ask about applicable transfer safeguards and how to obtain a copy where available.

7. Retention

Datafolks keeps server records while they are needed to perform the applicable obligations under a participant account, accepted task, customer delivery, review, or payout. Once those obligations end, Datafolks keeps the records for one further year where lawful to handle disputes, prevent abuse, and establish or defend legal claims, then deletes or de-identifies them. Datafolks may delete information sooner when required or keep particular records longer when law requires it. This period concerns Datafolks' copies, not a customer's independently held copies.

• Account and profile: while the account is active. The sign-in account and personal profile are removed after account deletion, subject to necessary retained records described below.
• Unsubmitted local files: on the device until removed, submitted, or the app's local data is cleared.
• Submissions and accepted content: during review, agreed customer delivery and other continuing task obligations, then for one further year under the rule above. Material already delivered to a customer or incorporated into a trained system is addressed by the task notice, the customer's obligations, and applicable law.
• Rejected work: during review and any related dispute or fraud investigation, then for one further year under the rule above. Rejected work is not supplied to customers.
• Legal acceptance, reward, payout, audit, and tax records: during the applicable contractual and legal obligations, then for one further year where lawful; a mandatory accounting, tax, reporting, or claims period may require longer retention.

8. Account deletion and pseudonymisation

The in-app Delete account control removes the authentication account and personal profile. Completed task, submission, content, reward, payout, audit, and legal acceptance records may remain under a new random pseudonym for the periods described above, so they are no longer directly linked to the deleted authentication identifier. Pseudonymised data remains personal information where re-identification is reasonably possible and continues to receive applicable protection. Account deletion does not by itself recall material already supplied to a customer under the accepted task terms.

9. Your rights and how to contact us

Depending on your location and applicable law, you may have rights to access, correct, delete, restrict or object to processing, receive a portable copy, withdraw consent, opt out of certain sales or sharing, limit certain sensitive-data uses, and complain to a regulator. You may also have rights concerning automated decisions and platform-work management.

Use the in-app control to delete your account. For other privacy requests, questions, or an appeal, email support@datafolks.space. We may ask for information reasonably needed to verify that a request concerns you, including when an authorised agent makes a request. If an account has been deleted, tell us the email address previously used with it and any task details you can provide; we will explain what records we can still locate and what rights apply. Datafolks will not discriminate against a person for exercising a mandatory privacy right.

10. Automated matching and review

Profile fields are used to identify potentially suitable tasks. Current submission decisions are made through operator review. Before material automated monitoring, ranking, eligibility, suspension, or review decisions are introduced, Datafolks will provide the additional explanation, safeguards, human review, and worker information required by applicable law.

11. Security and children

Datafolks uses access controls, private file storage, pseudonymisation on account deletion, and role-based administration. No system is completely secure. Protect your devices and credentials and report suspected compromise to support@datafolks.space.

Datafolks is limited to adults aged 18 or older and is not intended for children.

12. Invitation and advertising measurement

Invitation requests and our own measurement

When you request a TestFlight link, we process your email, the request and sending timestamps, sending status, and campaign labels such as source, medium, campaign, creative, keyword, campaign ID, ad-set ID, and ad ID. These labels are taken from the URL of the page you opened. We do not store Facebook click IDs, use browser cookies or persistent browser storage for this feature, or use device fingerprints. Network-address hashes used to prevent abuse remain separate and are not used to match invitations with accounts.

Datafolks uses these records internally to understand the cost and effectiveness of recruiting participants. We compare invitation email addresses with account email addresses and account-creation timestamps. When addresses differ, we may estimate a relationship from the timing of an invitation and a registration. Time-only estimates are uncertain, displayed separately to operators, and excluded from confirmed figures by default. These estimates do not change your account, task eligibility, rewards, or review decisions. This internal processing relies on our legitimate interest in measuring and improving recruitment, balanced against your rights. You may object by contacting support@datafolks.space.

Invitation records are restricted to the service and authorised operators. Entries inactive for more than 90 days are removed when the next invitation request is processed; reports cover the most recent 90 days. Invitation records are stored separately from accounts and may remain for that period after account deletion; you can contact us to request earlier removal, including when you used a different invitation email. Deleted accounts are excluded from the acquisition report. We do not send invitation emails, campaign-to-account matches, or time-only estimates to Meta.

Optional Meta measurement in the iOS app

Some app versions include the Meta iOS SDK to measure and improve our Facebook and Instagram advertising. This feature remains off unless it is enabled in that app version, you separately choose to allow advertising measurement, and iOS App Tracking Transparency authorises tracking. Acknowledging this Privacy Notice or the Participant Terms does not grant advertising consent. Declining either permission leaves your access to Datafolks, tasks, and rewards unchanged.

When enabled with your permission, the app sends Meta basic events such as app activation, completed registration, completed screening, task start, and work submission, together with the device advertising identifier and technical information handled by the SDK, such as app and device details and network metadata. Local event-deduplication keys are not sent to Meta. Datafolks does not put account emails, account IDs, screening answers, task responses, uploaded media, review notes, payout details, or reward amounts into these advertising events. Meta may combine the permitted event information with information from its own services or other sources for advertising measurement and related advertising purposes.

This optional processing relies on consent. You can switch off advertising measurement in Datafolks Settings and manage tracking permission in iOS Settings. New advertising events stop when either permission is withdrawn; withdrawal does not affect processing already lawful before it. Signing out or deleting an account turns off the app’s separate advertising consent. Datafolks does not keep a server-side copy of the Meta event stream. Meta handles information already received under its applicable data terms and privacy policy; contact us for assistance with a data-rights request. Where required, international-transfer safeguards apply. This optional advertising sharing may be treated as sharing for behavioural advertising under some laws.

Website advertising pixels and cookies are not enabled by this notice. Before introducing them, Datafolks will explain their actual operation and provide the separate choices required for that feature.

13. Changes to this notice

Each notice has a version and effective date. New registrants acknowledge the current version. Material changes are shown in the app when renewed acknowledgement or consent is required. Historical versions and acceptance evidence are retained.