Privacy policy

1. Scope and development status

This policy applies to the Navy Pigeon website and development application. The service is currently intended only for people expressly invited by the project owner to participate in development testing.

If you were not invited, do not create an account, connect a mailbox, import contacts, or otherwise provide personal data. If you already did so, stop using the service and contact the project owner through the channel by which you learned about Navy Pigeon.

2. Information we may process

• Account information, including your email address, account name, encrypted password credentials, verification records, and workspace membership.
• Content you add to the service, such as projects, contact details, campaign information, connected mailbox details, messages, and attachments.
• Connection and authorization data needed to integrate with providers such as Google or Microsoft. Mailbox credentials and tokens are protected and are not intended to be displayed publicly.
• Technical and security information, such as request times, error details, rate-limit records, browser type, approximate location, and service logs.
• Aggregated website usage information collected through Vercel Web Analytics, such as page views, referrers, device type, and general geographic region.

3. How information is used

Information is used only as reasonably necessary to:

• provide, test, secure, troubleshoot, and improve Navy Pigeon;
• authenticate users and protect accounts and workspaces;
• operate mailbox connections and requested email features;
• detect abuse, investigate errors, and maintain service reliability; and
• comply with applicable legal obligations.

4. Service providers and connected services

Navy Pigeon relies on infrastructure and service providers for hosting, databases, security, encryption, email delivery, and analytics. Current integrations may include Vercel, Amazon Web Services, Google, and Microsoft. These providers process information under their own terms and privacy notices when you use or connect their services.

Information is not sold. It may be disclosed when required by law, needed to protect the service or another person, or involved in a future transfer of the project, subject to applicable safeguards.

5. Retention and deletion

Development data is kept only while reasonably needed for testing, security, legal compliance, and service operation. Some short-lived records, such as verification codes and authorization state, expire automatically. Backups and security logs may persist for a limited period after primary data is removed.

Because this is a restricted development service, invited testers should request account or data deletion directly from the project owner using their existing communication channel.

6. Security

Reasonable technical and organizational safeguards are used, including access controls, encrypted connections, hashed passwords and verification codes, and encryption for sensitive mailbox credentials. No system is completely secure, and development software may contain defects. Do not add production, confidential, or sensitive data unless the project owner has specifically authorized the test.

7. Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, restrict, or export personal data, or to object to certain processing. You may also withdraw consent where processing relies on consent. These rights may be subject to legal limitations.

8. Children

Navy Pigeon is not intended for children or anyone under the age required to consent to online services in their jurisdiction. Do not create an account for a child or submit children's personal data.

9. International processing

Infrastructure providers may process data in countries other than your own. Where required, appropriate contractual or legal safeguards should be used for such transfers before broader availability.

10. Changes and contact

This interim policy may change as Navy Pigeon develops. A finalized policy, including complete operator identity and privacy contact details, will be published before the service is offered for general use. Invited testers can raise privacy questions through their existing contact with the project owner.