People who click or scan a fwdr link
For each scan we record:
- the time, which link, how it was opened (QR code, NFC tag, plain link) and any point or variables the link passes on;
- your rough location (country, state or city), worked out from your IP address with an offline database;
- the kind of device, operating system and browser, and the referring page if your browser sends one;
- for NFC tags, the tag's ID and tap counter.
We don't keep your IP address. To count how many different people scanned on a day, we keep a scrambled code made from your IP address and browser that changes every day and can't be turned back into either. Redirects set no cookies. The link's owner sees these statistics in summary.
Visitors to this website
When you open a page of fwdr.link itself (not a short link), we count the visit the same way: the page, the time, the referring site (its name only, not the full address), the campaign tag in the address (utm_source) if there is one, your country and kind of device, and the daily scrambled code. The count uses no cookies, keeps no IP addresses, and uses no outside analytics or advertising services. For automated visitors (search engines, AI crawlers) we record the name they give.
Calls to our API
When you or your agent call our API (fwdr.link/v1 and /api), or a script or bot asks fwdr.link for an address that doesn't exist, we record the time, which call it was (its route, never what you sent or the query string), the answer's status and error code, how long it took, the name your software gives, your account if you used a key (never the key), and the daily scrambled code. Calls to the free QR code generator are recorded without the scrambled code. We use this to see where callers get stuck, and keep it for 90 days.
Customers (people and agents with an account)
We collect your email address if you sign up with one, your API keys (stored only in scrambled form), your links with their targets and variables, your balance and every charge and top-up. For top-ups and pay-as-you-go we record the paying wallet address, the refund address you give, the transaction and the amount, with the US-dollar to Australian-dollar rate on the day. Payments on a blockchain are public and permanent; we can't change or remove them.
If you sign in at fwdr.link/login, we set one cookie that keeps you signed in, for up to 30 days after your last visit or until you sign out. Nothing else on fwdr.link sets cookies.
If you sign in with Google or GitHub, they tell us your email address, your name and your account id there; we use these only to sign you in and keep no access to your Google or GitHub account.
Feature requests and abuse reports
We keep what you write and any contact you give. To limit spam we keep a scrambled code of your IP address, never the address itself. Contact details are never shown publicly.
The free QR code generator
The text or address you turn into a QR code is sent to our server to draw the code and is not kept. A logo you choose on the generator page stays in your browser and is never sent to us. A logo sent through the API is used in memory for that one answer only, and is not stored or logged. To limit how many codes one place can make, we count calls under a scrambled code of your IP address. That count is kept in memory only, never in our database, and is forgotten about a day after your last call.
How we use it
To run fwdr (forward links, count scans, charge, top up), to keep it safe (check targets, stop abuse), to answer you, and to keep the business and tax records the law requires. We don't sell personal information or use it for advertising.
Safety checks
When a link is made or changed, we send its target address and text taken from that page to services that check it: Google Web Risk and AI models through OpenRouter. These contain no information about the people who scan your links.
Who we share it with
Services that run fwdr for us, only for that purpose:
| Service | What for | Where |
|---|---|---|
| Railway | hosting and database | Singapore (US company) |
| Resend | sending and receiving email | Japan (US company) |
| OpenRouter and the AI model providers it uses | safety checks of targets | United States |
| Google Web Risk | safety checks of targets | United States |
| Coinbase (x402 facilitator) | checking and settling USDC payments on Base | United States |
| NEAR x402 facilitator | checking and settling USDC payments on NEAR | independent operator |
| NEAR Intents (1Click) | turning top-ups in other coins into USDC | decentralised network |
| Google, GitHub | signing you in, if you choose to | United States |
This product includes GeoLite Data created by MaxMind, available from www.maxmind.com. The database runs on our own server; no information is sent to MaxMind.
How long we keep it
Scan records: as long as the link's account exists. Email sign-up and sign-in codes: deleted once used, and expire after 15 minutes. Account and payment records: while the account exists, and payment records for five years after, as Australian tax law requires. Records of API calls: 90 days.
Your rights
Email us to see what we hold about you, to correct it, or to have it deleted (where we don't have to keep it by law). We'll reply within 30 days. If you're unhappy with our answer, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.
Changes
We'll post changes here with a new date, and email account holders about important ones.