PRIVACY

Privacy Policy

Last updated: 9 November 2026

This policy describes how the Finitor operator platform (finitor.andrewstarkey.net) handles information for this controlled pilot. It is written to match the software’s actual behaviour. It is not legal advice and does not claim certification under a specific privacy regime.

1. Who this applies to

This policy covers people who open the Finitor operator console or related suite surfaces (for example Studio or Lovanta) on this pilot host, including people who sign in with Google.

2. Information we collect

Google sign-in (Sign in with Google / OpenID Connect)

When Google sign-in is used, Finitor receives a signed identity token from Google after you complete Google’s consent and authentication flow. From that token Finitor may read and retain:

• Google subject identifier (sub)
• Email address and email verification flag, when provided
• Issuer (iss)
• Multi-factor / authentication-method evidence when present (for example amr containing mfa)
• Authentication time (auth_time), when present
• Token expiry used to bound the Finitor session

The authorization request may include scopes openid, email, and profile. Finitor does not use Google account data to show ads, build advertising profiles, or sell personal information.

Session and security data

• A short-lived HttpOnly session cookie (platform_session) whose value is stored only as a hash server-side
• Temporary OpenID login state (PKCE verifier, nonce, expiry) during sign-in
• Audit events for operator actions in the workspace

Workspace content

Operators and tenant members may create or import website content, membership records, entitlements, and related operational data for customers they manage. That content is processed to provide the service the operator requested.

3. How we use the information

• Authenticate you and maintain a signed-in operator session
• Authorise access to tenants, sites, Studio, Lovanta, and related APIs
• Enforce platform-administrator and tenant MFA policies using verified token claims where configured
• Operate publishing, audit, and support workflows for this pilot
• Protect the service against abuse and unauthorised access

4. Storage

Application data for this pilot is stored in a PostgreSQL database on the host that runs Finitor, with sessions and login-state records as described above. Session lifetime is bounded (on the order of one hour or earlier token expiry). Hosting and backups are managed by the pilot operator.

5. Sharing

Finitor shares Google identity data with Google only as required to complete Sign in with Google (you authenticate at Google; Google returns a signed token to Finitor). Finitor does not sell personal information. Service providers that host or back up this pilot environment may process data solely to operate the pilot, under the pilot operator’s arrangements. Finitor may disclose information if required by law.

6. Retention

Login sessions expire and are rejected after expiry. Temporary OpenID state is short-lived. Workspace content, memberships, and audit records persist for the life of the pilot (or until an authorised operator deletes or suspends the relevant records), subject to backup retention set by the pilot operator. Exact multi-year retention schedules for this pilot are not separately published in the application.

7. Your choices

• Sign out of the Finitor console to clear the browser session cookie
• Review or revoke Finitor’s access to your Google Account in Google Account permissions
• Ask the pilot operator to deactivate your Finitor membership where applicable

8. Children

The operator console is not directed at children. Do not use Finitor if you are not authorised to operate this pilot workspace.

9. Contact

For privacy questions about this Finitor pilot, contact the pilot operator. A dedicated public privacy email for Finitor Labs will be published here when designated.

Related pages: About Finitor · Terms of Service