ClarityOS Privacy Policy

Version 2.0 | Effective September 7, 2026
Operated by GLOBALDEV ONE STUDIO LLC

This Privacy Policy explains how ClarityOS accesses, collects, uses, stores, shares, protects, retains, and deletes information when you use the ClarityOS mobile application and related services. It also explains the controls available to you. ClarityOS is designed to request data and permissions in the context of the feature you choose to use and to avoid collecting information solely for hypothetical or unimplemented functionality.

ClarityOS is provided by GLOBALDEV ONE STUDIO LLC (“ClarityOS,” “we,” “us,” or “our”). This Policy applies to ClarityOS and not to third-party services that operate under their own privacy terms.

1. Scope and Core Privacy Principles

• Data minimization: process only information reasonably necessary for the selected feature, security, support, billing, or legal obligations.
• Purpose limitation: use personal and sensitive data only for disclosed ClarityOS purposes.
• User control: request sensitive permissions and connected-account access in context, and allow revocation where supported.
• Security by design: use technical and organizational safeguards appropriate to the sensitivity of the data.
• Truthful disclosures: the live Policy, in-app disclosures, Google Play Data Safety form, OAuth consent screen, and production behavior describe the same real data flows.
• No sale of personal or sensitive user information by ClarityOS.

2. Information ClarityOS May Process

2.1 Account and authentication information

• Name or profile information you provide.
• Email address and authentication identifiers.
• Account status, device/session identifiers used for security, and subscription entitlement status.
• Authentication events and limited security logs used to prevent unauthorized access or investigate abuse.

If you use Google Sign-In, Google authentication identifies your ClarityOS account. Google Sign-In by itself does not grant ClarityOS access to Gmail. Gmail access is requested separately only when you deliberately connect Gmail to a supported email feature.

2.2 Device health, storage, privacy, and app-audit signals

• Storage capacity, storage usage, and information about removable or temporary items where the operating system allows.
• Device configuration, operating-system version, app version, performance or maintenance signals, and other device-health indicators exposed by Android.
• Installed-application/package inventory and application permission status where technically supported and where the ClarityOS App Audit or privacy feature requires it.
• Permission availability, denial, or limited-access state needed to explain why a feature can or cannot operate.

ClarityOS uses these signals to provide device-health, privacy, security, storage, maintenance, and optimization insights. “Device health” refers to the condition and performance of the device, not a person's medical health.

2.3 Wi-Fi, nearby-device, and local-network information

• Current network identity and connection information where available.
• Gateway, DNS, network-security, and local-network conditions used for Wi-Fi posture analysis.
• Devices visible on the user's local network where Android and network configuration permit discovery.
• Trusted/unknown classifications, scan history, and network changes generated by the user-facing network feature.

Some Android versions may require nearby-device or location-related permissions for specific Wi-Fi or network discovery functions even when ClarityOS is not using the permission to build a location history. ClarityOS will not use precise location for advertising and will not request broader location access when a narrower supported mechanism can provide the feature.

2.4 Scanner, OCR, documents, signatures, and Vault

• Camera input when you open the Scanner.
• Photos, media, documents, or files that you select or capture.
• OCR text and other document-processing output.
• Annotations and signature images you intentionally add.
• Vault items, Vault metadata, and backup/restore information where those features are enabled.

ClarityOS does not intentionally access documents or photos you have not selected or otherwise authorized the application to access. Documents, OCR output, signatures, and Vault content are treated as potentially sensitive user content and are not placed in analytics, crash logs, or general diagnostic logs.

2.5 Threat Shield, breach checks, and user-submitted security content

• URLs, QR-code content, text, messages, or email content that you intentionally submit to a security or scam-analysis feature.
• Email addresses or identifiers that you deliberately submit to a breach/exposure check.
• Result metadata, confidence indicators, provider availability, and history necessary to show the outcome of the selected check.

A third-party security or breach provider may receive the minimum information required to perform a check when the user initiates the feature. Provider unavailability is never replaced with fabricated results.

