Privacy notice

Data collected

TaskLink stores account and profile details, advertisements, approximate and precise listing coordinates, introductory conversations, reports, blocks, subscriptions, notifications, consent records, and security logs needed to operate the service. It does not request or store agreed task prices or task-payment records.

How data is used

Data supports authentication, email verification and recovery, listing discovery, communication, subscriptions, abuse prevention, moderation, account enforcement, and service reliability. Account email addresses and transactional message contents are sent to the configured email processor. Submitted text may be sent to the configured AI moderation provider for classification. A user report preserves a report-time copy of the reported content and responsible account so later edits cannot erase safety evidence. Blocked or low-severity automated decisions create audit metadata using a keyed content hash, category, source, and timestamp; rejected text is not copied into that automated audit event.

TaskLink does not ask users to enter task prices and does not extract, classify, summarize, calculate, or commercially use price or earnings information from private messages. Because users control message text, TaskLink cannot promise that a user will never type such information. Do not use TaskLink chat to conclude a task contract or document its price.

Operational statistics

TaskLink keeps aggregate hourly page-view counters for service operation and improvement. Each counter contains only a normalized route, hour and total count. It does not store an analytics cookie, visitor or session identifier, IP address, fingerprint, query string, referrer, device profile, exact location or cross-site activity. Hourly counters are automatically deleted after 90 days. Administrators also see aggregate counts derived from service records, such as registrations, listing states, introductions, safety reports and active TaskLink access plans; these statistics do not include task prices, user earnings or agreements between users.

Visibility and location

Public search uses coarse location cells. Subscribers may see advertisement details and poster identity. Exact stored coordinates remain visible only to the poster; users independently coordinate meeting details. Private messages are visible to their participants and may be reviewed after a safety report.

Control and retention

Account controls provide JSON export, session revocation, blocking, and deletion. Deletion removes credentials, profiles, subscriptions, precise locations, and authored content. Minimal pseudonymized conversation and moderation records may remain where necessary to preserve another participant's history, prevent abuse, or maintain an audit trail. Exact retention periods must be finalized before production.

Before public launch, the operator must add its legal identity, privacy contact, lawful-basis and processor details, retention schedule, and counsel-approved rights procedure.