Trust

How Brevily is run, and what it keeps

What Brevily always does, what it never does, and where something is missing.

Brevily always

  • Checks every destination, before and after

    With Google Web Risk and URLhaus, when a link is made and while it is clicked.

  • Stops every link to a flagged page

    One flag covers every link to it, in every account.

  • Lets anyone check a link with a +

    Add a + to any Brevily link to see where it goes.

  • Tells you when a destination stops answering

    The link is marked and whoever made it gets an email.

  • Lets paid plans export your data, any time

    Links, and the clicks, events and audit log the plan keeps, as CSV.

  • Deletes an IP address after 90 days

    It is stored encrypted until then.

Brevily never

  • Sets a cookie on your short links

    So no consent banner for them, unless the owner adds a pixel.

  • Builds profiles of the people who click

    Nothing follows a visitor across sites.

  • Sells click data

    It goes only where the link’s owner sends it.

  • Shows a visitor’s IP address to the owner

    Owners see the country, region and city.

  • Charges per click or sends an overage bill

    Redirects are unlimited on every plan.

  • Raises the price you signed up at

    Your subscription keeps the price you signed up at.

In practice

From the first click to the day you leave

How a link is checked, what a click keeps, and how your data leaves.

Know where a link goes

Add a + to the end of any Brevily link to see where it goes, before you click. Nothing to install, and a link’s owner cannot turn it off.

  1. Without the +

    brvl.app/q3-launchGoes straight to example.com, and counts as a click.
  2. With a +

    brvl.app/q3-launch+Stops on a preview page instead: the full destination, when the link was made and its last safety check. Not counted as a click.

Click or tap the + above to see the page it opens.

https://brvl.app/q3-launch+

Where this link goes

You added a +, so this page shows the destination instead of sending you there. Nothing has been loaded from it.

Destinationhttps://example.com/campaigns/2026/q3-launch/landing?utm_source=newsletter&utm_medium=email&utm_campaign=q3
Short linkbrvl.app/q3-launch
Created2 September 2026
Destination checksNot listed. Last checked 30 Sep 2026.
Continue to example.comReport this link

Checks say what is known, not that a page is safe. A destination can change after it is checked, so read the address before you continue.

An example: the page the redirect edge serves for brvl.app/q3-launch+. Nothing is loaded from the destination until you choose to continue.

When a destination is harmful

A flag belongs to the destination, so one flag stops every link to it.

  1. Checked when the link is made, and whenever its destination changesGoogle Web Risk, URLhaus and Brevily’s own checks
  2. Checked again while it is clickedPeriodically, and at once if its redirects start landing on a new site
  3. Flagged: every link to it stopsIn every organisation, with a warning page, and no new link can point there
  4. A person reviews itThe owner fixes the destination and asks; editing alone never lifts a flag
  • Anyone can report a link without an account, and a person reviews every report. Reports can put a warning in front of a link and send it for a check; reports alone never block it
  • Every owner whose link is flagged, or reviewed, is told by email

Report a linkWhat gets a link stopped

What a click records

A click is counted and described in a few words. Nothing about the person who clicked is kept.

Recorded

  • The time, the link and where it sent the visitor
  • Country, region and city
  • Device type, operating system and browser
  • The browser’s user-agent string
  • The referring site, and whether it was a QR scan
  • A visitor code for the day, to count unique visitors
  • The IP address, encrypted, deleted after 90 days

Never recorded

  • A name or an email address
  • What the visitor does on the page
  • A profile that follows anyone across sites
  • Anything sold to anyone

How long it stays

Free shows daily totals only, for 30 days. Starter shows each click for 90 days and daily totals for 180 days. Pro shows each click for 180 days and daily totals for 365 days. Business shows each click for 365 days and daily totals for 730 days.
Plan Each click Daily totals
Free Totals only 30 days
Starter 90 days 180 days
Pro 180 days 365 days
Business 365 days 730 days
  • A visitor is told apart for one day (in the time zone of the link’s owner) by a keyed hash of their network, browser and the link’s domain, under a key made fresh each day, kept only until the day after and never stored with the clicks
  • Known bots are counted apart, in the numbers and in anything sent on
  • Each click is kept at least seven days on every plan, since the daily totals are built from it. What a plan stops showing is hidden at once and deleted 30 days later, so an upgrade in between shows it again.

Your data leaves when you say

On a paid plan your data comes with you, and nothing lingers after you go.

Export

On a paid plan: your links, and the clicks, events and audit log it keeps, as CSV at any time.

Delete

The owner asks, with their password, and can cancel until the day. After 30 days its people are erased, keys revoked and links deleted; billing and audit records stay, as the law requires.

Payments

Dodo Payments, the merchant of record, takes the payment and adds any tax. Card details go to Dodo, never to Brevily.

Providers

Who else handles data

The service providers that receive any of it, and what each receives.

Provider What for What it receives
Google Cloud Hosts the website, the console, the redirects and the database; queues clicks and caches link data Everything Brevily stores, and clicks in transit
Cloudflare Sends email, runs the bot check on the sign-up, report and contact forms, and answers DNS for Brevily's own domains The address an email goes to and what it says; for the bot check, a visitor's network address and browser
SendGrid and Resend Back-up email delivery, used only when Cloudflare cannot send The address an email goes to and what it says
MXroute Hosts Brevily's own mailboxes, where email sent to Brevily arrives The email you send to Brevily, kept until it is filed as a ticket and for a week after
Dodo Payments Merchant of record: payments, tax and invoices Billing name, address and payment details
Google Web Risk Checks destinations against lists of unsafe sites Destination URLs only, never who made the link
URLhaus (abuse.ch) Checks destinations against its list of sites spreading malware Destination URLs only, never who made the link
Google Analytics Counts visits to this website and use of the console. In the European Economic Area, the United Kingdom and Switzerland it loads only after you accept; elsewhere it loads by default, and you can turn it off under Cookie settings. The console loads it only after you turn it on The path of the pages you open; never a link's click data, a search or a name
Microsoft Clarity Heatmaps and recordings of this website and the console. In the European Economic Area, the United Kingdom and Switzerland it loads only after you accept; elsewhere it loads by default, and you can turn it off under Cookie settings. The console loads it only after you turn it on How a page is scrolled and clicked, with every text and field masked

What Brevily does not have yet

  • No SOC 2 report or ISO 27001 certificate yet.
  • No paid bug bounty: report a vulnerability to security@brevily.com.
  • No uptime promise or SLA: the status page shows the last 90 days.

Something not answered here?

Security and procurement questions reach a person. Brevily is built by Abhinav A V, at Psionic Ventures LLP.