2.6 Family and contacts-safety information

• Family/household invitations, member identifiers, membership status, and security/privacy states necessary for an enabled family feature.
• Contact information selected by the user, or contact information made available under an approved Android permission, only where a contacts-safety feature genuinely requires it.
• Device/member relationships and alert settings needed for the user's approved family configuration.

ClarityOS is not designed for covert monitoring. Where a narrower system picker or user-selected contact flow can provide the feature, ClarityOS prefers that approach over broad contacts access. Broad contacts access is not requested unless the shipped feature genuinely requires it and the user has received a clear feature-specific disclosure.

2.7 Notifications

If you grant notification permission, ClarityOS may send device-health alerts, security notices, account messages, reminders, family notifications, subscription notices, or other user-facing ClarityOS notifications. Sensitive content is minimized in notification payloads and lock-screen previews.

2.8 Subscription and billing information

When a purchase or subscription is processed through Google Play or another approved app-store billing provider, ClarityOS may receive product identifiers, purchase/transaction references, subscription state, renewal/expiration information, entitlement status, and related billing metadata necessary to grant features and provide support. ClarityOS does not receive or store your complete payment-card number when the store processes the payment.

2.9 Diagnostics, crash, security, and support information

• App version/build, device model, operating-system version, crash or performance diagnostics, and service health.
• Security events such as failed authentication, token revocation, suspicious access, abuse, or integrity failures.
• Information you voluntarily provide in support requests.

Production diagnostics are configured to avoid recording passwords, authentication tokens, OAuth secrets, private API keys, full Gmail message bodies, document/Vault plaintext, signatures, or other sensitive content that is not required for diagnostics.

3. Gmail and Google API Data

ClarityOS includes an optional Gmail connection for supported Email Cleaner / Email Intelligence functionality. Gmail access is not required to use unrelated ClarityOS features.

3.1 OAuth permission and least privilege

When the shipped Gmail feature requires message access and supported mailbox actions, ClarityOS requests the restricted Google OAuth scope:

ClarityOS requests the narrowest Google scope that is genuinely necessary for the production feature and will not request broader Google access merely for possible future functionality.

3.2 Gmail data used

• Sender and recipient information where needed for the requested email view or action.
• Subject, date/time, labels, message/thread identifiers, size, and unsubscribe-related headers.
• Message snippets or body content only when technically necessary for the specific user-facing classification, review, or action you have chosen.
• Mailbox action state necessary to archive, mark read/unread, label, move, trash, or otherwise perform supported actions you authorize.

3.3 User control over Gmail actions

Connecting Gmail does not authorize ClarityOS to make arbitrary mailbox changes. Mailbox changes correspond to the user-facing feature and your selections, confirmation, or clearly configured rule. Disconnecting Gmail or revoking ClarityOS in your Google Account stops continued use of that authorization.

3.4 Storage, sharing, and Google Limited Use

• ClarityOS does not store a general-purpose server-side copy of your Gmail mailbox.
• OAuth tokens, where retained to maintain your authorized connection, are stored only as necessary and protected using secure device storage. Gmail passwords are never requested or stored by ClarityOS.
• Gmail data is not sold, used for advertising or retargeting, provided to data brokers, used for credit or lending decisions, used for surveillance, or used to train general-purpose AI models.
• Gmail content and Google-restricted user data are not sent to Gemini or another general-purpose AI model for training or generalized analysis. If a future Gmail-specific AI feature would require such processing, ClarityOS will update its disclosures, OAuth verification, technical architecture, and obtain any required user consent before introducing that use.
• Human access to Gmail data is prohibited except where you affirmatively request support involving specific content, access is necessary for security/abuse investigation, access is required by law, or another use is expressly permitted by Google's Limited Use requirements.
• Transfers of Google user data are limited to uses permitted by the Google API Services User Data Policy, including providing or improving the user-facing feature with your consent, security purposes, legal compliance, or another expressly permitted circumstance.

