We use cookies to understand how this site is used and which of our ads work. They stay off unless you accept. Privacy policy
This is a plain-language description of what Freveo collects and why. The short version: we collect what the product needs to work, nothing is sold or used to show you personalised ads, and your card details never touch our servers.
Last updated 13 November 2026
Freveo (freveo.app) is a tool for freelancers to manage clients, projects, invoices and payments. It is run by Sarthak Kundu, an individual trading as Freveo (Udyam registration UDYAM-WB-14-0322413), based in Kolkata, India. We decide how and why your data is used, which makes us the data controller (under India’s Digital Personal Data Protection Act, the data fiduciary). For anything in this policy, contact contact@freveo.app.
Freveo is not for anyone under 18, and we don’t knowingly collect data about children. If you think a child has given us their data, email contact@freveo.app and we will delete it.
Account details: your name, username, email address and a hashed password. We never store passwords in plain text.
Profile content you choose to publish: title, bio, business name, country, contact details, links, and the sections and files on your public page.
Workspace data you create: clients, projects, invoices and their contents.
Files you upload: avatars, covers and portfolio items.
Usage events and activity logs about your own account — shown back to you on the Analytics and Logs pages.
Visit totals for public profiles: daily counts of visits, opens, link clicks and contact-form use, with no visitor identified (see “Visits to public profiles”).
A record of the policies you accept: which version, when, and the IP address and browser your device reported at the time — so either of us can show what was agreed.
A record of each answer to a document you are asked to accept, such as a contract, a quote or a change order: whether you accepted or declined, the name you typed, the time, the IP address and browser your device reported, and a fingerprint of the exact document you saw (see "Your clients' data").
How you first arrived at Freveo, and your country, saved with your account when you sign up, if you accepted analytics cookies (see "Analytics").
Briefs sent through the freelancer directory, and a record of their confirmation (see “Client briefs”).
Reports about public profiles: the reason, any note, and your email address if you give one so we can confirm we received it.
Sign-in security, if you turn it on: the secret behind your authenticator app and your backup codes, both stored encrypted, and the public keys of your passkeys. A passkey’s private key never leaves your device.
Support requests: your name, email address, the topic and your messages, together with our replies (see “Support requests”).
The client and invoice records you keep in your workspace can contain personal data about your clients. That data is yours: you decide what to store, and we process it only to run the product for you. We do not use it for advertising and we do not sell it.
We email your clients only because of something you do in the product: sending them an invoice or document, inviting them to your client portal, asking for a testimonial, answering a payment or project request they sent you, or reminding them about an unpaid invoice if you turn on payment reminders. We never send marketing to an address that only exists in your client records. When you send an invoice or document, we record when your client first opens it, so you can see it was received.
You can also ask a client to accept a document, such as a contract, a quote or a change order. They answer from their client portal, and we keep a record of the answer: whether they accepted or declined, the full name they typed, their portal account, the time, a fingerprint of the exact document they saw, any reason they gave for declining, and the IP address and browser their device reported. You can see whether they accepted or declined, the name they typed, their account email and the time, and these are printed on the document when you export it, so either of you can show what was agreed. The IP address and browser are kept by Freveo only, in case we need to settle a dispute or the law requires it. The record is kept for as long as the document exists. A document that has an answer can’t be deleted, and the record stays with it even if your client later deletes their portal account.
A client who creates their own portal account becomes a Freveo user, and this policy applies to that account directly. If they agree to it when signing up, we may send them product news, and every one of those emails has an unsubscribe link.
If you use chat, the messages and files you and your client exchange in the client portal are stored so both of you can read them, and they are deleted with your account. Freveo staff read a conversation only when a message in it is reported to us, or when the law requires it.
If you turn on payment reminders, we email your client about an invoice you have already sent them. We use only the address you sent that invoice to, and only while money is still owed on it. Reminders go out before and after the due date, at most four times per invoice for each address. They stop once the invoice is paid or canceled, and pause while your client has told you they’ve paid and you haven’t yet confirmed it.
Each reminder comes from Freveo’s address with your business name on it, and replies go to you. Delivery is handled by Resend. We keep a list of the reminders sent (the address, the invoice and when) so you can see it on the invoice. That list is deleted when the invoice is. A copy of each email stays in our sending queue for up to 30 days.
Every reminder has a link that stops reminders from you to that client. Stopping doesn’t affect the invoices themselves or any other email you send them. We keep a record that they stopped them so we can honour it. Only your client can turn reminders back on, from the same link. The record is deleted if you delete that client or your account.
Anyone can describe a project on our freelancer directory and ask us to pass it on, without creating an account. We store the name, email address and project details you give us (category, description, and budget and timeline if you add them), along with the IP address your device reported when you sent it, so we can show the request came from you.
We send one email to confirm your address. Nothing is shared until you click its link, and if you never click it, the brief is deleted after 7 days. Once you confirm, we send it to up to five freelancers listed in the directory whose profiles match the work. Each of them receives your name, email address and brief as an enquiry and contacts you directly. From then on, their copy is part of their own workspace (see “Your clients’ data”).
We review briefs to stop spam and abuse, and we may block an address that misuses the form. To have a brief deleted, email contact@freveo.app and we will delete our copy. Copies already sent are held by the freelancers who received them, and you can ask them directly.
If you are a freelancer listed in the directory, matching briefs arrive in your leads. You can turn this off with “Receive briefs” in your directory listing settings.
Some profiles in the freelancer directory appear in a “Featured” row. Some are chosen by our team and marked “Picked by Freveo”; others are paid for by the freelancer and marked “Sponsored”. A featured profile shows only what is already public on it.
We count how many times each featured profile is shown, per day, so the freelancer can see it and we can check that placements are fair. The count is a number only: nothing about who saw the profile is recorded — no account, IP address, cookie or device identifier. To avoid counting the same visitor twice, your browser keeps a short note of which featured profiles it has already shown you; it is cleared when you close the tab. Because it identifies no one, this runs whether or not you accept analytics cookies.
When you visit a freelancer’s public profile on Freveo, we count the visit for that freelancer, together with which pieces of work you open, which of their links you click, whether you open their contact form and whether you send them a message. If you arrived through a link the freelancer shared, we note which kind of link it was (for example LinkedIn or a QR code). In the freelancer directory, we also count how often a freelancer’s profile is shown to you in search results and whether you click it.
We keep these only as daily totals, alongside the website that sent you (its address, not the page), your country as estimated by our hosting provider from your connection, and whether you use a phone, tablet or computer. We do not use cookies for this, and we do not store your IP address, your browser details or anything that identifies you. A freelancer sees only the totals, never who visited. Visits by the freelancer themself and by automated crawlers are not counted. Because it identifies no one, this runs whether or not you accept analytics cookies.
The totals are kept for 13 months and then deleted. We do this on the freelancer’s behalf, so they can see how their profile is found. The legal basis is our and their legitimate interest in understanding, in aggregate, how a public page is used.
Public profiles are open to anyone, so we check what goes on them.
Words. Usernames and profile text are checked against lists of abusive words. This runs on our own servers and nothing is sent to anyone else. Text that matches is flagged for a person to review; we never block a save because of it.
Links. When you add a link we follow it to where it finally leads and check every address on the way against public lists of adult, phishing and scam sites. A link on those lists can’t be saved. Profile links point through freveo.app/go/ so we can check them again when they’re clicked and remove one that turns bad; we count how often each is clicked.
Images. Avatars, cover images and portfolio images are sent to Amazon Web Services (Rekognition), which processes them in the United States as our processor and tells us whether an image may contain nudity, violence or hate symbols. An image it flags is hidden from your public profile and kept privately until a person on our team reviews it. You’ll see it marked “In review”.
Reports and review. Anyone can report a profile. A person on our team reviews every report and every flag; nothing is removed for good by a machine alone. If we hide something, we tell you why. Profiles listed in the directory are approved by a person before they appear.
Child safety. Where the law requires it, we report child sexual abuse material and the account that posted it to the authorities.
What we keep. Content we take down is moved to private storage instead of being deleted, so we can review it or hand it to the authorities when the law requires. It may be kept after your account is deleted, for as long as that requires.
Known abuse material. Public images are checked by Cloudflare against hashes of known child sexual abuse material, and matches are reported to the authorities.
Freveo has optional AI features that draft text for you and an assistant that can act in your workspace. Nothing is sent to a model unless you invoke one of them. When you do, your instruction and the record it is working from are sent — which can include personal data about your clients.
The model is provided by OpenAI, which processes these requests in the United States as our processor. OpenAI does not train its models on what we send through its API, and keeps requests for up to 30 days to detect abuse before deleting them. We do not train models on your data and we do not keep AI conversations. The AI and data page sets all of this out in full.
Payments for subscriptions and one-off purchases — credit packs and featured passes — are processed by Polar, our payment provider and merchant of record. Your card details go to Polar and never touch our servers. We store the status of your checkouts, subscriptions and orders so the product knows what you have bought.
Most of the email we send is transactional: verification codes, password and security notices, payment receipts and subscription updates. Product news and other marketing email goes only to people who asked for it, or who agreed to receive it as part of a demo or tester account we set up for them, and every one of those emails has an unsubscribe link. Delivery is handled by Resend.
Some of these emails are sent automatically when something happens, such as a welcome after you verify your address or a follow-up after you send a support request. Marketing ones follow the same consent rules as all our marketing email. When our team connects Freveo to a tool we use to run the service (for example a help desk or a notification channel), the details of that event — such as your name, email address and plan — may be passed to it. Those tools work for us as processors and may not use the data for anything else.
You can contact us from the contact form, from your account, or with the report button on an assistant reply. We store your name, email address, the topic and what you write, and our team’s replies, as a numbered ticket. If you are signed in, the ticket is linked to your account. We use it only to answer you and to improve the service.
Tickets are not deleted automatically, including when you delete your account, so that we keep a record of what was asked and answered. To have yours deleted, email contact@freveo.app.
Your data is stored in our database and uploaded files in our storage provider, Supabase, in the United States (North Virginia). Content you put on your public profile — including files in portfolio sections — is publicly accessible by design. Public files — avatars, cover images and portfolio files — are delivered through Cloudflare, which caches them and checks them against known child sexual abuse material.
The freveo.app website is served by Vercel, and our server, which handles every request to the app, runs at OVHcloud in Canada. Both see your IP address and browser details while they handle a request. Short-lived counters that protect the service from abuse are kept at Redis Cloud in Canada; they include your IP address and expire within minutes.
These providers, and the others named in this policy, act as our processors and may use the data only to provide their service to us. Because they are in the United States and Canada, data from the UK and the EEA is transferred there. We rely on their data processing terms for this, including the European Commission’s Standard Contractual Clauses and the UK addendum where they apply.
We use PostHog to see how the site is used — which pages people open, what they click, and how long they stay. It runs only if you accept analytics cookies, and only on our marketing pages, the sign-up pages and the signed-in dashboard.
It never runs on public profiles or anywhere in the client portal. Your visitors and your clients are not ours to measure.
PostHog processes this data in the United States as our processor, under its data processing agreement, which covers transfers out of the UK and the EEA. We have switched off storage of your IP address — PostHog reads it to work out a rough location and then discards it — so we can see which country people arrive from without keeping the address itself. We never record your screen: session replay is off.
If you are signed in, the only thing we attach to your activity is your account id. We do not send your name, email or username, and we never send anything from your workspace — no client names, no invoice numbers, no amounts.
When you create an account, we also save how you first arrived: the campaign tags in the link you followed, the website that sent you (its name only, not the page), the page you landed on, your country as estimated by our hosting provider from your connection (we do not store your IP address), and, if you came from one of our ads, the click identifier the ad network added to the link. We record this only if you accepted analytics cookies, it stays in our own database rather than going to PostHog, and it is deleted with your account. We use it to learn which places bring people to Freveo.
The analytics you see inside the product are a different thing entirely. They cover your own account and, for freelancers, the visit totals described in “Visits to public profiles”. Those are counted on our own servers and never sent to PostHog.
When someone searches the freelancer directory, we record the words searched, the category chosen, how many profiles matched, and when. Nothing about who searched is recorded: no account, IP address, cookie or device identifier. If you type a name into the search, that name is stored with the other words. We use this to see what clients look for that the directory can’t yet supply, and we delete each entry after 30 days. Because it identifies no one, it runs whether or not you accept analytics cookies.
We sometimes advertise Freveo on Google Search. If you accept cookies on our marketing or sign-up pages, the Google Ads tag runs there so Google can tell us which ads led to sign-ups. It never runs on public profiles, in the client portal or in the signed-in dashboard.
When an account created from one of our ads signs up or starts a paid plan, we send Google the click identifier Google attached to that ad visit, what happened (sign-up or purchase), when, and for a purchase its amount and currency. We do not send your name, email address or anything from your workspace. Ad personalisation and Google signals are switched off.
Google processes this data as described in its own privacy policy, including in the United States. If you do not accept cookies, the tag is never loaded and nothing about your visit reaches Google.
When something breaks, an error report goes to Sentry so we can find and fix it. A report holds the error message, where in our code it happened, the page or endpoint involved, and your browser and operating system.
We have switched off everything else Sentry can collect: no names, email addresses or account ids, no cookies, no request headers or bodies, no query strings, nothing from your workspace and no screen recordings. Sentry processes these reports in the United States as our processor.
Your account, profile and workspace: until you delete them, or delete your account.
Activity logs about your account: 90 days.
Records of actions taken by our staff, which can name your account: 90 days, then an archive kept for one more year before it is deleted.
Anything with its own period in this policy — visit totals, directory searches, briefs, newsletter sign-ups and reminder records — for the period stated there.
Deleted data can remain in our database backups for a short time until they are replaced.
Tables in the app export to CSV whenever you want a copy. Deleting your account from the Security page removes your account data and deletes your customer record at Polar. Public profile content comes down with it. Content we have removed for breaking our rules may be kept privately after deletion where the law requires us to preserve it.
If you want to complain about content on Freveo or about how we handled your data, contact our Grievance Officer, Sarthak Kundu, at grievance@freveo.app. We acknowledge complaints within 24 hours and resolve them within 15 days.
You can access and correct your data in the app, export it, or delete the account entirely. For anything you cannot do from the app, email contact@freveo.app and we will handle it.
We use your data to provide the service you signed up for (our contract with you); for analytics, advertising measurement and marketing email, only with your consent, which you can withdraw at any time; to keep the service secure and free of abuse, which is our legitimate interest; and where the law requires us to.
If you are in the UK or the EEA, you also have the right to object to processing based on our legitimate interests, to ask us to restrict it, and to complain to your data protection authority. We would appreciate the chance to sort it out with you first.
If this policy changes in a way that matters, we will say so in the product before the change takes effect. The date at the top always reflects the latest revision.