Effective date: 26 February 2026
Last updated: 15 November 2026
Version: 1.0
CompactSaaS provides web analytics and related services to businesses ("Customers"). Our Customers add a tracking script to their websites, and we collect data about their website visitors ("End Users") to provide analytics dashboards and reports.
This policy covers:
We collect the minimum data necessary to provide our services. We do not sell personal information. We do not use cookies for tracking. We do not collect form inputs or passwords from End Users.
Key facts:
CompactSaaS is operated by Compact SaaS Pty Ltd (ABN 75 680 223 965, ACN 680 223 965). Our contact details for privacy enquiries are:
In this policy, "we", "us", and "our" refers to CompactSaaS. "You" refers to either a Customer or an End User, depending on context.
When you create a CompactSaaS account, we collect:
| Information | Purpose | Source |
|---|---|---|
| Email address | Account authentication, billing notifications, service communications | Provided by you during sign-up |
| Name (contact name or team display name) | Account identification, billing records | Provided by you during onboarding |
| Phone number (optional) | Account contact | Provided by you during onboarding |
| Country and industry | Business classification for billing | Provided by you during onboarding |
| Company size | Business classification | Provided by you during onboarding |
| Tax ID (e.g. ABN) | Tax compliance, invoicing | Provided by you during onboarding |
| Billing address | Invoicing, tax calculation | Provided by you during onboarding |
| Payment method details | Processing payments | Collected by Stripe (our payment processor) — we do not store card numbers |
We also generate and store:
When an End User visits a Customer's website that has our tracking script installed, we collect:
| Information | Purpose | Stored? |
|---|---|---|
| IP address | Received with every request. Our content delivery network uses it to work out approximate location; it is not an input to any visitor or session identifier | Not in analytics records. Kept for limited periods in the access and security logs listed in Section 2.5 |
| Page URL and page title | Analytics (which pages are visited) | Yes — retained per retention policy |
| Referrer URL | Analytics (where visitors came from) | Yes |
| User agent string | Browser, operating system, and device type detection | Yes |
| Screen resolution | Device analytics | Yes |
| Browser language | Language analytics | Yes |
| Country, region, and city | Geographic analytics | Yes — worked out from the IP address by our content delivery network at the network edge; we receive the location |
| Referrer URL | Traffic source attribution | Yes, if present |
Campaign tags in the address of the page the visitor arrived on: the values of utm_source, utm_medium, utm_campaign, utm_content and utm_term, when the address has them. For the standard tracking script, these are the only values from the query string of the page address that we store (the referrer is a separate row); the advanced script and the API record the page address as the Customer's site sends it (see Page URL above) | Traffic source attribution for the Customer: which campaign and channel (for example paid search, social or email) brought a visit | Yes — each value is kept as an attribute of the page view or event record, with control characters removed and cut at 256 characters. Kept for as long as the record (see 4.3). The daily summaries keep only the count per channel, not the values |
| Custom event name and event data | Custom analytics events defined by the Customer | Yes — event names truncated to 100 characters, data values to 500 characters |
What we do NOT collect from End Users:
Visits are grouped into sessions with a random session identifier that the tracking script creates and keeps in sessionStorage until the browser tab is closed (see Section 10). If a request arrives without a session identifier, our servers give it a new random one.
When the persistent browser identifier described in Section 10 is used, it counts returning visitors on that website. Otherwise each session counts as one visitor, so someone who comes back in a new tab or on another day is counted again. A click on a short link, redirect or QR code has no session, and each click gets its own random identifier.
We do not derive visitor or session identifiers from IP addresses. Analytics records created before we made this change may carry a visitor identifier that was a SHA-256 hash of the IP address, browser user agent and website ID, shortened to 16 characters, and some of those records use the same value as their session identifier. We treat all of these identifiers as personal information.
When Customers use our dashboard or API, our infrastructure automatically logs:
Every request to our services carries the sender's IP address, as it does with any website. We do not write End User IP addresses into analytics records, and we do not use them to build visitor or session identifiers. The records that do keep IP addresses are:
Click log: for each short-link, redirect and QR-code click, our content delivery network writes a record into a log stream that we keep for 24 hours. The record holds the time, the address requested, including any query string, the response status, the user agent, referrer and country, the location that served the request, how long it took and the identifier of the domain it was served for. It does not include the visitor's IP address. We use it to count clicks and to record clicks in the link's analytics; the query string of the address requested is not copied into the link's analytics.
Our tracking endpoint also receives the IP address with each request. Our content delivery network uses it to work out approximate location and our servers may use it, in memory only, to limit request rates. We do not store it.
We collect Customer information when you:
Our Customers install a JavaScript tracking script on their websites. When an End User loads a page, the script sends a request to our tracking endpoint containing the data described in Section 2.2.
The tracking script:
Customer account data and End User analytics records are stored on Amazon Web Services (AWS) infrastructure in Northern Virginia, United States. This means personal information about both Customers and End Users is transferred to and stored in the United States. Requests for short links, images and the tracking endpoint are first handled at AWS network edge locations near the visitor, and the logs of our edge functions are kept in the AWS regions where those functions run (Section 7).
See Section 7 for more information about overseas disclosure.
We implement the following security controls:
By default, End User analytics data is kept without a fixed expiry date. For each website, the Customer can choose instead to have analytics data deleted after 90, 180, 365, 730 or 1,825 days. A choice applies to data recorded after it is made; data already recorded keeps the period that applied when it was recorded.
| Data type | Retention period | How it ends |
|---|---|---|
| End User analytics events (page views and events) | No fixed expiry by default, or the period the Customer chose: 90, 180, 365, 730 or 1,825 days | When a chosen period ends, our database deletes the record automatically, usually within a few days |
| End User sessions | The same as the website's analytics events | As for analytics events, and a copy of the session record is kept in the analytics archive |
| End User analytics rollups (daily summaries) | No fixed expiry date while the website exists | Not deleted automatically when analytics events expire. Deleted after the website is deleted, as set out for deleted analytics websites below |
| Analytics archive | Copies of session records whose retention period has ended: up to seven years | Deleted automatically after seven years. A deleted copy can still be recovered for about one more year |
| Analytics exports (Section 6.4) | The download link works for 10 hours. The export file is deleted one to two days after it is created | Deleted automatically; a recoverable copy is kept for one to two more days |
| Backups | Point-in-time database recovery for 35 days; monthly backups for 366 days | Deleted automatically |
| Service logs | Most application logs 30 or 90 days; API and MCP access logs 30 days; API key check logs 90 days; billing aggregation logs 120 days; short-link click delivery records 24 hours. Some other operational logs, including those written by our build, deployment, testing, performance-tuning, alarm and usage-billing systems, have no fixed expiry date | Deleted automatically where a period applies |
| Security audit logs | Up to 365 days | Deleted automatically. A deleted file can still be recovered for about one more year |
| Customer account data | Retained while the account is active | Closing an account removes its team and membership records, stops its API keys working and switches off its short links and redirects. Its other records, including websites and their analytics data, short links, redirects, QR codes and custom domains, are kept until you ask us to delete them. We then delete them, and your login if you belong to no other account, except the billing and invoice records below |
| Billing and usage records | 13 months | Automatic TTL expiration |
| Tax and invoice records | 7 years (tax compliance) | Automatic TTL expiration |
| API keys | Retained until revoked by the Customer or the account is closed | A revoked key stays on record as revoked until the account's records are deleted on request |
| Analytics websites the Customer deletes, including one created for a short link, redirect or QR code | A 7-day grace period | A deleted website disappears from the dashboard and stops collecting new analytics within about a minute. For 7 days we can restore it if the Customer asks. When the 7 days end, our database deletes the website's record (its name, domain and any link details stored with it), usually within a few days, and an automated clean-up, which runs when we release a back-end update to our dashboard service, deletes the website's daily summaries. The clean-up leaves the daily summaries of a website that a short link, redirect, bio page or wallet pass the Customer has kept still uses to show click history, until that item is deleted, and of a website under a legal hold. The other analytics data already recorded for it (individual page views, events and sessions, and the copies in the analytics archive) is not deleted with it: it keeps the website's retention period above, and the Customer can contact us to ask for its deletion |
| Short links, redirects and QR codes | Retained until the Customer deletes them | Deleting a short link or redirect also removes it from our edge network, so it stops redirecting within about a minute, and deletes the analytics website created for it as above. Deleting a QR code also deletes the tracked short link created with it. A short link the Customer created separately and attached to a QR code is kept, as is the short link of an older QR code made from a web address; the dashboard says which applies before the Customer confirms |
| Data under a legal hold | As long as a legal claim, investigation or legal obligation requires, even if a period above has ended | Released when the hold ends |
Daily rollups hold, for each website and day, its totals (pageviews, events, visitors, sessions and bounce rate), the most common pages, referring domains, browsers, operating systems, devices, countries, regions, cities, screen sizes, languages and event names with their counts, and a compact record derived from hashed visitor identifiers that is used to estimate distinct visitors over a period. They hold no individual events, query strings, page titles or IP addresses. On a website with little traffic, a day's figures may describe a single visit.
The periods above (other than legal holds), and where each copy of the data is held and what enforces its period, are recorded in our internal data map and the records it cites (version 1.9, 12 November 2026), and we update it when a period changes.
We collect, use, and hold Customer information for the following purposes:
We do not use Customer information for marketing purposes beyond service-related communications. We do not sell Customer information.
We collect and use End User information solely to provide analytics services to our Customers. Specifically:
We do not:
We disclose personal information to the following categories of recipients:
| Recipient | Information shared | Purpose | Location |
|---|---|---|---|
| Amazon Web Services (AWS) | All data (as infrastructure provider) | Hosting, compute, storage, email delivery | United States (Northern Virginia); edge locations in other countries (Section 7) |
| Stripe | Customer name, email, team ID, tax ID, billing address, payment method | Payment processing, subscription management, invoicing | United States |
We do not disclose End User analytics data to any third party. A Customer's analytics data is accessible only to that Customer, unless the Customer publishes it through a public share link.
Public share links: Sharing is off by default. A team owner or administrator can create a public share link for each of the team's websites. Each link covers one website, and creating a new link for a website stops its earlier link from working. Anyone who has the link can, without logging in, view the website's name and domain and its aggregate analytics for a period of up to one year that they choose: the total pageviews, visitors and events; the pageviews, visitors and events for each day; and the ten pages, referring domains, browsers and countries with the most activity. A share does not show individual visits or events, query strings or page titles. Page paths are shown as the website records them, so anything a page path contains is visible to anyone with the link, and on a website with little traffic, or over a short period, a figure may describe a single visit. Every share link expires 7, 30, 90 or 365 days after it is created (30 days unless the Customer chooses otherwise). Any member of the team can turn a share off or delete it at any time, and deleting the website or the team ends its shares. The share page asks search engines not to index it, but anyone with the link can still view it.
QR codes: Anyone who has a QR code can read what it holds. An untracked code holds its content in its image. A tracked Wi-Fi or contact code sends the scanner to a short link that carries the details inside the link, so a person needs the link or the printed code to read them. For a code of any other type (URL, email, phone, SMS, location or event), anyone who has the code's two identifiers can also read its name, type and content, without logging in, from a public address of ours. That address does not return Wi-Fi passwords or contact details, tells browsers and caches not to keep a copy, and we limit how many requests one internet address can make to it. The Customer chooses what goes into a QR code and should not put in anything that must stay private.
We may disclose personal information if required by law, regulation, or legal process (such as a court order or lawful request from a government authority).
You have the right to request access to the personal information we hold about you, and to request correction of any information that is inaccurate, out of date, incomplete, or misleading.
To make a request, contact us at privacy@compactsaas.com. We will respond within 30 days.
You can also directly access and update much of your information through the CompactSaaS dashboard:
If you are an End User and wish to access or correct personal information we hold about you, please contact us at privacy@compactsaas.com. Because we do not collect directly identifying information about End Users (no names, emails, or accounts), we may need to work with the relevant Customer to identify the data associated with your visit.
Note that our analytics data is pseudonymous. Session identifiers are random values, created in the browser or by our servers, and a visitor identifier is either a random browser identifier or the session identifier. Older records may carry a visitor identifier that was a hash of the IP address, browser user agent and website ID (see Section 2.3). We treat all of these as personal information. Geographic data is approximate (city-level at most). We do not hold enough information to identify a specific individual from our analytics data alone.
We may refuse access to personal information in limited circumstances permitted by the Privacy Act, such as where providing access would pose a serious threat to the life or health of any individual, or would unreasonably impact the privacy of other individuals. If we refuse a request, we will provide written reasons.
A Customer can ask us, at privacy@compactsaas.com, for an export of a website's analytics data. The export is not a copy of everything we hold. It is one JSON file covering the last 365 days and the current day. It contains every page view, event and session record for the website in that period, as we store it, with every attribute stored on the record except the internal fields we use to file and find it:
In the page and referrer URLs in the file, we replace the value of any query-string or fragment parameter whose name marks it as a credential or a contact detail (for example token, password, secret, API key, email or phone), and any user name and password before the host, with [redacted]. We do not change other fields, or credentials that do not carry such a name. We send a download link that works for 10 hours. The export does not include records older than 365 days, daily rollups, the analytics archive, real-time counters, website settings, reports, segments, revenue records, short links, redirects, QR codes, custom domains, account, team or billing records, or logs. If a website holds more data than one export can read, we do not send a partial file, and we prepare the export by hand. For information outside the export, contact us at the same address and we will deal with the request individually. If the download link has stopped working, ask us at the same address and we will send a new link.
Customer account data and End User analytics records are stored and processed in the United States (Northern Virginia). This applies to both Customer account data and End User analytics data.
Requests for short links, images and the tracking endpoint are also handled at AWS network edge locations near the visitor, which can be in other countries. Our edge functions run in AWS regions in Australia, Brazil, Germany, India, Ireland, Japan, Singapore, South Korea, the United Kingdom and the United States, and the logs they write are kept in those regions for 30 days.
Our third-party service providers are located in:
| Provider | Country | Safeguards |
|---|---|---|
| Amazon Web Services | United States; edge locations and edge-function regions in the other countries listed above | AWS Data Processing Addendum; AWS states that it holds SOC 2 reports and an ISO 27001 certification |
| Stripe (including its affiliate Sold Through Link, LLC and Link, which handle payments for Customers outside Australia) | United States | Stripe Data Processing Agreement; Stripe states that it is PCI DSS Level 1 certified |
We rely on contractual controls (data processing addendums) with our infrastructure providers to ensure that personal information is handled consistently with the Australian Privacy Principles.
If you are located in Australia, your personal information will be transferred to the United States when you use our service. By using CompactSaaS, you acknowledge this transfer. If you are a Customer deploying our tracking script on a website with Australian visitors, you should disclose this overseas transfer in your own privacy policy and collection notices.
If you believe we have breached the Australian Privacy Principles or handled your personal information inappropriately, you can make a complaint by contacting us at:
We will:
If you are not satisfied with our response, you may lodge a complaint with the Office of the Australian Information Commissioner (OAIC):
CompactSaaS acts as a data processor on behalf of our Customers. Our Customers are data controllers who determine the purpose of collecting analytics data about their End Users.
If you are a CompactSaaS Customer, you are responsible for:
If you deploy our tracking script on a website where the subject matter could reveal sensitive information about visitors (for example, a mental health service), you should obtain express consent from your End Users before enabling analytics tracking, as the mere act of visiting such a website may constitute sensitive information under the Privacy Act.
CompactSaaS does not use cookies for analytics tracking.
Our tracking scripts do not set cookies. They use the following browser-storage keys on the Customer's website. Each key is scoped to that one website, so it cannot be used to recognise an End User across different Customers' websites.
| Key | Store | Lifetime | Purpose |
|---|---|---|---|
aa_visitor_id | localStorage | Until the End User clears site data (the script sets no expiry) | A random, pseudonymous visitor identifier used to count returning visitors on that website. Written only by the advanced tracking script, and only when none of the controls below applies. |
aa_session_id | sessionStorage | Until the browser tab is closed | Groups the page views of one visit into a session. |
analytics_session | sessionStorage | Until the browser tab is closed | Groups the page views of one visit into a session. |
Controls. The persistent visitor identifier (aa_visitor_id) is not written or sent when any of the following applies, and the advanced tracking script also removes any value left by an earlier visit:
data-persistent-id="false". From the moment the setting is on, our ingestion service also ignores any visitor identifier a browser sends for that website, even before the snippet is updated.When the persistent identifier is not used, each browser session counts as one visitor (see Section 2.3); we do not build an identifier from the IP address instead. If the browser blocks storage, the scripts write nothing and keep working with values held in memory for that page load only.
These controls apply to browser tracking. On the server-to-server API (/v1/track), the Customer supplies the visitor identifier and is responsible for honouring their visitors' privacy preferences; when the "No persistent visitor ID" setting is on, /v1/track drops any supplied visitorId.
Our Customer dashboard (the CompactSaaS web application) uses standard authentication cookies managed by our identity provider for maintaining your login session. These are strictly necessary for the functioning of the dashboard and are not used for tracking or analytics purposes.
We may update this privacy policy from time to time to reflect changes in our practices or legal requirements. When we make material changes, we will:
We encourage you to review this policy periodically.
For any questions, concerns, or requests related to this privacy policy or our handling of personal information:
This privacy policy was last reviewed on 26 February 2026. It applies to the CompactSaaS service operated by Compact SaaS Pty Ltd (ABN 75 680 223 965).