Pre-launch privacy notice

Current scope: this notice describes the early-access site. Final controller details, retention schedules, subprocessors and production data-processing terms will be published before paid customer data is onboarded.

What the early-access service stores

When you sign in or use setup, WorkQuarter may store account identity information supplied by the authentication service, the business and contact details you enter, branding and onboarding preferences, saved automation rules, test results and technical information required to operate and secure the service.

What it does not currently do

The WorkQuarter early-access site does not currently take card payments, activate a paid subscription, connect your mailbox through the setup wizard, or import live customer CRM records merely because you save a launch request.

Why information is used

Information is used to provide requested early-access functionality, save your setup, secure accounts, diagnose problems and prepare your requested onboarding. It is not sold as customer data.

Service providers

Infrastructure providers may process limited account, hosting, authentication, AI-request or technical data to provide the service. Production subprocessors and contractual safeguards will be documented before commercial launch.

Retention and deletion

The setup screen currently includes a control to delete saved setup preferences. Other production retention, export and deletion controls are being designed before launch. Technical records may be retained where reasonably required for security and service operation.

Your data rights

Depending on applicable law, you may have rights to access, correct, delete, restrict or object to processing and to request portability. The final production notice will identify the controller and dedicated privacy contact so these rights can be exercised directly.

Security

Early-access private records require authentication and current preview data is scoped to the signed-in account. Production customer data will not be onboarded until workspace isolation, production database controls, secrets handling, backups and access auditing have been verified.