Privacy Policy

This policy explains how Screenpay, the operator of Screenpay, collects, holds, uses and discloses personal information. This policy is designed around the Australian Privacy Principles. Whether a particular statutory obligation applies depends on the operator and the circumstances; the contact route below remains available in either case.

Who controls talent records

The production organisation using a workspace ordinarily decides why talent information is collected and how it is used. It enters that information into Screenpay and directs us to process it. We also collect limited information directly when a person uses a Screenpay signing link, contacts support, creates an account or uses the product.

Where data is handled

Authentication, hosting, database, object-storage, billing, email, analytics, support and optional AI providers may handle limited information in Australia or overseas. Provider routing can involve Australia and overseas locations that vary with the configured services. Ask hello@screenpay.com.au for the current likely-country information relevant to the production deployment. Supplier routing and subprocessors can change. A changed production arrangement must be reviewed and this policy and relevant collection notices updated before relying on the new arrangement.

We do not hold payroll funds

Screenpay produces files; the workspace customer pays talent from its own bank. We do not hold, receive or move payroll funds. Stripe handles service-payment details; Screenpay does not receive the complete card number. Talent bank details are held to prepare customer-authorised bank hand-off files and records.

We do not store tax file numbers

We record only whether a TFN is held, never the number itself. There is no TFN-number field in Screenpay.

What we collect and how

• ·Account, workspace and production settings, including company and payer-bank details.
• ·Where an express workspace acceptance was captured: authenticated account and organisation identifiers, account name and email snapshots, organisation name, exact Terms and Privacy versions and source hash, acceptance wording and time, a keyed pseudonymous network indicator and coarse browser family.
• ·Talent records entered by a workspace customer: identity and contact details, engagement and tax-status selections, ABN, payment and super-fund details, pay records and consent terms.
• ·Signing evidence supplied directly by talent: typed name, optional drawn signature, time, a keyed pseudonymous network indicator and a coarse browser family.
• ·Service, security and support data, including product events, request logs, messages and billing status.

We receive information directly from account holders and signers, and indirectly from production organisations that create talent records. We do not sell personal information or use workspace payroll records for behavioural advertising. Screenpay does not build or train its own model from workspace records. Optional AI features disclose the limited prompt content described below to the configured provider; that provider’s retention and model-use terms must be verified for the production arrangement before live use.

Why we use and disclose it

We handle personal information to provide and secure workspaces; calculate and display selected payment rules; prepare customer-authorised records and exports; collect service charges; send requested signing and account messages; provide support; investigate misuse; meet legal obligations; and improve reliability. If required identity, engagement, payment or signing information is not supplied, the relevant person may not be included in a bank hand-off file or complete a consent record.

How we protect it

• ·Encryption — TLS protects connections. The current release supports authenticated field-level encryption for payer/payee bank-account fields and retained export artifacts; the operator must complete and verify the documented production migration before live financial data is accepted.
• ·Workspace isolation — application reads and mutations are scoped to the active organisation, with administrator checks for higher-impact operations.
• ·Private media — the current release serves uploaded headshots, job covers and logos through an authenticated workspace check. The operator must complete the documented private-storage migration and cross-workspace acceptance test before live media is accepted.
• ·Server-side secrets — credentials and encryption keys are kept out of browser-delivered code.
• ·Audit evidence — material record changes, approvals and exports are attributed and logged.

Service providers and optional AI

Depending on the production deployment and enabled features, service providers can include Clerk (authentication and organisations), Neon (database), Vercel (application hosting), Cloudflare R2 (private media), Stripe (billing), PostHog (product analytics), Resend (transactional email), and Anthropic (optional AI features). An AI payment-batch review sends the figures and labels shown in that review. Callie receives a limited workspace summary that can include the organisation name, talent names, recent batch totals and calculated flags. Bank account numbers, BSBs, TFN-status flags and contact details are excluded from those AI prompts. AI features are optional and their outputs require human review.

Keeping and deleting

We keep information while a workspace is active and for legitimate security, billing, dispute and legal-record purposes. The period depends on the record, why it is held, the legal party responsible for it and any legal hold; there is no single retention period for every workspace record. Draft operational records can be placed in Trash. Approved or exported financial evidence, including a recorded bank confirmation, is protected against ordinary in-app purge so a customer cannot silently destroy its sealed trail. To close a workspace or request deletion, contact us. We will explain what can be deleted or de-identified and what remains required or reasonably needed. Workspace administrators can export the records exposed by the self-service export; a privacy access request may cover other personal information we hold. Customers remain responsible for keeping their own authoritative records.

Access, correction and complaints

You may ask for access to or correction of personal information we hold about you. A talent person may also contact the production organisation that created the workspace record. Send requests or privacy complaints using the contact details below and describe the record or concern. We may verify identity before releasing or changing information. We will acknowledge the request, investigate it, explain our response in writing and tell you about available escalation options. If you are not satisfied, you may complain to the Office of the Australian Information Commissioner at oaic.gov.au.

Data incidents

Customers must promptly report suspected loss, disclosure or unauthorised access in their workspace so it can be contained and assessed. Where the Notifiable Data Breaches scheme applies after assessment, affected individuals and the OAIC must be notified as required.

Contact

Privacy contact for Screenpay: hello@screenpay.com.au. Ask us if you need this policy in another accessible form.