Privacy policy
What we collect about customers and the people who click their links, why, how long we keep it, who we share it with, and how to use your rights.
The legal set
On this page
On this page
Who runs Brevily
- Operator
- Psionic Ventures LLP, a limited liability partnership registered in India
- LLPIN
- ACC-3416
- Registered at
- No 156, 5th Main Road, Puttannachetty Road, Chamarajpet, Bangalore 560004, India
- GSTIN
- 29ABEFP0656L1ZU
- Privacy
- privacy@brevily.com
- Security
- security@brevily.com
Brevily is operated by Psionic Ventures LLP ("we", "us"). Read this page with our Terms of service and Acceptable use policy.
We are the data fiduciary (under India's Digital Personal Data Protection Act, 2023) and the data controller (under the UK and EU GDPR, where they apply) for the personal data described below. Our registered details are in the footer of every page.
1. The short version
We collect three kinds of data: what you give us to run an account, what we record when someone clicks one of your links, and the ordinary technical logs any web service keeps. We do not set a cross-site cookie on the people who click your links, we do not build profiles of them, and we do not sell data to anyone.
2. Data about you, our customer
What: your name, email address, organisation name, and the password hash for your account. If you buy a paid plan, your billing country and the subscription and receipt records our merchant of record, Dodo Payments, sends us. Dodo Payments collects your payment details and billing address itself; we never see or store your full card number.
Why: to give you an account, to bill you, to provide support, to tell you about material changes to the service, and, once a month when something changed, to email you what is new in the product unless you turn that off under Your account › Email me about. The lawful basis is performance of our contract with you, and our legitimate interest in running and securing the service.
How long: while your account is open, and for seven years after it closes for anything needed to satisfy Indian tax and company law. Payment and subscription records (your organisation's code and name, amounts, currency, dates, status and invoice references) are kept for that period even after the organisation is deleted. The raw messages Dodo Payments sends us about a payment, which carry the payer's name, email address and billing address, are deleted after 90 days, and the record of the payment stays. Support tickets are kept for 90 days after they close, and those about personal data or a grievance for two years.
If you ask for access: the request form keeps the name, email address, organisation, website, intended uses, link volume, whether you have a domain of your own, and the notes you type, with how many times you asked and when. The email address is stored encrypted, beside a keyed digest that lets a second request from it be recognised without reading it. Your network address is never stored: only a keyed digest of it, enough to see many requests arriving from one network, which cannot be turned back into the address without a secret key the database does not hold. Brevily's staff who handle new customers read the request; where staff alerts are on, the staff's own chat is told that a request arrived, with nothing about you. Staff record whether you were invited or declined, with an optional note. A declined request is not answered by email. The request is kept until a person decides it, then for 180 days after the decision; if you are invited, the account you then open is covered by the rest of this section. The lawful basis is the legitimate interest in answering you and in keeping the form from being flooded.
If you write to us: the contact form, and Contact support in the console, keep your name, your email address, the topic you chose and your message, with when you sent it, as a ticket. The email address is stored encrypted, beside a keyed digest that lets staff find a ticket by the exact address. For the contact form, your network address is never stored: only a keyed digest of it, enough to limit how many messages one network can send, which cannot be turned back into the address without a secret key the database does not hold. Email you send us becomes a ticket the same way. Brevily's staff read tickets in the console; where staff alerts are on, the staff's own chat is told that a ticket arrived and its topic, with nothing about you. Staff record when a ticket was handled, with an optional note. A ticket filed in the console, or an email to privacy@brevily.com, is acknowledged automatically; otherwise nothing is sent to you until a person replies. A ticket is deleted 90 days after it is closed. One about your personal data, or a grievance, is kept for two years after it is closed, as the record of how it was answered. The lawful basis is the legitimate interest in answering you and in keeping the form from being flooded.
If you report a link: the report keeps the link, the reason you chose, your note, your email address if you give one, and your network address (for an IPv6 address, its network part only), and is given a reference you can quote. Your email address and your network address are stored encrypted. Your network address is never shown to anyone: only its keyed digest is compared, to accept one open report per address on a link and to count how many different addresses reported it. Where the form's bot check is on, Cloudflare Turnstile sees your network address and your browser before the report is sent, under Cloudflare's own terms. Brevily's staff who review abuse read the report, with your email address shown to them masked. The organisation that owns the link is never shown who reported it: it is told that the link was reported and the reason chosen, never your note, your email address, your network address or anything else about you. If you gave an email address, it is used once, to tell you the outcome when the report is closed, and never the reviewer's reasons. A report stays with the record of the link it names, as the record of how that link was handled; write to privacy@brevily.com to have your email address removed from it. The lawful basis is the legitimate interest in keeping the service from being used to hurt people.
Analytics, and how to turn it off: in the European Economic Area, the United Kingdom and Switzerland, this website loads Google Analytics and Microsoft Clarity (where they are switched on) only after you accept them in its banner. The console loads them only after you turn usage analytics on under Your account, and a shared report page asks its viewer the same way. Each is told the path of the pages you open, never a search, a name or a link; Clarity also records how a page is used, with every text and field masked before it leaves your browser. The Cookies page lists what each sets and how to withdraw. Nothing is loaded for staff, and no customer's click data goes near either. Outside the European Economic Area, the United Kingdom and Switzerland, this website runs analytics by default instead of asking first. You can turn it off at any time under "Cookie settings" in the footer, and a browser that sends Global Privacy Control is treated as having turned it off.
How quickly pages load, on the same terms: once this website's analytics runs (after you accept its banner, or by default outside the European Economic Area, the United Kingdom and Switzerland), or once you turn usage analytics on in the console, a small first-party script reports how long the page you opened took to draw and to answer a tap, and how much it shifted while loading (three numbers: LCP, INP and CLS), with the page's address pattern (such as /links/:id, never an id, a search or a name). It sets no cookie and sends no identifier; the network address it comes from is used only to count how many reports one network sends in a quarter of an hour, and is never kept with the numbers. The numbers are added into fixed time ranges per page and hour, so no report can be told apart afterwards. Nothing is reported from staff pages or shared report pages.
3. Data about people who click your links
When someone follows one of your short links we record the time, the destination it was sent to, the country the request came from, the device type, operating system and browser family, the browser's user-agent string, the referring site where the browser sends one, whether the link was reached from its QR code, and a visitor identifier for the day, used to count unique visitors and to keep an A/B test's choice per visitor for the day. We also record a coarse location, the region and the city, as the platform in front of our redirect service reads it from the network address. No cookie is set on a short link: the identifier is a keyed hash of the network address (for IPv6, its network part), the browser's user-agent string and the short link's domain, under a random key made for each day (a calendar day in the time zone of the link's owner), kept only until the day after and never stored with the clicks, so a visitor cannot be recognised on another day or another domain and no consent banner is needed for it. Where the link's owner sends clicks to their own webhook or to Google Analytics, a pseudonymous identifier derived from it, different for each of our customers, goes with each click, and changes every day with it. Known crawlers are recorded as such and counted apart from people. We record the IP address in encrypted form for abuse investigation; it is never used for analytics or shown to you.
What we do not do: we do not set a cookie that follows anyone across sites, we do not build advertising profiles, and we do not resolve a visitor to a named individual. A cross-site cookie is set only when the link's owner turns on a retargeting pixel for a link; then the ad platform they chose sets it, under its own terms.
Events you send: when your server, your website (through brv.js and a website key) or your app (through an app key) reports what a visit led to, such as a sale, an install, a sign-up or an event you name yourself, we keep it as an event. An event records:
- its name and when it happened;
- the click and link it belongs to, where there is one;
- your own id for the event;
- the id you give for your customer, if you send one;
- its properties: up to 15 names, each with text, a number or true/false;
- for a sale reported from your server, its amount and currency.
Your customer id is what ties a person's later events to their first click, so it should be an id of your own, never an email address or a name, and properties should never hold personal data. An event records nothing about the browser or device that sent it. The address it came from (for IPv6, its network part) is used only to limit how often it may be sent, held for one minute, and is not kept with the event.
Why: so that you get click analytics, and so that we can detect and stop abuse of the service. For the analytics, and for the events you send, we act as a processor on your behalf; you are the controller of your links' click data and your events, and our Data processing terms apply. For abuse detection we act as a controller on our own legitimate interest in keeping the service from being used to hurt people.
How long: raw click records for as long as your plan shows them, as listed on the pricing page, and never less than seven days, because the daily counts are built from them; what a plan no longer shows is hidden at once and deleted 30 days later. Aggregated daily counts for longer, because they carry no identifier. The encrypted IP address is deleted after 90 days, or with its click record if that goes first. Events for as long as your plan keeps them, as listed on the pricing page, or for fewer days if your organisation chooses fewer under Settings › General. What your own choice drops is deleted at the next daily clean-up; what only the plan drops is hidden at once and deleted 30 days later, as for clicks.
4. Destinations you link to
We check a destination when a link is created or its destination changes, and again periodically while links to it are clicked, with Google Web Risk, the URLhaus list from abuse.ch, and our own heuristics. In between, we request the destination only to see where its redirects end, daily in its first week and then weekly while it is clicked; when it starts landing somewhere new, that is checked at once. We do not read the page itself. Google and abuse.ch receive the destination URL and, when it changes, the address it lands on, never your identity or your visitors'. We store the result of the check and the host name it lands on. A destination found to be phishing or malware is flagged, which stops every link to it, in every account, and a person reviews every request to lift a flag.
5. Technical logs
Google Cloud, our hosting provider, keeps ordinary request logs containing IP address, user agent, path and timestamp, for security, debugging and capacity planning. Only a sample of redirect requests is logged. They are kept for at most 30 days and then deleted.
7. Where data is held
Our services and primary database are hosted on Google Cloud. A visitor's connection is accepted at the point of Google's network nearest them, and each click is processed and stored in our hosting region. Where data leaves India or the European Economic Area, we rely on the transfer mechanisms our providers offer, including standard contractual clauses.
8. Your rights
Depending on where you live you have some or all of these rights: to know what we hold, to get a copy, to correct it, to have it deleted, to restrict or object to processing, and to withdraw consent where consent is the basis. You also have the right to nominate someone to exercise these rights on your behalf if you die or become incapacitated, as provided by the DPDP Act.
Write to privacy@brevily.com and we will respond within 30 days. We may ask you to verify your identity first.
If you are unhappy with our answer you may complain to the Data Protection Board of India, or to your local supervisory authority if you are in the UK or EEA.
9. Grievance officer
Under the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021 and the DPDP Act, our grievance officer is:
- Name: Abhinav A V
- Email: privacy@brevily.com
- Address: as published in the footer of this site
We acknowledge a grievance within 24 hours and resolve it within 15 days.
10. Security
Passwords are stored hashed, never in plain text. Secrets are encrypted at rest. Personal identifiers that need to be searchable are stored encrypted alongside a keyed digest, so a stolen table cannot be reversed against a list of common values. Access to production data is limited to the people who need it and is logged. Report a vulnerability to security@brevily.com; we will not pursue anyone who reports one in good faith and gives us reasonable time to fix it.
11. Children
Brevily is not for children. We do not knowingly process the personal data of anyone under 18. Tell us at privacy@brevily.com if you believe we have, and we will delete it.
12. Changes
We will post any change here and update the date at the top. If a change materially affects how we use your data we will email you before it takes effect.
Published 17 Nov 2026. Questions: privacy@brevily.com.