Privacy Policy
Our privacy policy and how we use your data
Last updated: 1 November 2026
This policy explains how Brainium Labs Pty Ltd (ABN 44 621 469 298) (“Brainium Labs”, “we”, “us”) collects, uses and shares personal information when you use PagePot: our website, web app, share pages and API. We’re an Australian company bound by the Privacy Act 1988 (Cth) and the Australian Privacy Principles. If the EU or UK General Data Protection Regulation (GDPR) applies to you, this policy also explains your rights under it.
1. Our role
- Information about you as a user or visitor (your account, billing, support requests and website visits): we decide how it’s used, and we’re responsible for it (under the GDPR, we’re the controller).
- Information inside a workspace’s projects (for example, staff names and photos in page copy, client files or comments): we handle it on behalf of the customer who owns the workspace, under our Terms of Service. The customer’s own privacy policy applies to it. If you want to access or correct that information, contact the customer; we’ll help them respond.
2. Information we collect
| Type | What it includes |
|---|---|
| Account | Your name, email address, password (stored only as a one-way hash), profile picture, preferences, two-factor settings and how you last signed in. If you sign in with Google, we receive your name, email address, profile picture and Google account ID, and store Google’s sign-in tokens encrypted. |
| Workspace and team | Workspace name and branding (logo, colours, website), members, roles, project access, the email addresses of people you invite and any message you add to an invitation. |
| Billing | Your plan, subscription status and Stripe customer ID. Subscriptions are sold through Link (see section 5), which collects your card and billing details and keeps your invoices; we never store full card numbers. |
| Content you add | Projects, sitemaps, pages, files, diagrams, comments, approvals and metadata, plus activity and revision history showing who changed what. Files you upload may contain embedded information (such as where a photo was taken), which we don’t remove from project files. |
| Collaboration | Your name and profile picture shown to other members while you’re viewing or editing a page, in-app notifications, and notification emails. |
| Share-link guests | The name you enter to comment on a shared plan, and your comments. |
| Integrations, API and AI agents | API key names and scopes (only a hash of each key is stored), Slack workspace and channel names, webhook addresses, Drupal integration details, any crawler login details you give us (stored encrypted), and short-lived records of what was sent to Slack and webhooks. For AI agents you connect: the agent’s name and registration details, the workspace, access level and projects you chose, sign-in tokens for the connection, and when it was last used. |
| AI features | Records of AI use and credits; AI results, kept briefly so you can apply them; short page summaries; and the prompts for AI images you keep and the brief for AI-built projects. |
| Contact and support | Your name, email address, company, topic, message and IP address when you use our contact form, and emails you send us. |
| Technical | IP address, browser and device type, sign-in sessions, rate-limit and security records (which include IP addresses), and server and error logs (which can include email addresses). |
| Analytics | Pages viewed (with secret links removed), the site you came from, device and browser type and approximate location. See section 6. |
| Imported websites | Content from websites you ask us to import or crawl, which may include personal information published on those sites. |
We collect most of this from you directly. We also get information from your workspace admin (when they invite you), from Google (if you sign in with Google), from Stripe and Link (about payments), from your browser (through cookies and logs) and from websites you ask us to import.
You don’t have to give us personal information, but without an email address and name we can’t create an account for you. You can’t use PagePot anonymously, though you can browse our website and comment on a shared plan under any name you choose.
3. How we use it
| Purpose | GDPR legal basis |
|---|---|
| Providing PagePot: accounts, sign-in, workspaces, projects, share links, exports, integrations and the API | Performing our contract with you |
| Running AI features when you or your team use them | Performing our contract with you |
| Billing and managing subscriptions and trials | Performing our contract; legal obligation (tax records) |
| Sending service emails: email confirmation, password resets, invitations, notifications and reminders (Stripe sends payment receipts and billing emails) | Performing our contract with you |
| Answering support and contact requests | Legitimate interests (helping you) |
| Keeping PagePot secure: preventing abuse, fraud, spam and repeat trials, rate limiting and checking uploaded files | Legitimate interests (security) |
| Understanding how our website and app are used, to improve them | Consent (analytics cookies); legitimate interests (cookieless measurement, see section 6) |
| Meeting legal obligations and enforcing our terms | Legal obligation; legitimate interests |
We don’t sell personal information, and we don’t use it for advertising. We don’t currently send marketing emails. If we start, we’ll only send them as the Spam Act 2003 (Cth) and other applicable laws allow, and every one will have an unsubscribe link.
4. AI features
PagePot’s AI assistant uses Anthropic’s Claude models for text and for reading images (for example, to write alt text or read uploaded mockups), and Google’s Gemini models for generating images. Content is sent to these providers when someone runs an assistant action, such as drafting copy, writing alt text, generating an image or building a project from uploaded files. Requests include project context, such as the brief, the sitemap and summaries of related pages. To keep answers consistent, the assistant also refreshes short page summaries in the background for projects where someone has used it in the last 30 days.
- We don’t use your content to train AI models, and our AI providers’ commercial terms don’t allow them to use it to train theirs. They may keep it for a limited time to detect misuse.
- Files uploaded to plan an AI project are deleted once the project is created (except files you choose to keep in it), or within about 8 days if no project is created.
- Workspace admins can turn the AI assistant off for the whole workspace. When it’s off, nothing is sent to AI providers.
AI agents you connect
You can connect your own AI agent, such as Claude, ChatGPT or Cursor, to PagePot through our MCP server. You approve each connection by signing in to PagePot and choosing the workspace, what the agent can do and which projects it can reach. The agent then acts as you: it can only see and change what your project roles allow, and its changes are recorded in the project history as yours.
- When the agent asks for project information, such as pages, comments or file details, PagePot sends it to the agent. From there it goes to the agent’s provider (for example Anthropic or OpenAI) under your own account with them. Their terms and privacy policy apply to it, not ours, and we don’t control what they do with it.
- You can disconnect an agent at any time in Settings → API and AI agents. Workspace admins can disconnect anyone’s agents in their workspace, or turn agent connections off for the whole workspace.
- Using an agent doesn’t send anything to PagePot’s own AI providers and doesn’t use PagePot AI credits.
5. Who we share it with
We use the service providers below to run PagePot. They may only use personal information to provide their services to us.
| Provider | What they do | Where |
|---|---|---|
| DigitalOcean | Hosts our servers, database and file storage | Sydney, Australia |
| Cloudflare | Domain name service, content delivery, security and bot protection (including Turnstile checks on our contact, sign-in, sign-up and password-reset forms) | Global network; United States |
| Stripe and Link | Subscription billing. Subscriptions are sold through Link, Stripe’s reseller service, which handles your payment details, tax and receipts as an independent controller under the Link privacy policy | Australia; United States; Ireland |
| Twilio SendGrid | Sending email from PagePot | United States |
| Anthropic | AI text features and reading images | United States |
| Google sign-in and Google profile pictures (if you use Google sign-in), Gemini AI image generation, Google Analytics, and playing YouTube videos embedded in page content | United States | |
| Slack | Project notifications, only if a workspace connects Slack | United States |
| Vimeo | Playing Vimeo videos embedded in page content | United States |
We also share personal information:
- Within your workspace: other members can see your name, email address, profile picture and activity in the projects you share. Workspace admins can see every project in the workspace.
- Through share links: people with a link can see the shared plan, including commenters’ names and comments.
- With services your workspace connects, such as webhook endpoints, Drupal sites and Slack channels, and with AI agents that people in your workspace connect to their own accounts. Their own privacy policies apply.
- With our professional advisers (such as lawyers and accountants), where needed.
- When the law requires it, or to protect the rights, safety or property of our users, the public or us.
- In a business sale: if we sell or transfer our business or PagePot, personal information may transfer to the buyer, who must protect it as this policy describes.
A small number of our staff can access personal information when needed for support, security or to fix problems, including by temporarily signing in as a user to investigate an issue.
6. Analytics and cookies
We use Google Analytics to understand how our website and app are used. Analytics cookies are only set if you accept them in our cookie banner. Before you choose, or if you reject them, Google Analytics may still receive limited signals without cookies (for example, that a page was viewed), which Google uses to estimate overall traffic. Google Analytics doesn’t store your IP address.
We remove secrets before anything reaches Google: share-link and invitation codes are masked, page titles (which can include client project names) aren’t sent, and only campaign parameters are kept from web addresses. We don’t send your name, email address or user ID. Google Analytics data is kept for 14 months.
Our Cookie Policy lists the cookies we use and how to change your choice.
7. Overseas disclosure
Some of our providers store or access personal information outside Australia, mainly in the United States. Cloudflare processes traffic at the data centre nearest each visitor, which may be in any country where it operates. We take reasonable steps to make sure our providers protect personal information consistently with the Australian Privacy Principles, including through contracts. Where the GDPR applies, we rely on adequacy decisions or standard contractual clauses for transfers outside the EU or UK.
8. How we protect it
- All connections to PagePot are encrypted with HTTPS.
- Passwords, API keys, share links and Drupal integration tokens are stored only as hashes. AI agents connect through OAuth with short-lived access tokens that only PagePot’s MCP server accepts. Webhook signing secrets, Slack and Google sign-in credentials, and crawler login details are encrypted (AES-256-GCM).
- Project files are kept in private storage and downloaded through short-lived signed links. Profile pictures and workspace logos are stored at public, hard-to-guess addresses.
- Access is limited by role: members see only the projects they’re added to, and workspace admins see every project in their workspace.
- If you sign in with a password, you can add two-factor authentication with an authenticator app.
No system is perfectly secure. If a data breach is likely to cause serious harm, we’ll notify affected people and the Office of the Australian Information Commissioner (OAIC) as the Notifiable Data Breaches scheme requires, and other regulators where the law requires.
9. How long we keep it
- Accounts: while your account is open. When you delete it, we remove your personal information from our live systemsimmediately. Your name stays on comments, approvals, revisions and activity history in workspaces you belonged to, so those records stay accurate. Rate-limit records (keyed by IP address, not linked to your account) and server logs aren’t removed when you delete your account, and Stripe keeps billing records under its own policy.
- Workspaces: while the workspace exists. When a workspace owner deletes it, we delete its projects and files from our live systems immediately. This includes locked workspaces (after a paid plan ends) and read-only workspaces (after a trial ends): we keep their data until the workspace is deleted, and you can ask us to delete it at any time.
- Backups: deleted data stays in backups until they expire, within 7 days.
- Billing records: for as long as tax law requires (in Australia, generally five years).
- AI planning files: deleted once the project is created (except files you keep), or within about 8 days.
10. Your rights
You can ask to access the personal information we hold about you, or to correct it. You can update most account details yourself in your profile settings, and you can delete your account there.
If the GDPR applies to you, you can also ask us to erase your information, restrict or object to how we use it, or give you a copy in a portable format. Where we rely on your consent (such as for analytics cookies), you can withdraw it at any time.
To make a request, email [email protected]. We may need to confirm your identity first. We’ll respond within 30 days and won’t charge you for a reasonable request. If we refuse, we’ll tell you why. For information inside a workspace’s projects, contact the customer who owns the workspace (see section 1).
If you’re in the EU or UK, you can also contact our representatives under Article 27 of the GDPR and UK GDPR:
- EU representative: [EU representative name and contact details]
- UK representative: [UK representative name and contact details]
11. Children
PagePot is for businesses and isn’t intended for anyone under 18. We don’t knowingly collect personal information from children. If you think a child has given us personal information, contact us and we’ll delete it.
12. Complaints
If you have a concern about how we’ve handled your personal information, please contact us at [email protected]. We’ll respond within 30 days. If you’re not satisfied, you can complain to the Office of the Australian Information Commissioner (1300 363 992). If you’re in the EU or UK, you can also complain to your local data protection authority.
13. Changes to this policy
We may update this policy. The date at the top shows when it last changed. If we make significant changes, we’ll tell you by email or in PagePot before they take effect.
14. Contact us
Brainium Labs Pty Ltd (ABN 44 621 469 298)
[email protected]

