shipAI.ca Contact
Privacy Policy

Privacy Policy for shipAI website and Transreader

This page explains how shipAI handles information submitted through the public website and how Transreader handles data inside the Chrome extension. It is intended to serve as the public privacy policy URL for both the website and the Transreader Chrome Web Store listing.

Effective date: May 2, 2026 Domain: shipAI.ca
Scope

Two products, one public policy page

shipAI currently uses this page to describe two separate contexts:

  • shipAI website: the marketing site and demo-request form published on shipAI.ca.
  • Transreader: a Chrome extension for bilingual reading that uses the user's own AI provider credentials.

The sections below distinguish what is stored locally, what is sent to third-party providers, and what is not intentionally collected for shipAI's own backend services.

Contact

Questions or requests

For website, product, or privacy questions, contact:

shipAI Website

What information we collect on the shipAI website

When someone submits the website form, shipAI may collect the business contact and quoting-intake details entered by that visitor, including:

  • work email
  • company name and role
  • RFQ channels and RFQ volume
  • primary service type
  • whether class or NMFC help is needed
  • current system information and operational pain points
  • Turnstile verification token, IP address, and user agent used for abuse prevention

How the website data is used

shipAI uses this information to review demo requests, respond to business inquiries, qualify potential pilots, and protect the site against spam or abuse. Form submissions may be stored in infrastructure operated for shipAI, including Cloudflare services and email delivery tooling used to notify the operator of a new request.

shipAI does not sell submitted website lead data. Website information is only used for operating the site, responding to requests, and running business development follow-up related to that inquiry.

Transreader Extension

What Transreader stores

Transreader stores information inside Chrome extension storage on the user's device and browser profile. This may include:

  • selected AI provider, selected model, target language, and optional endpoint override
  • the user's own API key needed to authenticate requests to the selected provider
  • recent article metadata such as URL, title, domain, reading mode, and local favorite state
  • limited local product-event metadata such as provider selection, target language, block counts, and timing or error metadata

If Chrome Sync is enabled, some settings may sync through the user's browser profile according to Chrome's own behavior.

What Transreader sends to third parties

Transreader uses a bring-your-own-key model. The user adds their own API key for OpenAI, Claude, Gemini, or a compatible custom endpoint. When the user requests translation, Transreader may send:

  • extracted article text blocks needed for translation
  • the selected target language and model parameters
  • the user's API key as part of request authentication to the selected provider

Transreader is designed to send extracted reading content rather than the full page DOM. Users are responsible for reviewing the privacy practices of any AI provider or custom endpoint they choose to use.

Data Use

Why this data is processed

  • shipAI website submissions are used to respond to inquiries and evaluate demo requests.
  • Transreader data is used to render bilingual reading views, reopen recent sessions, and send translation requests requested by the user.
  • Neither product is intended to sell personal information.
Retention

How long data may remain

Website lead information may remain in operational storage and business email systems for as long as needed to handle the inquiry and maintain business records. Transreader data stored locally remains there until the user clears extension data, removes stored settings, or uninstalls the extension.

Security Notes

Important limitations

  • No website or browser extension can guarantee absolute security.
  • Storing API keys in browser extension storage carries risk if the local device or browser profile is compromised.
  • Using a custom endpoint means data is handled according to that endpoint operator's practices.
Policy Updates

Changes to this policy

shipAI may update this page from time to time as the website, Transreader, or related data practices change. Material changes should be reflected here before or at the time those changes are released publicly.