Private-test privacy notice

Stage 1A · Updated 28 September 2026

Who operates this test

Design Animal Limited, trading as Byte Digital, operates this private staging application. For support, privacy questions or a deletion request, contact gareth@bytedigital.io.

What this stage handles

The portal uses your verified Google sign-in identity to restrict access to the two nominated testers and keep each tester’s records separate. Advertiser accounts, connection credentials and performance figures used in this stage are fictional. Real Google Ads access is disabled.

The application handles your sign-in identity, a secure session, fictional connection and summary records, and limited technical records needed to protect access and investigate failures. The Google sign-in is for portal identity only.

Why the information is used

The information supports this requested private test: signing you in, keeping your records separate, exercising collection and deletion, and checking that the service behaves safely. It is not used here for marketing audiences, advertising pixels, AI processing or CRM lead scoring.

Where it is processed

The private application and its stored test records use Cloudflare. Google provides portal sign-in. Cloudflare Turnstile checks the browser and request for automated abuse before sign-in; the server validates its short-lived result before creating a login transaction. These providers process information under their own applicable service terms. This notice does not claim that processing occurs only in the UK.

How long it is kept

• Portal identity: kept for the duration of the private test and removed on request or when the test is taken down. Identity records do not expire automatically when a session ends.
• Portal sessions: up to two hours. Sign out to end the current session earlier.
• Fictional connection access: closes after collection, failure or disconnect, with an absolute two-hour limit.
• Saved fictional summaries: available for up to 24 hours, unless deleted earlier.
• Closure and deletion journals: minimal connection-status records may remain for up to 30 days so deleted or closed data cannot be reopened during recovery.
• Backup history: records removed from the active application may remain in provider recovery history for up to seven days. Closure and deletion records must be checked before recovered data is served.

Disconnect, delete and sign out

Disconnect stops new fictional collection. It does not remove a summary that has already been saved. Delete test data removes access to the selected fictional connection and its saved summary in the active application. Sign out ends the current portal session.

You can contact Byte to request deletion of your portal identity or to ask about retained technical records. Some minimal closure information may need to remain during the stated recovery period so a deletion cannot be undone by a restore.

Essential session cookies

The portal uses essential cookies for secure sign-in and its session. This stage does not use advertising cookies or session-replay analytics.

Before any real Google Ads connection

A later stage would need a separate Google Ads consent flow, approved access and a reviewed credential-protection design. Its notice would explain the real account data and processing before that stage is enabled.