Questions

Not at once. Your plan runs to the end of the period you paid for, then moves to Free. 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, and 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. Links on your own domain keep working until the end of the period you paid for; after that, domains 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.

Each short link created counts once against the month’s allowance: a calendar month on Free, your billing period on Pro and Business. Clicks are never charged for, so a link that goes viral costs you nothing extra. Deleting and recreating the same link twice counts twice.

A credit is one cent, and most people never spend one. Each plan has monthly allowances: links, destination edits, styled QR codes, webhook deliveries. Past an allowance, each extra use costs a few credits at the prices on the pricing page, taken from the credits the plan includes each month or from a pack you bought; without enough credits, the use waits for the allowance to reset. Credit packs are sold on Pro and Business, with the plan’s discount, and bought credits last for the months stated on the pricing page. Every charge is listed on the Credits page in the console.

Plans are monthly only, at the price shown, and can be cancelled at any time: there is no annual plan to lock into and no price that assumes a year up front. Free needs no card. 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 at once and you pay the difference for the rest of the period. 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. Pro includes five domains and Business twenty-five; Free is on Brevily’s own short domains. Adding one gives it its own CNAME target, shown on its page in the console: a CNAME there sends visitors to your links and proves the domain is yours. A root domain (northwind.com rather than go.northwind.com) is proved with a TXT record instead, because a CNAME at the root is flattened and cannot be seen, and it needs a DNS provider that offers ALIAS, ANAME or CNAME flattening at the root; where there is none, use a name under the domain.

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, and past that for a credit each on Pro and Business. 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. Chosen back-halves keep their case, and a back-half differing only by case from an existing one is refused, so PayPal can never sit beside paypal. 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, and on Pro and Business a link can ask for a password before it redirects.

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 it goes.

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 click as its install referrer, so the first launch can report where it came from. On iOS a short page offers Open in the app beside the fallback. There is no in-app event tracking, and iOS first installs are not attributed; 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, single clicks on the plans that show them. Everything downloads as CSV at any time — every link, deleted ones included, and every day’s totals — and a scheduled report can email a link’s, a domain’s or a tag’s numbers daily, weekly or monthly to people who need no account.

On a plan with conversions, 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.

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. The written guides and the reference live in the console, behind sign-in.

Yes, on a plan with integrations. 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.

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. On Business, single sign-on through your own identity provider lets people join and sign in with their work account, and the audit log records who changed what.

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 reports from several different connections send the destination for an immediate check. 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 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.