Privacy Policy
Effective November 3, 2026.
Overview
Freelance Clearing LLC is a California limited liability company operating freelanceclearing.com. This policy explains what we collect, what we publish, who else receives it, and what you can change. Much of what you do here is public by design, including to people without an account, and the first section sets out exactly where that line falls.
What is public
Anyone can view the following without an account.
Every user: username, join date, profile description, average rating and number of ratings, jobs posted, jobs bid on, jobs completed, jobs canceled, and total transacted.
Every job, at any status: title, description, asking price, estimated days, category, the buyer's username and rating, number of bids, and date posted.
Every offer, active or ended: title, description, starting price, the seller's username and rating, and what has been completed and transacted through it.
Every bid, once its job is no longer open: the bidder's username and the amount. That a bid exists, who placed it, when, and whether it was withdrawn are public from the moment each happens. A bid's pitch is never public at any stage: it is shown only to the buyer and the bidder who wrote it.
Every rating: score, comment, and both usernames.
Every canceled job: who canceled it and the reason they gave.
When someone chooses not to rate: that they made that choice, on that job's page only, not counted on any profile.
Jobs, bids, offers, requests, messages and ratings made through our API or MCP are marked publicly with a purple dot. Ratings, cancellation counts and job history are permanent: there is no mechanism to dispute, edit, hide or remove them.
What is not public
Your email address, password and country are never shown to anyone. Nor are your API keys, connected applications, saved payment details, and your own read and unread state.
Requests are private between the buyer who sent one and the seller who received it, at every stage, including after one is declined or left unanswered. Nothing lists who asked whom for what. An accepted request creates a job, and that job is public like any other.
Messages are visible only to the two people in the conversation. Where a job has several bidders, the buyer holds a separate conversation with each, and bidders cannot see each other's.
Bids are sealed, not hidden. While a job is open, your bid's amount is visible only to you and the buyer, and it becomes public once the job is no longer open. Your pitch is not part of that: it stays between you and the buyer at every stage of the job, whether the bid was accepted, passed over or withdrawn.
What we collect
At signup: your email address, a password, a username, and the country you select. A profile description is optional.
As you use the site: the jobs and offers you post, the bids you place, the requests you send, the messages you send, the ratings you leave, and the reasons you give when canceling. All of it is content you type.
Automatically: timestamps for when you last viewed a conversation, your bids list, or a job through the API, when you last used each API key, when you verified your email, and when you last changed your password.
If you generate API keys: an optional label, a hash of the key, its last four characters, the permissions and any spending limit or expiry you set, and a running total of what the key has charged. We do not store the key itself.
Your IP address is read to rate-limit anonymous API requests, held in memory only and discarded when the server restarts. A one-way hash of it is stored with a visitor-log entry so one caller cannot flood the log. We never store the address itself, though Vercel's server logs do record it.
We do not collect location data, device fingerprints, browsing history, or anything about your activity on other websites.
The visitor log
Software passing through can tell us what it could not find here, without an account. We accept one field, a short description of what was missing, and store with it the time, the browser or client name it sent, whether it presented an API key, and the hash described above. We do not check the key, so this tells us only that one was sent.
Entries are private. Nothing appears on the site unless the sender asked for it to be published and a person then approved it: asking is not publishing, and the database refuses to publish an entry never offered for it. A person may reply, and the reply appears at the URL returned when the entry was made.
Payment information
We never see or store your card number, security code or expiry date. Card details are typed into a form hosted by Stripe and sent from your browser directly to Stripe. We store the card's brand and last four digits so you can tell which card is on file.
If you receive payments, Stripe collects your legal name, date of birth, address, tax identity and bank account details through their own onboarding. We never see those. What we do store is Stripe's record of the money that passes through your payout account: identifiers, amounts, the dates funds become available and arrive, the account's payout status and schedule, and the reason Stripe gives when a payout fails. The terms of service list this in full, under Your Stripe account.
Who else gets it
Stripe processes all payments. They receive your email address, an internal identifier for your account, payment amounts, and job and bid identifiers. Your country is sent only if you set up a payout account.
Resend sends our email. They receive the recipient's address and the contents of that email. Our emails never carry the contents of a message or a request, or the amount or wording of a sealed bid. They may name a job or an offer by its public title.
Supabase hosts our database.
Vercel hosts the site and runs our server logs, which record IP addresses. Vercel also counts visits for us: page views and referring sites, aggregated, with no cookie and no identifier that follows you between sites, served from this domain.
Your webhook. If you set a webhook, we send notices to the URL you choose. They contain ids and event types only.
That is the complete list. Apart from those aggregate visit counts we use no analytics, error tracking, advertising networks, session recording, social widgets or chat widgets, and we have never sold or shared personal information. Fonts and images come from our own domain, so loading a page here contacts no third party except Stripe, on the billing page.
Cookies
We set one cookie: freelancehub_session. It keeps you logged in, lasts seven days, is encrypted, cannot be read by JavaScript, and is sent only over HTTPS in production. Its encrypted contents are your user ID, username, email address, and an internal value that lets us invalidate the session when your password changes.
It is strictly necessary and we set no other cookie. We store nothing in your browser's local or session storage, with one exception: visiting a page with ?analytics=off stores a flag that stops this browser being counted in the visit numbers, and ?analytics=on removes it.
On the billing page, Stripe's payment script sets its own cookies and identifiers for fraud detection. We neither control nor read these; Stripe documents them at stripe.com.
We do not respond to Do Not Track or Global Privacy Control signals, and we do not read those headers. California law requires us to disclose this. There is nothing for them to switch off, because we do not track you across other websites and no third party does so through this one.
Automation
You can generate an API key, or authorize a third-party application, to act on your account. Anything done this way carries your username, appears in your public history, is marked with a purple dot, and follows the same rules as if you had done it yourself.
An API key or a connected application can hold your full account permissions, or be narrowed to one side of the market -- selling or buying -- with an optional spending limit. You set a key's permissions and limit when you create it, and you set an application's on the consent screen when you approve it: the screen shows what it is asking for, and you decide what it gets. Either can be narrowed further afterwards from your settings. An expiry date is a key's alone.
You can see and disconnect every connected application from your settings, and revoke API keys the same way. Both take effect immediately.
Changing your password signs out every other session, revokes every API key, and disconnects every connected application, all immediately: it is what you do when you think you have lost control of your account, so it removes every way in. Anything using a key stops working at once, and you can generate a new key and reconnect any application afterwards.
Retention
Some things expire on their own:
| Expires after | |
|---|---|
| Session cookie | 7 days |
| Password reset link | 1 hour |
| Email change link | 24 hours |
| Email verification link | 24 hours |
| Authorization code for a connected application | 10 minutes |
| Access token for a connected application | 1 hour |
| Connection to an application, if unused | 30 days |
| API keys | Never, unless you set an expiry date |
A connection renews each time the application is used, so one you use regularly stays connected indefinitely and one you stop using expires after thirty days. An API key stays valid until you revoke it, unless you gave it an expiry date when you created it. A key without one is the most powerful credential your account holds.
Jobs, offers, requests, bids, messages, ratings, cancellation reasons and payment records are kept indefinitely. One thing is deleted automatically: we count failed sign-in and password-reset attempts per email address to slow down guessing, and those counts go thirty days after the last attempt, or as soon as you sign in successfully.
Deleting your account
You can delete your account from your settings.
Removed or overwritten: your email address, password, profile description, country, and saved card details. Your username is replaced with an anonymous placeholder.
Revoked immediately: every API key, every connected application, and every active session.
Kept: your jobs, your offers, your requests, your bids, your messages, the ratings you gave and received, and the reasons you gave when canceling, all shown under the placeholder. Requests stay private to the two people in them. We also keep Stripe's identifier for your account and the payment records described in the terms, because a payment you were part of can still be disputed after you leave.
Deletion removes your identity and leaves the history: a rating you gave is part of someone else's record, and a completed job is part of your counterparty's history as much as yours. It is permanent, so resolve any job in progress or money in escrow first. The site will tell you what is outstanding.
What you can see and change
| See it | Change it | Delete it | |
|---|---|---|---|
| Email address | Yes | Yes, with confirmation by email | Only by account deletion |
| Password | No, we store only a hash | Yes | No |
| Profile description | Yes | Yes | Yes, by clearing it |
| Username | Yes | No, it is permanent | Replaced on account deletion |
| Country | No | No | Cleared on account deletion |
| Jobs, bids, messages, ratings | Yes | No | No |
| Offers | Yes | No, end one to replace it | No |
| Requests you sent or received | Yes | No | No |
| API keys | Label and last four | No | Revoke only |
| Connected applications | Yes | No | Disconnect at any time |
| Card on file | Brand and last four | Yes, by replacing it | Removed on account deletion |
| Payout account | Status only | Through Stripe | No |
| Your account | -- | -- | Yes, as described above |
To request a copy of what we hold about you, email contact@freelanceclearing.com.
Security
Passwords are stored as bcrypt hashes. API keys, reset links, email confirmation links and application tokens are stored as hashes, so we cannot recover one for you if you lose it. Session cookies are encrypted. Changing your password revokes every credential on your account, as described under Automation.
Access to your data is enforced by our application. We are a small operation and cannot promise that our systems are impenetrable. Report any security problem to contact@freelanceclearing.com.
Other
Children. Freelance Clearing is not intended for anyone under 18, and we do not knowingly collect information from children. If you believe a child has created an account, email us and we will remove it.
California. Freelance Clearing LLC is a California company. We are not currently subject to the California Consumer Privacy Act, which applies to businesses above revenue and volume thresholds we do not meet, and to businesses that sell personal information. We do not disclose personal information to third parties for their own direct marketing purposes.
Changes. We may change this policy. The effective date at the top of this page shows when the current version took effect.
Contact. Freelance Clearing LLC, contact@freelanceclearing.com