← Neo

Privacy Policy

Effective: September 24, 2026 · Applies to the Neo personal assistant OAuth application (“Neo”, “we”, “us”).

Neo is a personal assistant operated by Mayron for private use. This policy explains what information Neo accesses through Google OAuth, why, and how it is handled.

1. Who this covers

Neo is intended for the account owner (Mayron / [email protected]) and authorized household or work accounts the owner explicitly connects. It is not a public multi-tenant consumer product.

2. Google account data we access

When you authorize Neo in Google, Neo may request only the scopes you approve. Typical scopes include:

Neo does not request permission to delete your Google data. If additional Google scopes are added later, Google’s consent screen will show them and this policy should be updated before those scopes are used in production.

3. How we use the data

Accessed Google data is used only to:

We do not sell personal data. We do not use Google user data for advertising.

4. Where data is stored and processed

OAuth tokens and operational data are stored on the owner’s private Neo systems (for example, neo-home / Neo Core), not on a public shared SaaS tenancy. Limited processing may occur on owner-controlled compute used by Neo (including private language-model and speech services the owner configures).

Google remains the primary store of your Gmail and Calendar content. Neo keeps OAuth credentials and may temporarily cache content needed to fulfill a request.

5. Sharing

Neo does not share your Google account data with unaffiliated third parties for their own purposes. Service providers that the owner configures as part of Neo (for example, hosting, model inference, or speech vendors) may process data only to provide that service under the owner’s direction.

We may disclose information if required by law or to protect the security of the owner’s systems.

6. Retention

OAuth tokens are retained until the owner revokes access or Neo deletes them during re-authorization or decommissioning. Cached request content is kept only as long as needed for the feature, troubleshooting the owner requests, or security logs the owner configures.

7. Your choices

8. Security

Tokens are stored with restricted file permissions on private hosts. Access to Neo administration surfaces is limited to the owner and systems the owner authorizes. No method of transmission or storage is perfectly secure; the owner is responsible for host and network hardening.

9. Children

Neo is not directed to children under 13 and is not intended for their use.

10. Changes

We may update this policy. The effective date above will change when we do. Continued use of Neo after an update means you accept the revised policy.

11. Contact

Questions about this policy: [email protected]

This page is an operational draft for Google OAuth branding. It is not formal legal advice.