Privacy Policy
How we handle your data.
Version: 1.3
Effective: 30 October 2026
Jurisdiction: Western Australia, Australia
Framework: Australian Privacy Principles
01 Who We Are

SKOPIA is operated by Gavin Roberts trading as SKOPIA APP, located in Success, WA 6164, Australia. ABN registered in Australia.

This Privacy Policy applies to the SKOPIA website at skopia.com.au and all SKOPIA product tiers: SKOPIA Lens, SKOPIA Lens Pro, SKOPIA Command, SKOPIA Build, and SKOPIA Track.

By using any SKOPIA product, you agree to this policy. If you don't agree, don't use the service.

We handle personal information in line with the Australian Privacy Principles (APPs), and this policy has been written to meet them.

Beta features

SKOPIA Lens and SKOPIA Lens Pro are publicly available. SKOPIA Command, SKOPIA Build and SKOPIA Track are not yet publicly released; invited testers may use them before release. Where a beta feature sends data to our server, that is explained in the app at the point you use it. SKOPIA Command (Project Console) is described in section 6. The data flows of SKOPIA Build and SKOPIA Track will be added to this policy before those tiers are publicly released.

SKOPIA is a professional project planning and scheduling tool intended for business use and is not intended for use by children under 13.

02 What Data We Collect
Account and contact information

An account is required to use every SKOPIA plan, including the free Lens plan. When you create one, we collect your email address and password (the password is handled by Supabase, our authentication provider, and stored in hashed form), plus any additional information you voluntarily provide. We do not collect your physical address unless you provide it.

Plan and usage records

