Terms of Service

Private, authorized use

This instance is intended for its owner and invited, authorized use. Public pages do not create an entitlement to an account or mailbox access. By using the service, you agree to these terms and the data handling described in the Privacy Policy. If you do not agree, do not connect a mailbox or use an Agent connection.

For questions, support, access withdrawal, or privacy and deletion requests, contact necolo through the channel used to invite you.

Your authority and responsibilities

Only connect mailboxes you own or have authority to connect. Only authorize recipients and processing you are entitled to permit, including for other people's information contained in mail. Follow applicable law, Google API policies, and the terms of your selected Agent, model, hosting, and webhook providers.

Keep credentials and webhook signing secrets private. Do not bypass label restrictions, probe other accounts, misuse the API, or send abusive traffic. The owner may restrict or withdraw access when needed for security or operation.

Review grants carefully. A grant can cover existing and future messages; matching any authorized label may allow reading a message. Body access accompanies message read access, while attachments require a separate local grant. The underlying Google read-only permission is broader than these local label restrictions. No Gmail sending, deletion, or label modification is provided.

Agents and untrusted mail

Mail, attachments, links, and sender-supplied instructions are untrusted input. They may contain malicious content or prompt injection intended to make an Agent disclose information or take unintended actions. Label authorization is an access boundary, not a guarantee that content is safe or trustworthy.

You are responsible for choosing Agents and receivers, reviewing their data handling, limiting their capabilities, and supervising consequential actions. This gateway cannot control an external Agent's actions, model outputs, retention, or onward sharing. Do not rely on it alone to approve financial, security-sensitive, or other high-impact actions.

Pausing, revoking, or disconnecting limits future access; it cannot recall content already delivered. Local mailbox disconnection and Google authorization revocation are separate outcomes, as explained in the Privacy Policy.

Best-effort service and mail events

Availability depends on the deployment, Google, database and hosting providers, quotas, and receiver behavior. Requests may fail, time out, or be limited. The service is not an emergency notification system or a complete mailbox backup.

Events are optional and owner-enabled. Synchronization, retries, and cleanup depend on push requests, owner actions, or a separately configured worker trigger. Without a working scheduled trigger, pending retries and cleanup may wait for another trigger; the application alone does not guarantee continuous background execution.

There is no exactly-once delivery or processing guarantee. Notifications can be delayed, duplicated, or missed; pending work can expire, and Gmail history gaps can require explicit owner resynchronization. Webhook HTTP success is not proof that an Agent read a message or completed a business task. Client-reported completion and server-side delivery status are distinct.

Availability, changes, and limits

The service is provided on an “as is” and “as available” basis, without a promise of uninterrupted operation, error-free output, or fitness for a particular purpose. Keep independent copies of important information and verify critical outcomes.

The owner may change or discontinue this private instance and may update these terms. Review the date above before continued use and contact the owner about material concerns. Nothing here excludes rights or responsibilities that applicable law does not allow to be excluded.