Your workspace is private to your account. Optional connections and notifications share the information needed for the features you choose. This policy explains those flows and how to request access or deletion.
On this page12 sections
Who is responsible
Compiling operates this service from Canada. Compiling is responsible for protecting personal information and handles privacy questions at contact@compiling.app. Use “Privacy request” in the subject. This policy covers the Compiling website, account service and connected workspace.
Information we handle
- Account and business profile: your name, email address, password hash, verification status, sessions, acceptance records, business names, region, time zone and tax registrations.
- Workspace records: orders, products and images, inventory, storage and delivery addresses, shipments, sales, expenses, invoices, contacts, notes, uploaded files and source emails or attachments.
- Connections and preferences: provider identity, authorization tokens or app passwords, sync choices, notification events and Discord webhook details.
- Service records: support messages, selected parser examples, processing failures, notification delivery status, IP addresses, timestamps, request information and diagnostics used to operate and secure the service.
Only provide information you are entitled to use. Records can contain personal information about customers, recipients or other people. Avoid unnecessary sensitive information.
Why we use it
We use this information to run your account, import and organize records, calculate results, show shipment activity, deliver the notifications you choose, answer support requests and investigate failures or abuse. We do not sell personal information or use workspace records for advertising. Customer records and saved email examples are not made available to other customers; published parser rules are shared as described below.
Gmail and other inboxes
Connecting an inbox is optional. The Gmail API connection requests read-only access. This permission can read mailbox contents and settings; Google does not restrict it to receipts. Compiling searches and reads messages according to your selected stores, history and supported email formats, including archived mail and available Spam or Trash folders. Matching headers, message bodies and attachments can contain order references, products, prices, addresses and tracking details.
Original emails, attachments and extracted records may be retained in your workspace so you can review their source. Read-only means Compiling cannot send, edit or delete Gmail messages through this permission; it does not mean that imported content is never stored. Supported IMAP connections use the credentials you supply for email import. Older authorizations may have different scopes: review the permissions shown by your provider.
Disconnect an inbox in Accounts to stop future access through that connection. You can also revoke authorization in your Google Account. Disconnecting or revoking access does not delete records already imported, saved parser examples or copies already delivered to an enabled integration.
AI parsing, saved examples and human review
When you create, extend or repair a parser, a separate agreement covers sending your selected example emails and instructions to the configured AI provider and allowing Compiling to review those examples. The contents can include personal information in the messages. Select only examples needed for the task. Ordinary imports using existing extraction rules do not send every imported email to AI.
The private parser library retains selected examples, sender and subject information, instructions, generated rules and failure history so the requested parser can be checked and repaired. Other users receive published extraction rules, not your saved example messages. This agreement does not grant access to unrelated mailbox messages. Removing a parser from a list does not automatically erase saved examples; contact us to request removal.
Other AI-assisted features, when you choose to use them, send the submitted question or file and the relevant workspace context to the provider configured for that feature. That context may include products, transactions, financial summaries or document content. Saved connector secrets are excluded from assistant context; do not put passwords or unnecessary personal data in your prompts or files. Compiling does not use Google user data to train general-purpose AI models.
Notifications and Discord
The in-app notification menu shows recorded order and shipment activity in your workspace. It does not by itself enable Discord messages, browser push messages or promotional emails.
Discord is optional and configured per business. When you save a webhook and enable events in Settings → Notifications, Compiling sends those event messages to that channel. Depending on the event, a message can include product names and images, store or sales channel, order reference, quantity, total and currency, purchase date, status, carrier, tracking number and carrier link, expected delivery date, and the latest scan description, time or location. Discord and anyone with access to that channel can receive or retain those details. Use a channel you control and are authorized to share with.
The webhook secret is stored encrypted. Compiling also keeps delivery, retry and error information to operate notifications. New orders, cancellations, shipping emails and carrier activity can trigger the events you select. Initial imports and historical backfills establish a silent baseline rather than sending every old order as a new alert.
You can change events, disable notifications or remove the webhook in Settings → Notifications. Turning them off clears pending messages; it cannot recall a message already handed to Discord. “Send test” sends a connection test when you request it, including when automatic notifications are off. Removing the webhook does not erase posts already in Discord. Manage those copies in Discord under Discord’s privacy policy.
Account verification, password resets and necessary service or security messages are separate from optional shipment alerts. Enabling order notifications is not consent to marketing. If promotional messages are offered, their consent and unsubscribe controls will be provided separately where required.
Shipment tracking, maps and external content
Tracking services receive shipment identifiers, carrier information and the references needed to match updates. The current integration supports AfterShip and other configured carrier-data services. Their responses can include status, delivery estimates, scan times and locations. Background monitoring and provider callbacks can update a saved shipment without the workspace being open.
Map tiles are requested from OpenStreetMap services. Map providers can receive your IP address and the area requested by your browser. Road routing sends the scan or destination coordinates needed to draw an estimated route to the configured routing service. These are shipment-location estimates, not live GPS tracking of a person or device. Opening a carrier link sends you to that carrier’s website. External product images can also cause a request to their host; some images are served from Compiling’s cache.
Service providers and international processing
Hosting and infrastructure providers process account and workspace information to run the service. Resend delivers account emails and receives the recipient address and message content, including any temporary account link. Its configured sending region is North Virginia, United States. AI providers receive the examples, files or context needed for the feature you request. Tracking providers, map services and Discord receive the information described above when those features are used.
Information may be processed outside your province, territory or country, including outside Canada, and be subject to local laws. Provider practices and locations can change; contact us for the providers involved in your account. We will update relevant disclosures and seek fresh consent where required before adding a materially different use or recipient. Provider links: Resend, AfterShip, OpenStreetMap Foundation and Discord.
Google data and Limited Use
Compiling’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements, and the Google Workspace user data and developer policy. Google data is used for the disclosed, user-facing features you request. It is not sold, used for targeted advertising or used to determine creditworthiness.
Human access to Google data is limited to the specific material you affirmatively agree to share, necessary security investigations, applicable legal requirements or other uses expressly permitted by those policies. Transfers are limited to requested features with your consent, permitted security or legal needs, and a business transfer only with your prior consent. Routine operator access is not permission to browse unrelated mailbox contents.
Retention and deletion
Account and workspace records are retained while needed to provide your account and the purposes described here. We consider your account status, the record’s purpose, your deletion request and any legal, security or dispute-related need. Expired beta access, disconnecting an inbox and removing a webhook are not account-deletion requests.
Ask us to delete an account, imported content or selected parser examples at contact@compiling.app. Identify the account and the category of information; do not send passwords or a full mailbox. We verify ownership before releasing or deleting data and explain relevant restrictions. Existing backup copies may remain until replaced or removed and are not used as an active workspace. Copies sent to external services are subject to those services’ retention and deletion controls.
Your choices and rights
You can edit available profile and workspace information, choose import settings, disconnect providers, change notification settings and request access, correction, export or deletion. You can ask about withdrawing consent or raise a privacy complaint with us and, where applicable, the relevant privacy regulator. Some features need particular information to work; manual order entry does not require connecting Gmail or enabling Discord.
For information a business has placed in its workspace about you, contact that business first. Compiling can assist with requests within its role. Deleting a business and deleting your Compiling account are different actions; export needed records and read the confirmation before deleting a business.
Security and policy changes
Compiling uses HTTPS, authenticated access, separate customer workspaces, hashed passwords and encrypted storage for saved connector credentials and webhook secrets. These measures reduce risk but do not make any internet service immune to loss or unauthorized access. Report a suspected incident promptly to contact@compiling.app; we will investigate and provide notices required by applicable law.
The date and version above identify this policy. Material changes will be brought to affected users’ attention through an appropriate in-app or account communication. We will obtain consent where required before a new use of information. This policy does not give blanket permission for undisclosed future features.
Contact contact@compiling.app. Please do not send passwords or full mailbox contents.