Privacy Policy
1. Introduction
This Privacy Policy explains how STARBOARD SYSTEMS INC. ("Starboard," "we," "us," or "our") collects, uses, discloses, and safeguards information when you use the Starboard platform, including our web application, Outlook add-in, Gmail Chrome extension, public APIs, and related services (each, a "Service").
This Policy applies to:
- Customers — companies (typically freight forwarders) that subscribe to the Service.
- Authorized Users — individual employees or contractors of a Customer who access the Service.
- Visitors — anyone who interacts with our website or marketing materials.
If you are an Authorized User, your employer's agreement with us governs how your employer's data is processed; this Policy describes the personal information we handle in the course of providing the Service.
2. Information We Collect
2.1 Information You Provide
- Account information: name, work email, phone number, company name, role.
- Authentication credentials:OAuth tokens issued through your identity provider's standard sign-in flow: (a) Microsoft 365 OAuth tokens (Microsoft Entra ID); (b) Google OAuth tokens issued via Sign-in-with-Google using
chrome.identity.launchWebAuthFlowin our Gmail Chrome extension; and (c) IMAP credentials that you enter into our web application at https://app.starboard.biz and that the Gmail Chrome extension receives from that origin viachrome.runtime.sendMessagesolely to attach an existing web-app session. We do not see or store your Microsoft or Google mailbox password; IMAP credentials are held by our self-hosted mail connector on Google Cloud, encrypted at rest with a key kept in Google Secret Manager, and used only to fetch and send mail on your behalf. - Customer Content: rate sheets, quotes, freight data, customer/vendor contact details, and other freight-forwarding business records you upload, generate, or store in the Service.
- Support communications: information you provide when contacting us for help.
2.2 Information We Receive From Microsoft 365
When you connect a Microsoft 365 mailbox to the Service, we receive — only with your explicit consent and only for mailboxes you authorize:
- Email metadata (sender, recipient, subject, timestamps).
- Email content in the mailboxes you connect: we sync new and existing messages in your Inbox (and Sent Items where enabled) to detect requests for quote and rate replies.
- Attachments relevant to a quote (rate sheets, requests for quote, etc.).
- Your Outlook category list, which we use to label messages (see below).
We request these Microsoft permissions:
- Every user who connects Outlook:
offline_access,User.Read,Mail.ReadWrite,Mail.Send, andMailboxSettings.ReadWrite.MailboxSettings.ReadWriteis used only for Outlook's category list: Starboard creates its coloured labels there; when a category with the same name as one of its labels has a different colour, it deletes and recreates it in Starboard's colour, which also resets a user's own category of that name; and when Outlook's list is full it deletes old categories whose names start with#(Starboard's quote tags; a user's own#category can be removed too). Starboard does not read or change automatic replies, forwarding, inbox rules, time zone, working hours or language. - Users who work from a shared mailbox:
Mail.ReadWrite.SharedandMail.Send.Shared, to read, label and send from a shared mailbox you have delegate access to, andMail.Read.Sharedon the add-in's sign-in, to read the open message in that shared mailbox. - Outlook add-in:
User.Readto sign you in, and theReadWriteMailboxadd-in permission, which Outlook requires for the add-in to load in shared folders and shared mailboxes. - Organizations that register a shared mailbox: a Microsoft 365 administrator grants the application permissions
Mail.ReadWrite(read and label mail in the registered mailboxes with no user signed in),MailboxSettings.ReadWrite(the category list only, with the same limits as above), andMail.Send(send replies from those mailboxes). Microsoft grants these across the whole tenant. Starboard processes only the mailboxes registered with it, and your administrator can restrict the app to those mailboxes with an Exchange application access policy.
These can be reviewed and revoked by you or your IT administrator at any time in your Microsoft account or the Microsoft Entra admin center.
2.2b Information We Receive From Google (Gmail)
When you connect a Google account through our Gmail Chrome extension, we request the minimum Gmail API scopes needed to operate the Service:
openid,https://www.googleapis.com/auth/userinfo.email,https://www.googleapis.com/auth/userinfo.profile— identify your Google account and match it to your Starboard user.https://www.googleapis.com/auth/gmail.labels— create Starboard's labels in your mailbox.https://www.googleapis.com/auth/gmail.modify— apply Starboard's labels to incoming customer inquiries (for example, marking a message as processed so it is not re-ingested).https://www.googleapis.com/auth/gmail.readonly— read the content of customer inquiry emails you open in Gmail so we can parse the inquiry and prepare a quote draft.https://www.googleapis.com/auth/gmail.compose— create quote reply drafts inside the thread and, upon your explicit approval in the extension UI, send the drafted reply.
Once you connect your Google account, we watch your Gmail INBOX for new messages (using Gmail push notifications and the users.history.list delta API) to detect new customer-inquiry emails and trigger downstream automations (for example, automatically drafting a freight quote reply).
We process only new messages that arrive in your INBOX; we do not ingest Drafts, Spam, or other labels, and we do not perform historical backfills (only mail that arrives after you connect is processed). To follow a conversation, we read the headers (sender, recipients, and date, not the message content) of other messages in the same thread, including your sent replies. We do not use Gmail data to train AI or machine-learning models, and we do not serve advertising. These scopes can be reviewed and revoked at any time from your Google Account's Third-party apps & services page.
2.2c Google API Services User Data Policy — Limited Use
STARBOARD SYSTEMS INC.'s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:
- We limit our use of Gmail data to providing and improving user-facing features (inquiry ingestion, quote drafting, quote sending) that are prominent in the extension's UI.
- We do not transfer Gmail data to third parties except (a) with your consent to provide or improve user-facing features, (b) for security purposes such as investigating abuse, (c) to comply with applicable law, or (d) as part of a merger, acquisition, or sale of assets after obtaining your explicit prior consent.
- We do not allow humans to read Gmail data unless (a) we have your affirmative agreement for the specific messages, (b) it is necessary for security purposes such as investigating abuse, (c) it is necessary to comply with applicable law, or (d) the data is aggregated and used for internal operations in accordance with applicable privacy law.
- We do not use Gmail data to serve advertisements, and we do not sell Gmail data or transfer it to data brokers, information resellers, or for creditworthiness or lending purposes.
- We do not use Gmail data to develop, improve, or train generalized or non-personalized AI or machine-learning models, including Starboard's own models. AI providers that process Gmail data on our behalf (Section 4) do so only to perform the user-facing task and may not use it to train their models.
2.2d IMAP Mail Access
If you are an IMAP user, you enter your mailbox host, username, and app-password into the Starboard web application at https://app.starboard.biz. The Gmail Chrome extension obtains an existing web-app session from that origin via chrome.runtime.sendMessage and never receives or stores your raw IMAP password. All IMAP fetches and sends occur server-side over TLS; credentials are held by our self-hosted mail connector, encrypted at rest with a key kept in Google Secret Manager (see Section 9), and used only to retrieve customer inquiries and send freight quote replies you approve.
2.3 Information We Collect Automatically
- Usage data: features used, actions taken, timestamps, session identifiers.
- Device and log data: IP address, browser type, operating system, error logs.
- Cookies and similar technologies: session cookies for authentication, and analytics tools (Google Analytics and Hotjar) in parts of the Service to understand how it is used. On our public website, we and our advertising and analytics partners (currently Google and OpenAI) use cookies and similar technologies to understand site usage and measure the performance of our advertising, such as whether an ad led to a booked demo. We do not use advertising cookies inside the Service.
2.4 Information From Third Parties
- Carrier and rate data sources: publicly listed or licensed freight rate information used to fulfill quote requests.
- Service providers: information from our subprocessors (listed in Section 6) limited to what is necessary to operate the Service.
3. How We Use Information
We use the information we collect to:
- Provide, operate, and maintain the Service.
- Process freight quotes, parse rate sheets, generate responses, and synchronize bookings with integrated systems (e.g., CargoWise).
- Authenticate Authorized Users and enforce company-level data isolation.
- Provide customer support and respond to inquiries.
- Improve and develop new features (using aggregated and de-identified data where feasible).
- Create aggregated statistics, such as market rate ranges for shipping lanes, that combine data from multiple Customers and do not identify any Customer, its customers or its personnel, or reveal a Customer's rates.
- Measure and improve our website and marketing, including the performance of our advertising.
- Detect, prevent, and respond to fraud, abuse, security incidents, and violations of our Terms of Service.
- Comply with legal obligations, enforce our agreements, and protect the rights, property, or safety of Starboard, our Customers, or others.
4. AI and Machine-Learning Processing
The Service uses third-party AI model providers to extract information from emails, attachments, and rate sheets; to resolve locations, commodities, customers, and charge codes; to generate quote drafts; and to assist with related tasks. Our current providers are OpenAI, Google (Gemini models on Google Cloud Vertex AI), Anthropic, and TypeSafe AI. Documents such as PDF rate sheets and email attachments may first be converted to text by LlamaIndex (LlamaParse) or Microsoft Azure AI Document Intelligence. All are listed in Section 6.
- We send to a provider only the content needed for the specific task (e.g., the email body and rate sheet a User asks the Service to process). We do not send credentials, API keys, or bulk mailbox history.
- We use each provider's business API, whose terms do not permit the provider to use our inputs or outputs to train its models, and we minimize provider-side retention where supported (for example, we set
store=Falseon OpenAI endpoints). - Providers may retain submitted content for a limited period for abuse-monitoring or operational purposes before deletion: up to 30 days for OpenAI, Anthropic, and Google; within 24 hours for Microsoft Azure AI Document Intelligence; a 48-hour parse cache for LlamaIndex; and only as long as needed to provide its service for TypeSafe AI.
- We use Customer Content to train Starboard's own internal models, such as the models that recommend margins, rank rates, and extract quote details from emails, so the Service can quote faster and price more accurately. Before Customer Content is used for training, we remove names, email addresses, and other contact details. These models are used only to provide the Service; we do not sell or share them or their training data, and the training data stays within Starboard's own cloud environment. Third-party AI providers do not train on Customer Content. We never use data obtained through Google Workspace APIs, including Gmail, for this purpose.
- Outputs from LLMs may be inaccurate or incomplete. Authorized Users are responsible for reviewing AI-generated content before sending it to a customer or relying on it commercially.
5. How We Share Information
We do not sell personal information. We share information only as described below:
- With your Company:Authorized Users of the same Customer may see Customer Content created within that Customer's workspace, subject to role-based controls.
- With Subprocessors: see Section 6.
- With Integration Partners: when you choose to connect an integration (e.g., CargoWise, Front, a TMS), data flows between the Service and that partner per your configuration.
- With Advertising and Analytics Partners: when you visit our public website, partners such as Google and OpenAI may receive information such as cookie identifiers, the pages you visit, and whether you booked a demo, so that we can measure our advertising.
- For legal reasons: in response to lawful requests from public authorities, to comply with legal process, to enforce our agreements, or to protect rights, property, or safety.
- In a corporate transaction: in connection with a merger, acquisition, financing, or sale of assets, subject to the protections of this Policy.
- With your consent: for any other purpose disclosed at the time of collection.
6. Subprocessors
We use the following subprocessors to operate the Service. Each is contractually bound to confidentiality and security obligations consistent with this Policy.
| Subprocessor | Purpose | Region | Certifications |
|---|---|---|---|
| Google Cloud Platform | Backend compute (Cloud Run, Secret Manager); AI model inference (Gemini on Vertex AI) | United States (us-east4); Vertex AI: US for the main model, other calls not pinned to a region | SOC 1/2/3, ISO 27001, PCI DSS, FedRAMP |
| Supabase (on AWS) | Application database, file storage | United States (us-east-1) | SOC 2 Type II |
| Vercel | Web application hosting and edge delivery | United States | SOC 2 Type II |
| Upstash (on AWS) | Cache, job queue, and session data | United States | SOC 2 Type II |
| OpenAI | Large language model inference for AI features | Standard API, not pinned to a region | SOC 2 Type II |
| Anthropic | Large language model inference for AI features | Standard API, not pinned to a region | SOC 2 Type II, ISO 27001 |
| TypeSafe AI, Inc. | AI model inference for location, commodity, customer, and charge-code resolution | United States | SOC 2 Type II |
| LlamaIndex (LlamaParse) | Document parsing (PDF rate sheets) | United States | SOC 2 Type II |
| Microsoft (Azure AI Document Intelligence) | Document parsing (email attachments, PDF rate sheets) | United States | SOC 1/2/3, ISO 27001 |
| Api2Pdf | PDF generation for quote documents | United States | — |
| Amazon Web Services (SES) | Sending email from the Service (sign-in links, notifications, messages) | United States | SOC 1/2/3, ISO 27001 |
| Elastic | Search indexing | United States | SOC 2 Type II |
| Microsoft (Graph API) | OAuth authentication and email integration | Per Microsoft tenant region | SOC 2, ISO 27001, FedRAMP |
| Google LLC (Gmail API) | OAuth authentication and mailbox access for Gmail Chrome extension users (read customer inquiries, draft and send freight quote replies) | United States | SOC 1/2/3, ISO 27001 |
| Sentry | Application error monitoring | United States | SOC 2 Type II |
| Hotjar | Product usage analytics in the web application and Outlook add-in | European Union (Ireland) | SOC 2 Type II, ISO 27001 |
| Google LLC (Google Analytics) | Page-view analytics in the web application and Outlook add-in | United States | SOC 1/2/3, ISO 27001 |
We update this list as our subprocessor arrangements change. Material changes will be communicated to Customers in accordance with the Terms of Service.
7. International Data Transfers
The Service is hosted in the United States. If you access the Service from outside the United States, your information will be transferred to and processed in the United States. Some subprocessors process information elsewhere: Hotjar stores product analytics data in the European Union (Ireland), and some AI model providers' standard APIs are not pinned to a region (see Section 6).
8. Data Retention
- Customer Contentis retained while the Customer's subscription is active and for 90 days after termination, after which it is deleted or anonymized except where retention is required by law.
- Account information is retained for the life of the account and for a reasonable period thereafter to support audit, dispute, and legal-defense needs.
- Request logs are retained for up to 30 days, error-monitoring data for up to 90 days, and product analytics data for up to 365 days (Hotjar) or 14 months (Google Analytics).
- Backups: deleted data remains in database backups for up to 7 days, until those backups expire.
- Cached data (Redis): time-limited, typically minutes to hours, and auto-expires.
- OAuth challenges: 5-minute TTL.
A Customer may request deletion of its data on termination per the Terms of Service.
9. Security
We maintain administrative, technical, and physical safeguards designed to protect personal information, including:
- TLS/HTTPS for data in transit and AES-256 encryption at rest at the storage layer.
- Company-level data isolation enforced through query scoping and database row-level security.
- OAuth 2.0 with PKCE for authentication; access tokens are short-lived and refresh tokens are kept server-side in our access-controlled database, encrypted at rest.
- Secrets stored in Google Secret Manager and Vercel encrypted environment variables — never in source code.
- Logging and monitoring through Sentry and provider-native tooling.
- Regular review of access controls and dependencies.
No system is perfectly secure. If we become aware of a security incident affecting your information, we will notify affected Customers without undue delay and consistent with applicable law.
10. Your Rights
Depending on where you live, you may have rights regarding your personal information, including the right to:
- Access the personal information we hold about you.
- Correct information that is inaccurate or incomplete.
- Delete your personal information, subject to legal exceptions.
- Restrict or object to certain processing.
- Portability — receive your information in a structured, machine-readable format.
- Withdraw consent where processing is based on consent.
- Lodge a complaint with a supervisory authority.
To exercise these rights, contact us at admin@starboard.biz. If you are an Authorized User of a Customer, please direct rights requests to your Customer (your employer or organization), which acts as the controller for Customer Content; we will support the Customer in responding.
11. Children's Privacy
The Service is intended for business use and is not directed to individuals under 16. We do not knowingly collect personal information from children. If you believe we have collected information from a child, contact us and we will delete it.
12. Changes to This Policy
We may update this Policy from time to time. The "Last updated" date at the top reflects when changes were made. For material changes affecting Customer Content, we will provide reasonable advance notice (e.g., by email or in-product notification).
13. Contact Us
Starboard Systems Inc.
120 Adelaide Street West, Suite 2500
Toronto, ON M5H 1T1
Canada