1. Scope and service identity

This policy applies to the Opalia service available at airphub.online. Opalia is a private, invitation- and permission-based platform for interactive character content, accounts, character cards, saved conversations, scene state, and creator administration.

“Google user data” means data provided through Google Identity Services and processed by Opalia after a user chooses Google Sign-In. Data created through email/password registration and content created within Opalia are also covered by this policy.

2. Google user data

What we access and retain

• The stable unique identifier for the Google Account (the ID Token sub claim);
• The verified email address and email-verification status;
• The Google Workspace hosted domain (hd), when Google provides it; and
• The signed ID Token needed to complete a single verification. It is sent to the Opalia server to validate its signature, issuer, audience, and expiry.

A Google ID Token may contain other basic profile claims, but Opalia's server currently reads and persistently stores only the identity and email-related fields listed above. The Google ID Token is not placed in persistent browser storage and is not retained as a long-term credential.

What we do not access

Opalia does not request access to Gmail messages, Google Drive, Contacts, Calendar, Photos, payment data, or a Google password, and does not use Google Workspace APIs to obtain files or Workspace content.

Google user data is not used for advertising, retargeting, data brokerage, credit decisions, or training or improving generalized models.

3. Other data we process

• Account and profile data: email address or username, a secure password hash, email verification status, a unique public account ID, sign-in sessions, and the nickname, biography, and avatar a user chooses to provide.
• User content: interactive messages, saved conversations, character cards, persona preferences, scene state, summaries, memories, and creator settings.
• Community interactions: work comments, replies, like relationships, and the resulting notifications. The comment area shows a nickname, unique public account ID, and any avatar the user chooses to set to registered users who can access that work, but does not show the sign-in email address.
• Operations and security data: request time, IP address, browser and operating-system type, device category, browser locale, device time zone, errors, rate-limit records, usage totals, and sparse audit events that do not contain full prompts or model response text. Recent sign-in IP observations are counted to mark a common IP on the account page. The device time zone supplies only an approximate location and is not precise GPS location.
• Browser storage: Opalia stores first-party access and refresh credentials, basic profile metadata, and account-isolation cache markers in local browser storage. The current account avatar and comment-author avatars are loaded temporarily during the signed-in session and are not written as image data to persistent browser storage. The Google ID Token is not written to that persistent storage.

4. How we use data

We process data only as needed to provide, protect, and improve user-facing Opalia features, including to:

• Register, verify, sign in, and restore account sessions;
• Show recent signed-in devices, a common IP, and approximate device-time-zone location on the account security page, and let the user revoke another device's session;
• Save and display the nickname, biography, and avatar a user chooses to set;
• Reliably map the same Google identity to the same Opalia account and prevent duplicate cross-method registration;
• Save and restore interaction progress, build context requested by the user, and generate responses;
• Display work comments and replies, record likes, and send in-account notifications to the relevant comment author;
• Enforce access to roles, servers, invitations, and character cards;
• Prevent abuse, diagnose failures, and protect service capacity and security; and
• Send requested email verification codes and essential service notices.

5. Sharing, transfer, and disclosure

We do not sell Google user data or other personal data, and we do not share it with advertisers or data brokers.

• Google Identity Services: displays the official Google sign-in experience and returns a signed credential to Opalia. Google's own processing is governed by Google's policies.
• Infrastructure and email providers: process data only as necessary to host the service, transmit data, or deliver account verification email.
• Content-processing providers: relevant messages and scene context may be sent to the currently configured content-processing provider to produce interactive responses requested by the user. The stable Google account identifier, Google sign-in token, and verified email address are not included in processing instructions or sent to that provider.
• Legal and safety: we disclose the minimum necessary data only when required by law or genuinely needed to protect users and the service, investigate fraud, or enforce our terms.

If our sharing practices materially change, we will first update this policy and the in-product notice.

6. Data retention and deletion

The Google account identifier and verified email are generally retained while the Opalia account remains active so the user can continue signing in and account conflicts can be prevented. Account content is retained while needed to provide the features requested by the user.

You may delete a work comment or reply posted by your account. It is removed from the active system when no later reply depends on it. When replies depend on it, its text, tag, likes, and notifications are cleared immediately and only a “deleted” structural placeholder remains so other users' replies are not removed.

Current operations targets include 30 days for raw conversation messages, 30 days for revoked or expired sign-in session records and their IP/device observations, 90 days for security audit records, and up to 400 days for aggregate usage and maintenance records; routine backup rotation targets 30 days. Device information for an active sign-in session is retained while that session remains valid. Some data may be kept longer when an account remains in use or when needed for a security incident, dispute, or legal obligation, and data may also be deleted or de-identified sooner.

Once company contact details are finalized, this page will publish the channel for requesting deletion of an Opalia account and its linked Google identity mapping. After identity verification, data no longer needed will be deleted or de-identified from active systems; residual backup copies expire through backup rotation, except for minimal records that must be retained by law or to prevent abuse.

7. Data security

Opalia protects data with HTTPS transport, server-side Google Token verification, least-privilege access controls, account ownership constraints, sign-in rate limits, hashing or secret handling for sensitive credentials, backups, and audit controls. We do not record plaintext passwords or use a Google ID Token as a long-lived Opalia session credential.

No internet service can guarantee absolute security. This page will publish a security-reporting channel after company contact details are finalized.

8. Your choices and rights

• You may choose Google Sign-In or email/password registration; not using Google does not prevent use of another available registration method.
• You may sign out and revoke Opalia's Google sign-in permission from the third-party connections settings of your Google Account.
• You may review the current and other signed-in devices, common IP, and approximate device-time-zone location on the account page, and sign out another device.
• You may change your nickname and biography and upload or replace your avatar from the account page.
• You may delete comments or replies posted by your account from the work comment area.
• After official company contact details are published, you may use that channel to request access, correction, or deletion of personal data associated with your account. We may first need to verify account ownership.
• You may stop using the service. Revoking Google permission does not automatically delete an Opalia account that has already been created; submit a separate deletion request.

9. Changes to this policy

If the way Opalia accesses or uses Google user data changes, we will update this page and the in-product disclosure before implementation and complete renewed Google brand or OAuth verification when applicable. The latest update date appears at the top of this page.