Privacy Policy

taplee.link is operated by [legal entity name], ABN [ABN], of [registered address], Australia. We handle personal information in line with the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs).

We play two different roles:

• Our own information. For creator accounts, billing, sign-in and our analytics, we decide why and how the information is used. We are responsible for it.
• Information creators collect. When a creator collects details from visitors or buyers through their page (form submissions, buyer details for their sales), the creator decides why and how that information is used. The creator is responsible for it, and taplee.link acts as a processor, or service provider, storing and handling it on the creator’s behalf and on their instructions.

• Email address, used to sign you in (we email you a one-time code), send notifications you turn on, and contact you about your account.
• Your page content: handle, text, links, images, theme, form designs, product details, uploaded files, discount codes and QR code settings.
• Payment and payout details. These go to Stripe, not us. Stripe collects your identity and bank details when you connect an account, and your card when you subscribe to Pro. We never see or store card numbers. We keep Stripe reference IDs, your plan and subscription status, and whether your Stripe account can take payments.
• Sign-in and session data. A hashed login code (we don’t keep the code itself), a one-way hash of your IP address used to limit repeated attempts, and for each signed-in session a hashed session token, the browser’s user-agent text, and when it was last used.
• Sales records: orders, amounts, platform fees, discount codes used and the buyer’s email address (see below).
• Affiliate records: which creator referred which creator, the visits to a creator’s page or join link that led to a referral, and the commissions earned and paid. A creator who referred you can see your page handle, whether you are on Free or Pro, when you joined and what they have earned from you. Because commission includes part of the platform fee on your sales, their earnings reflect your sales volume, but they can’t see your email, individual orders or your buyers.

If you email us we keep that correspondence so we can help you and keep a record of it.

When someone opens a creator’s page, clicks a link, scans a QR code, submits a form or buys a product, we record an event so the creator can see how their page is doing. We do this without cookies and without storing IP addresses. Each event stores:

• the time, the page, and which link, QR code or product it relates to;
• the type of event: view, click, form submission, checkout start, purchase or QR scan;
• the referring website’s domain (for example instagram.com), not the full address;
• campaign tags (utm_source, utm_medium, utm_campaign) if they are in the link;
• an approximate location: country and region only, taken from the visitor’s network address by our network provider, Cloudflare, at the time of the request;
• device type, browser and operating system, worked out from the user-agent text (we don’t keep the user-agent text itself);
• the sale amount and currency, for purchase events;
• whether the visit looks automated (a bot).

To count unique visitors without tracking them, we compute a one-way hash of the visitor’s IP address, user-agent text and the page, mixed with a secret and a random salt that is replaced every day. We store the hash, not the IP address or user-agent. Old salts are deleted after about a day, so a hash cannot be matched to the same person on a different day, and we cannot reverse it to an IP address. These hashes are used only to count unique visitors on a given day.

The one exception is the referral cookie described under “Cookies” below. It is separate from page analytics; it only tells a creator how many browsers they brought to taplee.link.

Because the data does not identify individual visitors, we don’t treat these events as visitors’ personal information in the ordinary sense. We describe them here anyway so you can see exactly what happens. Creators see only totals and breakdowns (for example, views by country or by referrer), never an individual visitor’s record.

Our network provider, Cloudflare, necessarily handles visitors’ IP addresses to deliver pages and protect the service from attacks. Short-lived rate limits that protect forms, sign-in and checkout also use the IP address, held in the API server’s memory and not written to our database.

Creators can add forms to their pages. When a visitor submits one, we store the answers the visitor gives, a copy of the field labels as they were at the time, the time of submission, and whether the visitor ticked the consent box (if the creator included one). We don’t store the visitor’s IP address with the submission. Submissions are visible to the creator in their dashboard and can be exported by them as a CSV file. If the creator turns it on, we also email each submission to the creator.

The creator is the controller of this data and taplee.link is their processor. That means:

• The creator decides what to ask for and why, and is responsible for telling visitors how their details will be used (for example, by linking their own privacy policy).
• The creator must have their own lawful basis and a legitimate reason for collecting the data, and must collect only what they need.
• Marketing emails and SMS must comply with the Spam Act 2003. A visitor’s consent must be genuine, and the creator is responsible for honouring it and for including a working unsubscribe. A consent tick-box in a taplee.link form helps, but it is the creator’s responsibility to word it properly and to keep the record.
• We use form data only to provide the service to the creator: to store it, display it, export it, email it to them and keep it secure. We don’t use it for our own marketing and we don’t sell it.

If you are a visitor and want to see, correct or delete something you submitted through a creator’s form, please contact that creator first, because they hold the relationship with you. If you can’t reach them, email privacy@taplee.link and we will pass your request on to them, and help where we reasonably can.

On the Free plan, submissions beyond 100 in a calendar month are still stored but are locked until the creator upgrades. They remain subject to the same protections and retention as other submissions.

When someone buys a product from a creator, they pay on a page hosted by Stripe, which collects their payment details and email address. We never see their card number. We receive and store the buyer’s email address, the order (product, amount, discount code, fees and status) and Stripe reference IDs.

We use the buyer’s email only to send the receipt and the access link to their purchase, and to resend it if the creator asks. We don’t use it for marketing. The access link for a file product is valid for 30 days and allows up to 5 downloads. The creator can see the buyer’s email and order in their sales list, and the creator is the seller and the controller of that information. Stripe also holds its own records of the payment under its own privacy policy.

