This notice explains how AI Token Insights handles information on its public website and through AITI Newsroom, its private newsletter archive and editorial research tool. For a shorter introduction, read our privacy overview. Both pages form our privacy notice.

Questions or requests can be sent to eugene.cinq@aitokeninsights.com.

1. Website visits and correspondence

Our web server keeps standard technical logs that may include IP addresses, requested pages, browser information, request times, and error details. We use these records to operate, secure, and troubleshoot the website.

The website is configured to use Google Analytics to understand visits and improve content. Depending on your browser and applicable settings, analytics may collect page views, referral information, browser and device information, and identifiers stored in cookies. Google processes analytics information under its applicable terms and privacy policy.

Website analytics is separate from AITI Newsroom. We do not send Gmail message contents or mailbox credentials to Google Analytics. You can manage cookies and block analytics requests through your browser. Doing so may limit measurement but does not delete previously collected records.

If you contact us, we use the information you provide to respond and handle your request. Other websites linked from ours have their own privacy practices.

2. AITI Newsroom: a separate, private tool

AITI Newsroom supports our editorial work. It is not a public mailbox-connection service, and browsing this website does not connect your Google account or provide access to your email.

The tool accesses an editorial Google account only after its authorized user explicitly connects it through Google’s authorization process. It requests the Gmail read-only permission, gmail.readonly.

That permission allows reading mailbox data; it is not restricted by Google to newsletters alone. Our collector narrows its searches to configured newsletter senders and date ranges, and checks that it is connected to the intended account. It does not send email, change labels, mark messages read, move messages, or delete messages from Gmail.

3. Newsletter information collected

For matching messages, the archive can contain:

  • Message identifiers, sender and recipient headers, subjects, and dates.
  • Original email files, including HTML, plain text, and any attachments contained in the original message bytes.
  • Extracted text, source links, content hashes, and collection records used to check completeness and detect duplicates.
  • Label information used to check that collection has not changed mailbox state.

The collector does not execute attachments or load remote email images. Sender names and dates are recorded as supplied, not treated as proof of authenticity.

4. Research uses and Google data commitments

We use newsletters to preserve research sources, find relevant material, identify research leads, and support human-reviewed editorial work. Collection does not automatically verify a newsletter’s claims or turn it into a published article.

Mailbox-derived information is available only to the authorized operator and tools serving these disclosed purposes. The mailbox archive is not publicly searchable. We do not sell Gmail-derived information, use it for advertising or creditworthiness decisions, or use it to train or improve generalized AI or machine-learning models. Creating embeddings for research search is a disclosed processing use, not a promise that no AI processing occurs.

Our use and transfer of information received from Google APIs will comply with the Google API Services User Data Policy, including its Limited Use requirements. Connecting Gmail is not blanket permission for unrelated processing.

5. Where information goes

Local archive and credentials. Original emails and complete extracted text are stored in a private archive on the operator’s computer. Google authorization credentials are stored separately with restricted access.

Operational reporting. A collection-report workflow on our server receives sanitized operational summaries, including message identifiers, content hashes, and processing counts—not original email bodies or Gmail authorization credentials.

Pinecone research index. A separate indexing service on our server receives selected extracted newsletter text, complete text chunks, and limited source metadata and transfers them to Pinecone. Pinecone creates embeddings—representations of text used to find related material—and maintains a private searchable research index. Original email files and Gmail authorization credentials are not sent to Pinecone. The historical research library also contains newsletter excerpts; local storage of the original archive does not mean all research copies are local. Our research library also includes official project documents used as editorial sources.

Website hosting, Google Analytics, Google authorization services, and research-storage providers process information needed for their respective functions. Depending on the service, processing may occur outside your country. We limit disclosures to the stated purposes and applicable provider arrangements. Google-derived information remains subject to Google’s use and transfer restrictions.

6. Retention, revoking access, and deletion

The newsletter archive has no automatic expiry period. Archived messages and research records remain until deliberately removed.

The connected account user can revoke AITI Newsroom’s access in the third-party connections section of their Google Account. This stops further authorized access; it does not delete previously collected messages or research copies.

Email us to request deletion of collected messages, derived research records, or saved authorization credentials. We may need to verify your authority over the account or information. Requests are handled manually and include identifying relevant local records and third-party research-storage copies, including Pinecone records where applicable.

If a legitimate legal or security reason requires retaining particular information, or backup-related limitations affect removal, we will explain this. We do not promise immediate erasure from every copy.

Website logs, analytics records, and correspondence have their own retention settings and purposes. Contact us about the records relevant to your request.

7. Security and your choices

For the newsletter integration, we use restricted access, separately stored credentials, and encrypted network connections. These measures reduce risk, but no system can guarantee absolute security.

Depending on applicable law, you may have rights to request access, correction, deletion, or restrictions on the use of your personal information. Contact eugene.cinq@aitokeninsights.com to ask a question or make a request. Please do not include passwords, authorization tokens, or other account secrets.

8. Updates

We may update this notice when our services or information-handling practices change. Material changes to Google-data access, use, or sharing will be disclosed before new processing begins, with renewed consent where required.