ClarityOS's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

4. How We Use Information

• Provide, operate, personalize, and maintain the ClarityOS features you choose to use.
• Authenticate users, maintain sessions, and protect accounts.
• Generate device, storage, privacy, network, security, and maintenance insights from real available signals.
• Process user-selected documents, OCR, PDFs, annotations, signatures, and Vault actions.
• Operate user-authorized Gmail, Outlook/Hotmail, breach-check, family, notification, and other connected features.
• Validate subscriptions and entitlements and prevent billing or feature-access abuse.
• Provide local or cloud-assisted explanations and recommendations where the feature is enabled.
• Diagnose failures, maintain reliability, prevent fraud and abuse, and protect the service.
• Respond to support, privacy, and security requests.
• Comply with applicable law and enforce legitimate service and security requirements.

ClarityOS does not request access to personal or sensitive information solely for future or unimplemented functionality.

5. AI and Cloud Processing

Some ClarityOS features may use local rules, on-device logic, cloud services, or artificial intelligence to explain signals, prioritize recommendations, summarize user-selected information, or assist with supported workflows. ClarityOS does not invent device or security facts that are not grounded in available signals.

• Cloud AI processing is disclosed in context where required and limited to information needed for the selected AI-assisted feature.
• If you decline optional cloud AI, local functions remain available where technically possible.
• Sensitive content is minimized or redacted before cloud processing where feasible.
• Gmail data is subject to the stricter Google-specific limitations in Section 3.
• ClarityOS does not use your content to train a general-purpose ClarityOS foundation model unless a separate future program is introduced with clear disclosure and valid consent.

6. When Information May Be Shared

ClarityOS may disclose limited information to service providers only when needed to operate a feature, protect the service, process billing, or comply with law, including:

• Google/Firebase/Google Cloud services for authentication, hosting, app integrity, backend, storage, messaging, diagnostics, or other configured ClarityOS infrastructure.
• Google Play for app distribution, billing, subscription management, and store-related services.
• Google APIs for Google Sign-In and user-authorized Gmail functionality.
• Microsoft services when you voluntarily connect Outlook/Hotmail or another Microsoft account feature.
• Approved cloud-AI providers for explicitly enabled AI-assisted features, subject to the limitations described in this Policy.
• Approved breach/security providers when you initiate an exposure, URL, QR, message, or other supported security check.
• Infrastructure, monitoring, support, or communications providers that process data on our behalf under appropriate confidentiality and security obligations.

We may also disclose information when required by law, to protect users or the service from fraud or security threats, or as part of a merger, acquisition, financing, reorganization, or sale of assets, subject to applicable law and any additional restrictions that apply to Google user data. When you intentionally export or share a document through the Android share interface or another destination you choose, the receiving service processes the information under its own terms.

7. Permissions, Prominent Disclosure, and Consent

ClarityOS requests permissions in the context of the feature that needs them whenever supported by Android. Depending on the device and enabled features, permissions may relate to camera, photos/media/files, notifications, nearby devices, Wi-Fi/network information, installed-app/usage information, biometrics, contacts, and connected-account authorization.

• Where access, collection, use, or sharing of personal or sensitive user data may not be reasonably expected, ClarityOS presents a clear in-app disclosure before the permission or consent request.
• The disclosure explains what data is accessed, why it is needed, how it is used or shared, and requires an affirmative user action when consent is required.
• Declining an optional permission may disable the related feature but does not grant access to unrelated information.
• Biometric authentication is handled by the operating system or device security hardware where supported; ClarityOS receives only the authentication result, not raw biometric templates.

8. Security

ClarityOS uses technical and organizational safeguards intended to protect information against unauthorized access, alteration, disclosure, loss, misuse, or unlawful processing. These safeguards may include encrypted transport, protected storage, least-privilege access, server-side authorization, secure token handling, integrity controls, rate limits, security logging with redaction, environment separation, vulnerability/secret scanning, credential rotation, and incident-response procedures.

