Questions

Not at once. A cancelled plan runs to the end of the period you paid for, then moves to Free. A paid plan never goes to sleep while it is paid.

On Free:

• Links on a Brevily domain keep redirecting as long as someone in the organisation signs in at least every 180 days.
• After that the organisation goes to sleep: its links show a "not in use" page.
• 90 days later they are released: a back-half you chose can be taken by someone else, and where each link pointed is deleted.
• Signing in before then wakes it.

Own domains that Free does not include show a "not active" page, and come back if you move to a plan that does. You can export every link, with its clicks, as CSV at any point.

The plan keeps working for 30 days while the payment is retried, and the owner and billing admins are emailed. If it is still unpaid after that, the organisation moves to Free, and Free's limits apply: own domains Free does not include are parked, and new links count against Free's allowances. Nothing is deleted at the move. Paying again restores the plan, and parked domains come back, the busiest first, as far as the plan has room.

Each short link created counts once against the month's allowance: a calendar month on Free, your billing period on a paid plan. Links made through the API or by import count the same way. Clicks are never charged for, so a link that goes viral costs you nothing extra. Deleting and recreating the same link counts twice.

Two ways to get more than a plan includes, without changing plan.

• Add-ons sit on the subscription and are billed with it each period: an extra own domain, an extra seat, an extra mobile app, or a sharing pack (more shared reports, saved reports and link stats pages). Lowering or removing one takes effect at once and is not refunded; the new quantity is billed from the next renewal.
• Top-ups raise a monthly allowance (links, destination edits, conversion events or deliveries to integrations) for this period or the next few, paid once. A top-up is never a balance that runs down.

The prices, and how many of each a plan can add, are on the pricing page. Free has no add-ons.

Every plan's monthly allowances reset each month: links, destination edits, conversion events and deliveries to integrations.

• On Free, a limit is a stop until the month resets.
• On a paid plan, a grace of 10% past the allowance keeps work going, at no charge. Past the grace, the use waits for a top-up, an upgrade or the reset.
• Clicks are never refused. Past the month's counted clicks (Free 10,000, Starter 100,000, Pro unlimited and Business unlimited), links still redirect, but the clicks are not recorded.
• Conversion events past the limit are refused with a clear error. Send them again after a top-up or the reset. Each event is de-duplicated, so a resend never counts twice.
• API calls past the plan's per-minute or per-day limit are refused with 429 and a Retry-After time.

Counts such as domains, seats and mobile apps have no grace: add one, or move up a plan.

On a paid plan, yes, as add-ons on the subscription, at the prices on the pricing page and up to the most each plan allows:

• Own domains: on Starter, Pro and Business.
• Seats: on the plans that include more than one. On a one-seat plan, more people means moving up.
• Mobile apps: on Starter, Pro and Business.

A report or stats subdomain on your own domain does not count as a domain.

Plans are billed monthly at the price shown and can be cancelled at any time. Where a plan is offered yearly, the pricing page shows its yearly price beside the monthly one. Free needs no card, and there is no trial: Free is the way to try Brevily. A paid plan starts with a checkout through Dodo Payments, the merchant of record, which adds the tax that applies where you are and issues the invoice; card details never reach Brevily.

A dearer plan applies as soon as the difference for the rest of the period is paid, usually within seconds; if that payment does not go through, the plan stays as it was. A cheaper plan applies at the end of the period you paid for, and the current one keeps working until then. Moving to Free cancels at the period end. A subscription keeps the price it was sold at: if a plan's price rises later, yours does not; if it falls, the console offers the lower price. Nothing is refunded.

Yes. Domains included, by plan: Starter 1, Pro 10 and Business 50; Free is on Brevily's own short domains. Add one in the console and its page shows the records to add at your DNS provider: a TXT record proves the domain is yours, and the records that point it at Brevily send its visitors to your links. A root domain (northwind.com rather than go.northwind.com) works the same way, at any provider: the records are plain addresses, so nothing needs ALIAS or CNAME flattening.

Bulk import is on Pro and Business: add a CSV of back-halves and destinations, up to 200 links at a time, and keep the same back-halves. The export columns of popular shorteners are read as they are. Once your domain points here, existing links resolve unchanged.

Yes. A link's domain and back-half never change, so anything printed with it stays right. Its destination can change as often as the plan's monthly edits allow (Free 10, Starter 100, Pro 1,000 and Business 5,000), and an edits top-up adds more for the month. The QR code encodes the short link, not the destination, so it keeps working through every change.

You can type a back-half or take a generated one. Case never matters: PayPal and paypal are the same back-half, shown as you typed it and reached however a visitor types it, so one can never sit beside the other. Generated back-halves use lowercase letters and digits only. On Brevily's own domains a chosen back-half has a minimum length by plan; on your own domain it is your choice. A link can expire by date or after a number of clicks. On Starter, Pro and Business a link can ask for a password before it redirects, at no extra cost; its + preview asks for the password too, then shows where it goes.

