AffiliateRails Privacy Policy
Version: ar-privacy-au-2026-11 · Effective: 6 November 2026
The short version
- We run AffiliateRails, a partner (affiliate and referral) program platform, from Australia.
- We hold information about three groups: people who run brands' accounts, partners, and customers of brands who use a partner's code or link.
- Stripe collects partners' bank details and identity documents. We do not receive full bank account numbers or document copies.
- We do not sell personal information.
- Some of our providers are overseas. We name them below.
1. Who we are
Apptractive Pty Ltd (ABN 37 627 379 800), which provides AffiliateRails ("we", "us"). Contact our privacy officer at hello@apptractive.com.au or 79 O'Donnell Street, North Bondi NSW 2026.
We follow the Australian Privacy Principles in the Privacy Act 1988 for everything AffiliateRails does, whether or not an exemption applies to us. When we handle a brand's customer information we act on the brand's instructions, and we also use it for our own security, payments, tax, legal and dispute purposes. Both roles are covered by this policy.
2. Brand account users
If you manage a brand's AffiliateRails account, we collect your name, work email, role, the brand's legal name, ABN and address, your login and security details (including multi-factor settings), a keyed hash of your IP address when you create a brand (to stop abuse of sign-up), what you do in the account (an audit log of each action and when it happened), and your messages to us.
We use this to run and secure the account, bill the brand, give support and meet the law.
3. Partners
When you apply to a brand's program, we collect what the brand's form asks for: usually your name, email, business name, ABN and website, and how you plan to promote the brand. If you are approved, we also hold:
- your referral codes and links, and the clicks, sign-ups and sales tracked to them;
- your commissions: date, amount, status, holds and reversals;
- your ABN, entity name and GST status from the Australian Business Register (ABN Lookup), and your RCTI agreement if you give one;
- tax documents, payment and payout records;
- from Stripe: your Stripe account ID, whether your account is verified and can receive payments and payouts, your balance, payments, refunds, disputes and payouts, and any restrictions. Our system also reads your payout bank account's status, which comes with its bank name and last digits; we do not keep those. Stripe collects your identity documents and full bank details, and we do not receive them;
- which version of each set of terms you accepted, and when; and
- your messages to us and to the brand through AffiliateRails.
If you create a creator profile and choose to list it, eligible brands can see the fields you chose. You can unlist it at any time.
We use this to assess your application (with the brand), track referrals, calculate commission, arrange payment, issue tax documents, prevent fraud, handle disputes and meet tax law.
4. Customers of brands
If you buy from a brand that uses AffiliateRails, and you used a partner's code or link, the brand sends us a customer ID that it chooses (not your name), the code you used, and what you bought, when and for how much, and any refund. A brand may also send a one-way scrambled version of your email (a hash) or a keyed identity code, to link your records and stop partners earning from referring themselves. These codes can still be personal information even though they do not show your name or email.
When someone clicks a partner's link, we record the link, the page it came from, any campaign tags and the time. We do not store your IP address with the click. Click records expire after 400 days and the database then deletes them. Our web servers log IP addresses for security, as explained in section 9.
We do this for the brand, to work out which partner referred you and what commission they earn. The brand's own privacy policy also applies. Partners see their commissions and amounts, not your name or email. A partner with few referrals may still be able to work out that a sale or refund was yours.
5. Where we get information
From you; from the brand whose program you deal with; from Stripe; and from the Australian Business Register. If you do not give us what a form asks for, we may not be able to approve or pay you.
6. Who we share it with
- The brand whose program you apply to or join, or that you buy from. Brands may use it only for their program.
- Partners see their own commissions and payouts, as section 4 explains.
- Our service providers, listed in section 7, who handle it for us under contract.
- Authorities, such as the ATO, when the law requires.
- Professional advisers and a buyer of our business, under confidentiality.
We do not sell personal information. We do not use it for advertising.
7. Overseas providers
We store AffiliateRails data in Amazon Web Services in Sydney. Some providers handle information overseas:
| Provider | What it handles | Where |
|---|---|---|
| Stripe (Stripe Payments Australia Pty Ltd and its affiliates) | Partners' Stripe accounts, payments, payouts, and brands' card payments and billing | United States, India and other countries where Stripe and its providers operate |
| Amazon Web Services (CloudFront) | Our websites and portals are delivered through AWS's global network, which may cache pages and log requests (including IP addresses) near the visitor | Worldwide edge locations, including the United States |
| Google (Google Workspace) | Emails you send us, and our replies | United States and other countries where Google operates |
| Sentry (Functional Software, Inc.) | Error reports from our servers, with personal details removed where we can | United States (Iowa) |
We choose these providers carefully and use their data processing terms. Where Australian privacy law makes us accountable for what an overseas recipient does with information we send it, we remain accountable. We will update this list before adding a provider that receives personal information overseas.
8. Decisions made by computer programs
Some AffiliateRails decisions that affect a partner's earnings are made by computer programs.
Information the programs use: the partner's codes and links; clicks, sign-ups, sales and refunds tracked to them, with the brand's customer ID and any email hash or keyed identity code; the brand's commission rules; the partner's ABN, entity name and GST status from ABN Lookup; and the partner's Stripe account status, requirements, balance, payout bank account status and any risk hold.
Decisions the programs make on their own:
- working out each commission under the brand's rules and putting it on hold;
- cancelling a commission when the sale is refunded during the hold, and deducting it from later commission when the sale is refunded or charged back within 120 days after the sale;
- refusing a referral when the customer is the partner (a self-referral); and
- holding a payment or payout when Stripe says the account cannot be paid, has unmet requirements or no active bank account, when the balance is too low, when a risk hold is on, or when an ABN check fails.
Decisions people make, using the programs' output: approving or rejecting an application, suspending a partner, and rejecting a commission for suspected fraud.
If you think a decision about you is wrong, email us. A person will review it and tell you the result and the reason.
9. How long we keep it
| Information | How long |
|---|---|
| Commission, payment, payout, tax document, invoice and ABN check records | 7 years after the end of the financial year they relate to, then deleted or de-identified |
| Terms acceptance records | 7 years after the relationship ends |
| A partner's account and profile | While you are a partner, then 2 years, except the financial records above |
| Rejected applications | 12 months after the decision |
| Customer IDs and code use | While the brand's program needs them. When a brand asks us to erase a customer, we remove the email hash, the keyed identity code and other details. We keep the brand's customer ID, the code and the referral link only for the commission records above, with restricted access. They can still link to the brand's own records |
| Click records | 400 days |
| Web server and security logs (including IP addresses) | Up to 1 year |
| Database backups (point-in-time recovery) | Up to 35 days after the data is deleted |
| Emails with us | 2 years, or 7 years if they concern a payment, a tax document or a complaint |
10. Security
We use encryption, access controls, multi-factor authentication for staff and audit logs. No system is perfectly secure. If we suspect a data breach, we assess it quickly and take reasonable steps to finish within 30 days. If it is likely to cause serious harm, we tell you and the Office of the Australian Information Commissioner as soon as practicable, as the Notifiable Data Breaches scheme requires.
11. Access, correction and complaints
You can ask to see or correct your information. Email us. We may need to check who you are. We reply within 30 days. If we refuse, we tell you why.
If you have a complaint, email us. We acknowledge within one business day and aim to answer within 30 days. If you are not satisfied, you can complain to the Office of the Australian Information Commissioner (oaic.gov.au, 1300 363 992).
12. Changes
We will post any change here with a new date. If a change is significant, we will email account holders before it applies.
Optional website analytics
With your permission, Apptractive Pty Ltd uses Google Analytics on the public AffiliateRails website to understand page visits and navigation. Google receives page paths and titles, device/browser information and network information such as your IP address, and uses analytics cookies to distinguish visits. Google may process this information outside Australia.
Analytics is off until you choose Allow analytics. You can withdraw permission using Analytics preferences at the bottom of the page. Withdrawing stops future collection; it does not delete data already collected. We do not send account IDs, form contents or URL query strings, and do not enable advertising features. Event-level data uses Google's default two-month retention; aggregate reports may remain available longer.
See how Google uses information from sites that use its services.