Analytics: no cookies. Our analytics are cookieless, so visitors to a creator’s page don’t need a cookie banner because of them.

Creator pages: one referral cookie. When someone opens a creator’s page (taplee.link/handle), we set a first-party cookie so we can credit that creator if the visitor later signs up for taplee.link.

• tl_ref: lasts 90 days. It records which creator’s page the visitor saw first, plus a random visitor ID. It is set once and is not overwritten by later visits to other creators’ pages.
• tl_join: lasts 7 days. Set only when the visitor opens a creator’s join link (taplee.link/join/handle). It records that creator.

These cookies are used only for the creator affiliate programme: if the visitor signs up, we use them to record who referred them. They are not used for advertising, analytics or tracking across other websites. Visitors can delete them at any time in their browser settings. We do not currently show a cookie banner.

The app (when you are signed in): two strictly necessary cookies.

• taplee_session: keeps you signed in. It is HTTP-only, so scripts on the page can’t read it.
• taplee_csrf: protects your account from requests forged by other websites.

Both last up to 30 days (the session is extended while you keep using the app) and are removed when you log out. They aren’t used for tracking or advertising, and the service can’t work without them. We don’t use advertising or third-party analytics cookies.

Pages with a form or the sign-in page load Cloudflare Turnstile, a bot-check, from Cloudflare. Cloudflare handles that check under its own policies.

• to provide, secure and support the service, including signing you in and sending you the codes and notifications you ask for;
• to process payments, subscriptions and payouts through Stripe;
• to give creators analytics about their own pages;
• to run the affiliate programme: crediting referrals and calculating and paying commissions;
• to prevent spam, fraud and abuse, and enforce our terms;
• to meet our legal obligations, such as tax and record-keeping.

We don’t sell personal information. We use these providers to run taplee.link, and they handle information only for that purpose:

• Stripe: payments, Connect payouts for creators, and Pro subscriptions. Stripe is also an independent controller of the information it collects for its own regulatory purposes.
• Cloudflare: our website hosting and network (Workers, DNS, the security and caching layer), file storage (R2) for uploaded images and private product files, and the Turnstile bot check.
• DigitalOcean: hosts our application servers and the managed MySQL database that stores account, page, order and form data.
• [email provider]: sends our emails (sign-in codes, receipts and access links, and form notifications).
• Google Safe Browsing: when a page is published, the link addresses on it are sent to Google to check whether they are known to be unsafe.

We may also disclose information when the law requires it (for example, a valid court order), to protect people from harm, or as part of a sale or restructure of our business, in which case the new owner must honour this policy.

Some of these providers handle information outside Australia. Stripe and Cloudflare operate global networks, and information may be processed or stored in the United States and other countries where they operate, including the countries of their own sub-providers. The region in which our DigitalOcean database and servers run is [DigitalOcean region, e.g. Sydney (SYD1)]. [email provider] may store data in [email provider locations]. Our file storage (R2) is [R2 jurisdiction/location].

Before we disclose personal information overseas we take reasonable steps to make sure the recipient handles it consistently with the APPs, such as by using providers with contractual privacy and security commitments. By using taplee.link you understand that information may be sent to these providers overseas.

• Raw analytics events: kept for about 13 months, then the monthly batch they sit in is deleted. Free creators can view only the last 30 days, but events older than that are still stored until the 13-month limit.
• Daily analytics totals (counts of views, clicks and so on, with no visitor hashes): kept until the creator’s account is deleted.
• Daily salts used for visitor hashes: deleted after about a day.
• Sign-in codes: deleted after one day. Sessions: end when you log out or after 30 days without use, and expired sessions are deleted.
• Form submissions: until the creator deletes them (they can delete single submissions or all of them) or the account is deleted.
• Orders and buyer emails: while the creator’s account exists, and afterwards for as long as we need them for tax, accounting or dispute purposes: [retention period, e.g. 7 years].
• Account, page content and uploaded files: until you delete them or close your account. When an account is deleted, its pages, form submissions and analytics are deleted with it. Backups are overwritten in the ordinary cycle within [backup retention period].

We protect information with measures such as encrypted connections, hashed tokens and codes, private storage for product files with short-lived download links, bot and rate-limit controls, and restricted access to our systems. See our Security page for the plain-English detail. No system is perfectly secure. If a data breach is likely to cause serious harm, we will follow the Notifiable Data Breaches scheme and notify affected people and the Office of the Australian Information Commissioner (OAIC).

You can ask us for the personal information we hold about you, ask us to correct it, or ask us to delete it. As a creator you can also do much of this yourself:

• edit or delete your page content, products, forms and QR codes in the dashboard;
• delete individual form submissions, or all of them;
• download your data from Settings → Your data, and delete your account from there. If a self-serve option isn’t available for something you need, email us.

Email privacy@taplee.link for any request. We may need to confirm who you are first, and we will respond within a reasonable time (normally within 30 days). We can refuse a request where the law allows, and we will tell you why. For information that a creator controls (form and buyer data), we will direct you to the creator, as explained above.

If you think we have mishandled your information, email privacy@taplee.link with the details. We will acknowledge your complaint and aim to respond within 30 days. If you’re not satisfied, you can complain to the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au.

We may update this policy as the service or the law changes. The date at the top shows the current version, and we’ll tell creators about material changes by email or in the dashboard.

Privacy contact: privacy@taplee.link, or by post to [registered address].