No application, network, or storage system can guarantee absolute security. We work to reduce risk, limit access, detect abuse, and respond appropriately to incidents. Where legally required, affected users and authorities will be notified of qualifying data incidents.

9. Data Retention and Deletion

ClarityOS retains information only for as long as reasonably necessary for the purpose for which it was processed, to maintain the account or subscription, protect the service, resolve support/security issues, satisfy legitimate fraud-prevention needs, or comply with applicable legal, tax, accounting, or store obligations.

• User account data is retained while the account is active and then deleted or de-identified after a valid deletion request, subject to limited lawful retention described below.
• Temporary processing artifacts, caches, and failed uploads are removed when no longer needed for the requested feature or troubleshooting.
• Gmail data is not retained as a general-purpose mailbox copy. Any temporary/cached Gmail data is minimized and removed when no longer necessary for the user-facing feature, and authorization stops after disconnect/revocation.
• Security and diagnostic logs may be retained for a limited period appropriate to incident detection, abuse prevention, troubleshooting, and legal obligations; they exclude unnecessary sensitive content.
• Billing and transaction records may be retained for the period required to support subscriptions, resolve disputes, or satisfy accounting, tax, or legal obligations.
• Backups may not be erased instantaneously from every backup generation, but deleted data is isolated from ordinary use and expires under the applicable backup lifecycle unless retention is legally required.

10. Account Deletion and External Data-Deletion Requests

ClarityOS users who can create an account have a readily discoverable way to initiate account deletion from within ClarityOS and an external web resource available without requiring installation of the app.

• In-app path: Profile > Delete Account.
• External resource: https://clarityos.globaldevone.com/account-deletion
• Privacy/support email: clarityos@globaldevone.com

Account deletion is different from signing out, disconnecting Gmail or another provider, uninstalling ClarityOS, or canceling a Google Play subscription.

When an account is deleted, associated ClarityOS user data is also deleted or de-identified unless specific information must be retained for security, fraud prevention, billing disputes, tax/accounting, legal compliance, or another lawful documented purpose. Any retained information is limited to what is necessary, protected from ordinary product use, and retained only for the applicable purpose and period.

We may take reasonable steps, including re-authentication or account-control verification, to protect users from fraudulent deletion requests. Those steps do not create an unnecessary obstacle to exercising the deletion right. If third-party service providers hold user data on our behalf, we take reasonable steps to instruct them to delete or de-identify the data when required.

11. Your Privacy Rights and Choices

Depending on your jurisdiction, you may have rights to request access to personal information, correction, deletion, a copy or portability of certain data, restriction or objection to certain processing, withdrawal of consent, or an appeal/complaint to an applicable regulator. These rights are subject to legal exceptions and verification of the request.

You can also manage device permissions through Android settings, revoke Google access in your Google Account, disconnect supported connected services, manage notifications, and control supported privacy settings within ClarityOS.

12. International Processing

ClarityOS and its service providers may process information in countries other than the country where you live. Where applicable law requires safeguards for international transfers, GLOBALDEV ONE STUDIO LLC will use appropriate contractual, technical, or organizational measures for the relevant processing.

13. Children and Family Features

ClarityOS is not directed to children under 13. Where local law requires a higher age for a person to consent independently to digital services or data processing, a parent or legal guardian must provide any consent required by law. Family features do not authorize covert surveillance or access to another person's accounts or devices without appropriate authorization.

If we learn that ClarityOS has collected personal information from a child in a manner not permitted by law, we will take reasonable steps to delete or appropriately handle that information.

14. Changes to This Privacy Policy

We may update this Policy when ClarityOS functionality, providers, permissions, data practices, security controls, or legal/platform requirements change. If a change materially affects how personal, sensitive, or Google user data is accessed or used, the Policy and related disclosures will be updated before the new use begins, and additional notice or consent will be obtained where required.

15. Contact

Google API Limited Use Disclosure

ClarityOS's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.