Of record
Privacy Policy
Freelanix / p/privacy / Last updated August 11, 2026
This policy explains what Freelanix collects, why we keep it, how long we keep it and what happens to your data when you leave. It covers the platform at large, including the marketplace, messaging and payouts.
What we collect
- Account data: your name, email address, hashed password, country and avatar.
- Profile data: professional title, bio, hourly rate, skills, tags and portfolio items. Anything you put on a public profile is visible to other users and to search engines.
- Marketplace activity: projects, proposals, contracts, milestones, reviews, notifications and the messages you exchange with other users.
- Files you upload: message attachments, portfolio images and evidence submitted in a dispute.
- Payment metadata: amounts, currency, status and the reference given to us by our licensed payment provider. Card numbers and bank details are entered directly with that provider and never reach Freelanix servers.
- Technical data: your session cookie, IP address and timestamps written to our audit log for security and for reconstructing what happened on an account.
Why we use it
We use your data to run your account, show your profile and projects to the right people, deliver messages and notifications, instruct payouts, calculate fees, investigate disputes, prevent fraud and abuse, and meet our accounting obligations. We do not sell your data and we do not use your messages for advertising.
Uploads and where they live
Files you upload are stored on the platform server, not in a public bucket. They are served through an authenticated route that checks, on every request, that you are a party to the conversation, contract or dispute the file belongs to. A file URL alone is not enough to open it. Deleting a portfolio item also removes the stored image.
Who can see what
Public profile fields and published projects are visible to everyone. Proposals are visible to the client who received them. Messages, attachments, contracts, milestones and payout figures are visible only to the two sides and, where an investigation requires it, to platform administrators. Every administrator action of that kind is written to the audit log.
Sharing with others
We share the minimum necessary with our licensed payment provider so it can hold and release funds, with our email delivery provider so notifications reach you, and with authorities where the law requires it. These providers act on our instructions and cannot use your data for their own purposes.
Retention
Account and profile data is kept while your account exists. Contracts, invoices, payouts and audit entries are kept for the retention period required by accounting and tax law in our jurisdiction, which is longer than the life of the account. Messages and attachments are kept for the life of the contract they belong to, plus the dispute window.
Anonymization instead of deletion
Freelanix does not hard-delete accounts. On request, or when an account is closed for a breach, we anonymize it: your name is replaced with a neutral label, your email address, avatar, bio, country and portfolio are cleared, your login credentials stop working, and your reviews and messages are detached from your identity. The underlying financial and audit records remain, without the personal data, because we are required to keep them and because the other side of a past contract keeps its own history. Anonymization cannot be undone.
Cookies
We set one session cookie so you stay signed in, and nothing else. There is no advertising or third-party tracking cookie on Freelanix, so there is no consent banner to click through.
Your choices and how to reach us
You can edit or clear most profile fields yourself in your settings, download the documents attached to your contracts, and turn off email notifications you do not want. To ask for a copy of your data, correct something you cannot edit, or request anonymization, write to the support address shown in your account settings, or reply to any notification email you received from us. We answer data requests within 30 days.