It goes to the one fallback chosen for that link: the app's store listing, or the web address. On Android the app opens straight away when it is installed; on iOS a short page offers Open in the app beside that fallback, because iOS will not open an app without a tap. Every other device goes to the web address. The click is counted first, whichever way the phone is sent. After installing from the store, an Android app can open the screen the link was for, which the Play Store passes on; an iPhone app opens at its start screen, because the App Store passes nothing on.

Deep links are on Starter, Pro and Business, with mobile apps by plan: Starter 1, Pro 2 and Business 5. More apps can be added to a paid plan.

No. A deep link needs only what your app already has: its Android package name or iOS scheme, and its store listing. On Android the link opens the app directly, and when the app is not installed yet the Play listing receives the link's screen, and the click, as its install referrer, so the first launch can open that screen and report where it came from. On iPhone a one-tap page offers Open in the app beside the fallback. iOS has no deferred deep links: a fresh install opens at its start screen and is not attributed. There is no in-app event tracking; an attribution SDK stays your choice if you need those.

For every link: clicks over time, unique visitors, country, device, browser, operating system, referrer, and whether the click came from a QR code, with known crawlers counted apart. Daily totals are kept for the days the plan states, and single clicks on the plans that show them; past the plan's single-click allowance, clicks still count in the daily totals. Everything downloads as CSV at any time: every link, deleted ones included, and every day's totals.

On Starter, Pro and Business, a tracked link lands on your page with a click id in the address. Your server keeps it with the visitor (a cookie, a form field, a session) and, when they buy or sign up, posts one request to the API naming the click, the event, and optionally the amount, the currency and your id for the customer. No JavaScript is needed and nothing an ad blocker stops; a small optional script is there for sites that want the cookie handled for them. A later sale by the same customer is attributed to the first link that brought them.

Each plan includes a number of events a month (Starter 1,000, Pro 10,000 and Business 100,000), and an events top-up adds more. Events are kept for as long as the organisation exists.

Everything the console does to a link, the API does too: the same routes under /api, in JSON. Make, change, disable and delete links, manage routing rules and deep links, read analytics, and report conversions. A request carries an API key's two headers, or is signed with the key so the secret is never sent. An organisation's key never holds more than the person who made it, and a personal key acts as its owner. Calls are limited per minute and per day by plan; past a limit the answer is 429 with Retry-After. The written guides and the reference live in the console, behind sign-in.

Yes. Webhooks are on Pro and Business, and Google Analytics 4 forwarding on Pro and Business. A webhook receives one signed request per human click, retried on a schedule for about seven hours before it is given up, and Google Analytics 4 forwarding sends the same clicks to your property with a pseudonymous visitor id of your organisation's own. Either can cover every link or one link. A test send shows the exact body before you rely on it. Each send to each integration, webhook or GA4, counts as one delivery. Deliveries a month, by plan: Pro 100,000 and Business 1,000,000; a deliveries top-up adds more.

People are invited, never handed a shared password. Each organisation has an owner and two system groups, Admin and Billing, and any groups you make with exactly the permissions they need: links, domains, people, billing, settings and more, each with view, edit, create and delete. Seats are counted per plan, people and pending invitations alike.

• Single sign-on, on Business: people join and sign in with their work account through Google Workspace, Microsoft Entra, Okta or any OpenID Connect provider.
• A security policy, on Pro and Business: require two-factor for every member, set the longest sign-in, and allow invitations only to named email domains.
• The audit log, on Business, records who changed what.

The owner can hand the organisation to another member, who accepts by email.

Every destination is checked with Google Web Risk and Brevily's own heuristics when a link is made, and again on a schedule while it is clicked; a flagged destination stops every link that points there, in every account, and no new link can point there. Anyone can add a + to the end of a link to see where it goes before following it, and anyone can report a link without an account: a person reads every report, and a destination held by reports shows "This link was reported" first, with Continue, while a person reviews it. Lifting a flag takes a reviewer, never an edit.

Neither. The page is never read: its address is checked with Google Web Risk and Brevily's own heuristics when a link is made or its destination changes, and again every 30 days while people click it. In between, the address is requested only to see where its redirects end, and a new landing site is checked at once. Clicks are counted with one first-party cookie on the short link's own domain and no visitor profile: country, device, browser and referrer. A cross-site cookie appears only when a link's owner adds a retargeting pixel.

Your organisation's data lives in one primary database; redirects are answered from the edge network nearest the visitor and clicks travel back through a queue. Email addresses, secrets and IP addresses are stored encrypted, and a click's IP address is blanked after 90 days. You can export every link and every day's totals as CSV at any time. The owner can ask to delete the organisation, confirmed with their password; after the grace period stated on the trust page its people are erased, its keys revoked and its links deleted, with billing and audit records kept as the law requires. The trust page and the data processing terms name every provider that handles any of it.

From the edge, in the data centre nearest the person clicking. After its first visit a link is answered from the edge's cache without a trip to the database, and the click is recorded on the way without holding the redirect up. A change you make reaches every data centre within about a minute.