Privacy
The short version
Your profile is public — that's the point of it. Your plans, boards and saved references are private. We don't sell your data and we don't show ads.
What's public
Your name, handle, role, city, bio, portfolio, published projects, the credits on them, and your representation. Anyone can see these, signed in or not, and search engines can index them. Don't put anything on your page you wouldn't send to a client.
What's private
Your email address, your plans and their contents, your boards and saves, who you follow, your inquiries (sent and received), and your notifications. Stories are visible to the people described in the app and are deleted 24 hours after posting.
What we collect
- What you give us: email, profile details, images, and anything you type.
- When you confirmed your age and accepted these policies.
- Basic technical data needed to run the service and keep it secure.
- Product events, so we can tell whether the thing works: signing up (including when a signup is blocked, and why), choosing an account type, each step of the page builder, going live, publishing a project, sending an inquiry, posting a story, creating a plan or board, saving a project, and filing a report.
- Three events that are about you rather than about what you did, so your Insights page can exist: that your profile was viewed, that one of your projects was viewed, and that you appeared in a search for your role. They are filed under your account, not the viewer's. We do not record who looked — only the anonymous first-party id described below, and only so one person refreshing isn't counted as ten. Repeat looks by the same visitor collapse into one for thirty minutes.
Those events record that something happened and a few plain details about it — a project's type, how many people were credited, whether an inquiry went to an agency or direct. They never contain your messages, the text of a report, or your images. Each is tied to your account, or before you have one, to a random id in a first-party cookie that exists only to connect the two halves of the signup funnel.
When something breaks we record the error and the page it happened on, so we can fix it.
The waitlist
If you join the waitlist, we keep your email, and your role and city if you add them, with the time you joined. We use them only to invite you to the pilot and to see who's waiting. We never share or sell them, and they go to no email, analytics or ad service. We don't send a confirmation email or add you to a mailing list. Only the ForLance team can see the list, and no count of it is shown anywhere public.
To stop scripts flooding the list, we count tries from each network under a scrambled key, kept for two hours at most and never with your email. To come off the list, ask us at the address under Your choices.
Who else sees it
Our hosting and storage providers, as processors. Moderators, when a report involves you. Anyone you send an inquiry to — and, when you are represented, the agency your inquiry is routed to. Nobody else.
Your choices
You can edit or delete anything you've posted, take down a story before it expires, and delete your account. Ask us for a copy of your data or for it to be erased at privacy@forlance.co. We keep moderation records for [RETENTION PERIOD] after an account closes so we can act on repeat behaviour.
Minors
Fashion work involves people under 18, which makes this the part we take most seriously. Accounts require age confirmation at sign-up. Reports that concern a minor are reviewed first. [FULL POLICY — including guardian consent and whether under-18s can be tagged in credits — TO BE SET BEFORE LAUNCH.]
Still to be decided before launch
- Minimum age, and how under-18 talent is handled (guardian consent, agency representation, whether they can be tagged in credits at all).
- Operating entity, country of registration, and governing law.
- The DMCA / copyright takedown agent: a named person and address.
- Data retention: how long we keep accounts, images, inquiries and moderation records after deletion.
- Image rights: what a person warrants when they upload work someone else shot, and what happens on a credit dispute.
- Whether inquiries and messages are scanned or stored for safety review, and for how long.
- Whether the product-analytics events described in the privacy policy need a cookie banner or consent prompt in the markets we launch in.