Against your account we keep your plan and subscription status, a count of schedule uploads this month (used for the free plan's monthly limit), and, if you use Helios, a usage record for each Helios request: the type of request, the AI model used, the number of tokens processed, the cost, and the date. These records do not contain your schedule content. If you buy Helios credit, we also keep your credit balance.

Payment information

Payments are processed by Stripe. We do not receive or store your full card number, CVV, or bank account details. Stripe provides us with a payment token and transaction reference only. See section 7 for more on Stripe's role.

Usage and technical data

When you use SKOPIA, our infrastructure providers automatically log standard technical data: IP address, browser type and version, operating system, pages visited, time and date of access, and general usage patterns. This is used to operate the service, diagnose issues, and improve the product.

Schedule files

SKOPIA Lens and SKOPIA Lens Pro — on every tier, free or paid — process schedule files (XER, MPP, XML) by uploading them to our server, where the file is parsed and then deleted immediately. It is not retained or stored. Some Lens Pro features also send data derived from your schedule to our server when you use them. See section 5 for the full detail.

SKOPIA Project Console works differently: after the initial upload-and-parse step, your schedules are stored in your own browser, not on our servers. Some Console features send schedule data to our server when you use them, and nothing is kept afterward. See section 6 for the full list.

Communications

If you contact us by email or through any support channel, we retain those communications to respond to your enquiry and improve our service. If you send us a schedule file to help us investigate a problem, we use it only for that purpose and delete it once the issue is resolved.

03 How We Collect It

We collect personal information in the following ways:

  • Directly from you — when you sign up for an account, subscribe to a paid tier, or contact us.
  • Automatically — through server logs and, once configured, analytics tools when you use the website or application.
  • Through third-party processors — Stripe provides payment confirmation data; Supabase handles authentication events.

We do not purchase or acquire personal information from data brokers or third-party marketing lists.

We only collect personal information that is reasonably necessary for our functions and activities, consistent with APP 3.

04 How We Use Your Data

We use your personal information only for the following purposes:

  • To provide and operate the SKOPIA service.
  • To process your subscription and manage your account.
  • To communicate with you about your account, service updates, and support requests.
  • To send transactional emails (e.g. payment receipts, upgrade confirmations). See section 9.
  • To send optional marketing communications, with your consent. See section 9.
  • To diagnose technical issues and improve the product.
  • To comply with legal obligations.

We do not use your personal information for advertising profiling, and we do not sell it to any third party.

05 File Processing — SKOPIA Lens & Lens Pro
Your schedule file is uploaded for processing, then deleted immediately. SKOPIA Lens and SKOPIA Lens Pro — on every tier, free or paid — need to parse XER, MPP, and XML schedule files using tooling that only runs server-side. Your file is uploaded to our server for a single processing pass and deleted from disk as soon as parsing completes, within the same request. It is not stored or retained.

When you upload a schedule file to SKOPIA Lens or Lens Pro, it is sent to our backend (hosted on Render), written briefly to a temporary file, and parsed using MPXJ — a parsing library that requires a Java runtime and cannot run inside a web browser. This is why processing happens on our server rather than on your device, regardless of which SKOPIA tier you're on. MPXJ is an open-source (LGPL-licensed) library rather than a proprietary vendor parser, which keeps our parsing logic transparent and auditable.

The temporary file is deleted immediately after parsing, in the same request that created it. We do not keep a copy, and nothing from the file itself is written to a database as part of this step. Although the file is deleted immediately after processing, the upload step constitutes "collection" of personal information under Australian Privacy Principle 3 (APP 3) for the duration of processing, even though nothing is retained afterward.

Your health report is shown in your browser from the parsed result. We do not store reports on our servers. When you export a PDF report (on any plan), the report data you are looking at, including activity names, is sent to our server, which builds the PDF in memory and returns it to you. Nothing is written to disk or kept. The exported file is saved to your own device.

Lens Pro features that use our server

The following SKOPIA Lens Pro features send data to our server, and only when you choose to use them:

  • Recalculate (CPM) and Critical Path Test — send a derived version of the schedule you have open (activity IDs, names, WBS structure, dates, durations, calendars and relationships, but not the original file) for a one-off calculation. The result is returned to your browser and is not stored.
  • Schedule Converter (MPP files) — uploads the MPP file to be converted, using the same upload-and-delete step described above.
  • Helios AI — sends derived schedule data to Anthropic, as described in section 7.

Each of these is a temporary collection of information under APP 3 and APP 11, even though nothing from your schedule is kept afterward.

Because the file is deleted immediately after processing and never written to a database, we have no ongoing ability to access, read, or recover it once your request completes.

06 Project Console & Data Storage

When you first bring a schedule file into SKOPIA Project Console, it goes through the same upload-and-parse step described for SKOPIA Lens in section 5: the file is sent to our server, parsed, and deleted immediately. From then on, your Console library lives in your own browser, in a client-side database (wa-sqlite in the browser's Origin Private File System). Your library includes your schedules, your edits and notes, and a copy of each original schedule file, which Console keeps so it can export your schedule later. None of it is stored on our servers.

When Console sends data to our server

SKOPIA never reads or uploads your library in the background. Data leaves your device only when you use a feature that needs our server. Those features are:

  • Importing a schedule: the file is uploaded, parsed and deleted, as in section 5.
  • Recalculate (server) and the Critical Path Test: send a derived version of the schedule (activity IDs, names, WBS structure, dates, durations, float, calendars and relationships, but not the original file) for a one-off calculation.
  • Health Check: when you open the Health Check for a schedule you have changed since import, the same derived data is sent so the checks and insights can be recalculated.
  • Resource histogram: sends the derived schedule and resource data needed to draw it.
  • Activity codes and user-defined fields: the first time you show these for an XER schedule, the original file stored in your library is sent once more, parsed for its codes and fields, and deleted, as in section 5.
  • PDF export and Helios: as described in sections 5 and 7.

In every case the result is returned to your browser and nothing from your schedule is written to a database or kept on our servers. These features require you to be signed in. Each is a temporary collection of information under APP 3 and APP 11, even though nothing is stored afterward. Exporting your schedule as XER or Microsoft Project XML happens entirely in your browser.

Who made each change (editor identity)

Console records who made each edit and note. By default it records a display name (your initials, or a name you choose) and a random account ID. It records your email address only if you tick "Include my email". These details stay in your library, and travel with any file you export, publish or send from it (see below). Tick "Strip editor names" to remove names and email addresses from every one of those files. The random ID is kept so mark-ups can still be matched to the person who made them.

Files you share

Export database, Publish my library, Send my mark-ups and the change-log download each create a file on your device. You decide where it goes. Those files never pass through our servers, and once they leave your device they are outside our control.

Deleting Console data

Because your library is on your device, we cannot see it or delete it, and closing your SKOPIA account does not remove it. To delete it, clear this site's data in your browser settings (or delete the browser profile). Files you exported or shared must be deleted wherever you saved or sent them.

SKOPIA Build and SKOPIA Track are planned future tiers that may add further server-side project storage. That capability is not yet built. When it is, this Privacy Policy will be updated to describe exactly what is stored, where it is hosted, how long it is retained, and how you can delete it — and we will notify active subscribers of any material change before it takes effect.

Note: None of the Console features listed above store your schedule on our servers. No project or schedule data is stored server-side by SKOPIA today.
07 Third-Party Processors

SKOPIA uses the following third-party services to operate. Each processes personal or technical data on our behalf.

Provider Role What they process Privacy Policy
Vercel Frontend hosting IP address, request logs, static asset delivery vercel.com
Render Backend hosting IP address, request logs, API data render.com
Supabase Database + authentication Account credentials, session tokens, plan and subscription status, monthly upload count, Helios usage records and Helios credit balance supabase.com
Stripe Payment processing Payment card data (processed by Stripe directly), billing details, subscription status, Helios credit pack purchases, payment receipt emails stripe.com/au
Anthropic AI inference (Helios feature, Lens Pro and above) Derived schedule metrics and content — check results, grades, float values, activity counts, relationship counts, bottleneck scores, forecast dates, and the names/IDs of individual activities (and, where present, resources). Raw schedule files and file names are not sent. Because activity and resource names come directly from your schedule, they can in some cases carry identifying details — for example, a client, site, or contract name, or a person's name used as a resource. Data is used solely to generate the AI-written insights returned to you and is not retained by Anthropic for training purposes under their API usage policy. Where such details constitute personal information, they are handled in accordance with APP 3 and APP 6, and their transmission to Anthropic is an overseas disclosure under APP 8 — see below. anthropic.com
Google Analytics Usage analytics Page views, session data, device info, anonymised IP. Configured with IP anonymisation. Not yet active — will be enabled in a future release. google.com

We do not share your personal information with any third party beyond those listed here, except as required by law.

Stripe — Payment Data

All payment card data is entered directly into Stripe's secure payment form and transmitted to Stripe's servers. We receive only a payment token and a transaction confirmation. We never see or store your full card number or CVV. Stripe is PCI-DSS Level 1 certified.

Google Analytics — Opt-Out

Once Google Analytics is active on skopia.com.au, you can opt out of usage tracking by installing the Google Analytics Opt-out Browser Add-on, or by declining analytics cookies when prompted via the cookie consent mechanism on the site.

Anthropic — Data Location, Contract Basis & Personal Information

Anthropic processes data submitted to the Helios feature in the United States. Where that data includes personal information, this is an overseas disclosure under Australian Privacy Principle 8 (APP 8).

SKOPIA currently uses Anthropic's standard self-serve API under Anthropic's published commercial terms and API usage policy. We do not have a separately negotiated Data Processing Agreement or enterprise agreement with Anthropic beyond those standard terms, and we do not use Anthropic via AWS Bedrock, Google Vertex AI, or Azure. Anthropic's stated commitment not to use API data for model training is a policy commitment under its standard terms, not an independently verified bespoke contractual guarantee.

Derived schedule data sent to Anthropic (activity and resource names, IDs, float values, and related metrics) may contain personal information — for example, where a resource name is a person's name, or an activity name references a client, site, or contract. Where this occurs, the transmission is a collection and disclosure of personal information under the APPs, handled in accordance with APP 3, APP 6, and APP 8.

08 Cookies & Browser Storage
What we use now

SKOPIA does not currently set any cookies for analytics or marketing. Instead it uses your browser's own storage, only for things that are strictly necessary for the service to work:

  • Sign-in session: Supabase, our authentication provider, keeps your session in your browser's local storage so you stay logged in.
  • Your Project Console library: stored in the browser's Origin Private File System (see section 6). SKOPIA asks the browser to treat it as persistent, so it isn't cleared when disk space runs low. Whether to agree is the browser's decision.
  • Settings: small items in local storage, such as your Console editor name, the "Strip editor names" choice, and display preferences.

None of this is used for marketing or tracking, and none of it is sent to us unless you use a feature that needs it.

What we will add in future

We intend to add analytics cookies (Google Analytics) and may in future add optional marketing cookies. Before any non-essential cookies are set, you will be shown a cookie consent banner and given a clear choice to accept or decline. Non-essential cookies will not be set without your explicit consent.

Managing cookies

You can configure your browser to refuse cookies or to alert you when cookies are being set. Blocking site storage will prevent you from staying logged in and will stop Project Console from keeping your library. Clearing this site's data deletes your Project Console library. Disabling analytics and marketing cookies will not affect your use of the service.

For instructions on managing cookies in your browser, refer to your browser's help documentation.

09 Email Communications
Transactional emails

We will send you transactional emails related to your account — for example, welcome on signup, payment confirmation, subscription change, and error notifications. These are necessary to deliver the service and cannot be opted out of while you hold an active account.

Marketing emails

We may send you optional marketing communications about SKOPIA product updates, new features, and relevant content. We will only do this with your consent, which you can provide at signup or at any later point.

You can withdraw consent and unsubscribe at any time using the unsubscribe link in any marketing email, or by contacting us at contact@skopia.com.au. Unsubscribing from marketing emails does not affect transactional communications.

Email delivery provider

Account emails (sign-up confirmation and password reset) are sent through Supabase. Payment receipts are sent by Stripe. Your email address is shared with these providers only to deliver those messages. We do not send marketing emails today. If we start, we will ask for your consent first and name the provider in this policy.

10 Disclosure to Third Parties

We do not sell, trade, or rent your personal information. We only disclose it in the following circumstances:

  • To our service providers — as listed in section 7, to the extent necessary to operate the service.
  • When required by law — if we are compelled to do so by a court order, regulatory authority, or law enforcement agency under applicable Australian law.
  • To protect our rights or the safety of others — where we believe disclosure is necessary to prevent fraud, enforce our terms, or protect the safety of any person.
  • In a business transfer — if SKOPIA is sold, merged, or its assets are acquired, personal information held by us may form part of that transfer. We will notify you before your information is transferred and becomes subject to a different privacy policy.

In all cases, we limit disclosure to what is strictly necessary for the relevant purpose.

11 International Data Transfers

SKOPIA's infrastructure providers (Vercel, Render, Supabase, Stripe) operate data centres in multiple regions, which may include the United States and other countries outside Australia. Your data may be stored or processed in those countries as part of our normal operations.

If you use Helios, derived schedule data is sent to Anthropic, which processes it in the United States (see section 7).

Under the Australian Privacy Principles (APP 8), we take reasonable steps to ensure that overseas recipients of personal information handle it in a manner consistent with the APPs. We achieve this by using established cloud providers with published data processing agreements and applicable security certifications.

By using SKOPIA, you acknowledge that your personal information may be transferred to and processed in countries outside Australia.

12 Data Retention

We retain personal information only for as long as necessary for the purpose for which it was collected, or as required by law.

  • Schedule files processed by Lens / Lens Pro — not retained. Uploaded for a single server-side processing pass, then deleted immediately. See section 5.
  • Project Console data — stored in your browser and not held on our servers. It stays until you clear it, and closing your account does not remove it. Data sent to our server by a Console feature is not kept. See section 6.
  • PDF export and Lens Pro server features (Recalculate, Critical Path Test, Converter) — not retained. See section 5.
  • Plan, upload count and Helios usage records — retained for the duration of your account. Deleted within 30 days of account closure, except where needed for billing or financial records.
  • Helios credit balance — retained while your account is open.
  • Server request logs — kept by Vercel and Render under their own retention settings, for operating and securing the service.
  • Account information — retained for the duration of your account. On deletion, personal information is removed within 30 days, except where we are required to retain it for legal or financial record-keeping purposes.
  • Payment records — retained as required by Australian tax and financial reporting obligations (generally 7 years).
  • Support communications — retained for a reasonable period to support ongoing service improvement and to resolve any disputes.
  • Schedule files sent to us for support — deleted once the issue is resolved.
13 Your Rights

Consistent with the Australian Privacy Principles, you have the following rights:

Access

You can request a copy of the personal information we hold about you. We will respond within a reasonable time (typically within 30 days). We may ask you to verify your identity before releasing information.

Correction

If you believe personal information we hold about you is inaccurate, out of date, incomplete, or misleading, you can ask us to correct it. We will take reasonable steps to do so promptly.

Deletion

You can request deletion of your account and associated personal information at any time. We will action this within 30 days, subject to any legal retention obligations (e.g. tax records). Deletion of your account will terminate access to all paid features. This includes your plan, upload and Helios usage records. Project Console data is stored on your own device, not on our servers, so we cannot delete it for you. To remove it, clear this site's data in your browser (see section 6).

Complaints

If you believe we have handled your personal information in a way that breaches this policy or the Australian Privacy Principles, please contact us first so we can attempt to resolve the issue. If you remain unsatisfied, you can contact the Office of the Australian Information Commissioner (OAIC):

  • Website: www.oaic.gov.au
  • Phone: 1300 363 992
  • Mail: GPO Box 5288, Sydney NSW 2001

To exercise any of these rights, contact us at contact@skopia.com.au.

14 Data Security

We take reasonable steps to protect personal information from unauthorised access, loss, misuse, disclosure, or alteration. These measures include:

  • HTTPS encryption for all data in transit.
  • Authentication handled by Supabase with industry-standard session management.
  • Payment processing via Stripe, which is PCI-DSS Level 1 certified.
  • Access to production systems restricted to authorised personnel only.

No method of electronic transmission or storage is 100% secure. While we do our best to protect your information, we cannot guarantee absolute security. If you become aware of a security issue affecting your account, please contact us immediately at contact@skopia.com.au.

In the event of a data breach that is likely to cause serious harm, we will notify affected individuals and the OAIC, following the process of the Notifiable Data Breaches (NDB) scheme.

15 Changes to This Policy

We may update this Privacy Policy from time to time to reflect changes in our practices, product capabilities, or legal obligations. The current version will always be available at skopia.com.au/privacy.

A material change is one that adds a new purpose for using your information, a new recipient or processor, a new type of information we collect, or a new way your data leaves your device (for example, server-side storage of schedules). For a material change we will email active account holders at least 30 days before it takes effect. In that time you can export your data and close your account if you don't agree. Continued use of SKOPIA after the change takes effect constitutes acceptance of the updated policy.

Non-material changes, such as corrections, clarifications, or updates that describe what we already do more accurately, may be posted without email notice.

The effective date at the top of this page reflects when the current version came into force.

16 Contact Us

For any privacy questions, access requests, corrections, deletion requests, or complaints, contact us using the details below. We will respond within a reasonable timeframe.

Entity Gavin Roberts trading as SKOPIA APP Location Success, WA 6164, Australia Email contact@skopia.com.au Website skopia.com.au Governing law Laws of Western Australia and the Commonwealth of Australia