Synthreo
Legal Privacy Data Protection

Privacy Policy

Synthreo, Inc. · · Version 2.0

Synthreo processes customer content to deliver the Services and uses separate account and Product Data to operate, support, secure, and improve the product. We do not train or fine-tune AI models on customer content, even with consent. Personal and sensitive data may be processed in supported configurations, with advance notice and applicable agreements for regulated workloads. This policy explains the information we handle and the choices available to you.

This policy covers synthreo.ai, Wingtip, Pylon, Threo, Canopy, and Managed AI Services. It complements the End User License Agreement (“EULA”). It does not expand the content-use rights granted by your contract or override our Data Processing Addendum (“DPA”) or an executed Business Associate Agreement (“BAA”). Capitalized terms not defined here have the meanings in the EULA.

1. Who handles your information

Synthreo, Inc. is a Delaware corporation headquartered in Phoenix, Arizona.

For personal information submitted by a customer to use the Platform, Synthreo acts as a processor or service provider on that customer’s documented instructions. The customer may be the controller or may act for its own End Client. MSP and distributor roles depend on the actual processing chain and applicable DPA.

Synthreo acts as a controller for information needed for its own business relationship, including account administration, billing, security, website operation, service communications, lawful marketing, and the Product Data uses in Section 3.3. We distinguish these activities from processing customer content.

Our Data Processing Addendum applies automatically under the EULA; a countersigned copy is available from privacy@synthreo.ai. PHI processing for which HIPAA requires a BAA requires an executed Business Associate Agreement and a HIPAA-eligible configuration before processing begins; request one from privacy@synthreo.ai.

2. Information we collect

2.1 Account and business information

We collect names, business contact details, company information, account settings, billing records, and communications you send to us. Payment information is handled through payment providers as applicable. We receive necessary account and service information from an MSP Partner if it supplies your subscription.

2.2 Customer content

Customers and their users may submit prompts, files, documents, conversation content, configurations, workflow logic, and other information and generate outputs. When a user directs the Wingtip browser extension to work on a website, the page text, page structure, screenshots, and open-tab titles and addresses it reads for that request are customer content. This content may contain personal or sensitive information. Customers retain their ownership rights as described in the EULA.

We process this content for the configured service, related customer-directed support, security, legal obligations, and establishing, exercising, or defending legal claims concerning the Services, subject to the applicable DPA or BAA. Providing it for a support case does not authorize inclusion in a general research or model-training dataset.

2.3 Product and technical information

Product Data includes feature usage counts, token and execution counts, latency, availability, error codes, billing measurements, and security events. It is designed to exclude the substance of customer prompts, documents, outputs, and customer-specific business logic; customer content that appears in operational records remains customer content and is not used for product improvement.

Technical or account-linked records may include IP addresses, approximate location, device/browser information, session identifiers, page visits, timestamps, and activity associated with an account or tenant. Tenant audit logs of actions by a customer’s authorized users and AI agents are customer content under Section 2.2, not records described in this section. Such records may be personal information; we do not describe all analytics or technical records as anonymous.

Model selection and routing identifiers, weighted session and weekly consumption, allowance balances, and reset records are Product Data used to administer fair use, show usage, enforce disclosed limits, and investigate metering issues. These records are designed to exclude the substance of customer prompts and outputs, but may be personal information when linked to a user. They remain subject to the purposes, safeguards, and retention rules in this policy.

2.4 Other sources

We may receive information from business directories, lawful public sources, and providers helping prevent fraud or verify accounts, and use it only for the purposes and legal bases described here. Information retrieved from customer-authorized integrations to perform the Services is customer content under Section 2.2 and is processed only as that section describes.

2.5 Sensitive and regulated data

Personal information and sensitive business data are permitted in supported configurations. Notify privacy@synthreo.ai before beginning processing subject to specialized legal requirements so the data categories, safeguards, and agreements can be documented.

Where HIPAA requires a BAA for PHI processing, the BAA must be signed before that processing begins. Other regulated workloads require the agreed safeguards and any required DPA before use. Zero Data Retention at the inference-provider layer does not replace a BAA or other legal and security requirements. Sensitive data is not automatically deleted merely because it is sensitive.

3.1 Delivering and supporting the Services

We process information to provide requested functionality, maintain customer configurations, deliver outputs, resolve support cases, administer subscriptions, and process billing. Customer content is processed within the customer’s instructions and the agreement.

We use necessary records to protect accounts, detect misuse and fraud, investigate incidents, comply with law, and establish or defend legal claims. Any access to customer content must be limited to the applicable service, security, or legal purpose and consistent with the DPA or BAA.

3.3 Product improvement

We use Product Data to diagnose defects, evaluate feature use and performance, plan capacity, improve usability and reliability, and support the product. We may use aggregate statistics that cannot reasonably identify an individual or customer and do not reveal content or confidential business logic. We do not attempt to re-identify those statistics.

Identifiable operational records remain subject to this policy and applicable contractual restrictions. Optional research involving customer content requires a separate, specific written opt-in describing its purpose, scope, and withdrawal process. Such participation does not authorize model training. Declining optional research does not reduce purchased functionality.

3.4 Communications

We send account, billing, service, and security communications necessary for the business relationship. We send marketing only with consent or another applicable lawful basis and provide an unsubscribe method. Declining marketing does not stop necessary service notices.

Where a legal basis is required, our controller activities rely on contract performance, legal obligations, consent, or legitimate interests such as security, business administration, and product reliability, subject to the required balancing of individual rights. We rely on legitimate interests for website analytics, which runs on an opt-out basis as Section 6 describes, and obtain consent for marketing where applicable law requires it.

For customer-controlled content, the customer determines the lawful basis; Synthreo processes under its instructions and the DPA. A user’s acknowledgement of this policy is not blanket consent to optional processing or a waiver of privacy rights.

4. No model training and Zero Data Retention

Synthreo does not train or fine-tune AI models on customer content, outputs, or customer-specific business logic, with or without consent, and has never done so. We do not offer a model-training opt-in or opt-out and do not authorize model providers to train on that content.

Retrieval, prompting, and transformation used to answer a request are not model training. Zero Data Retention (ZDR) applies only to third-party inference providers: they process model inputs to generate outputs but do not retain those inputs or outputs after inference.

Synthreo stores customer data to provide the product, including conversation histories, uploaded files, outputs, workflow configurations, and audit records. ZDR does not apply to storage by Synthreo or its application backups. Those records remain subject to our access controls, security safeguards, and the export, retention, and deletion rules in Section 9 (for an existing customer’s Services, as EULA Section 28.3 provides) and any applicable DPA or BAA. Synthreo does not use that stored content to train or fine-tune AI models.

5. AI processing and human oversight

AI outputs may be inaccurate, incomplete, or non-unique. Customers must use appropriate human review for high-risk decisions and maintain required approvals for sensitive actions. Customer configuration or acceptance of responsibility does not waive required human oversight or applicable law.

We do not use optional product analytics to make decisions with legal or similarly significant effects about individuals. The EULA’s acceptable-use requirements govern customer-configured automation.

6. Cookies and similar technologies

Our website may use cookies, local storage, pixels, and similar technologies for operation, preferences, analytics, and marketing measurement. Essential storage supports functions such as security and saving preferences. Analytics services include Google Analytics, Google Tag Manager, and Microsoft Clarity; the data they handle may contain technical identifiers.

On synthreo.ai, analytics storage is on by default when you visit: Google Tag Manager loads Google Analytics and Microsoft Clarity before you make a choice. Advertising and personalization storage are off by default. You can turn analytics off, or advertising on, in the cookie banner when you first visit. To change a later choice, clear this site’s stored data in your browser. You can also contact privacy@synthreo.ai and we will delete analytics data we can associate with you, although an emailed request cannot change the setting stored in your browser. Because analytics loads before a stored choice is applied, a small amount of analytics data may be collected at the start of a page view even after you opt out. You can also use browser controls to manage stored cookies. Some storage is necessary for requested functionality. Cookie choices do not authorize model training or broader use of customer content.

Our website does not currently respond to Do Not Track or Global Privacy Control signals. To opt out, use the cookie banner (or clear this site’s stored data to see it again); you can also ask privacy@synthreo.ai to delete analytics data we can associate with you, as this Section describes.

7. Recipients and disclosures

7.1 Service providers and subprocessors

We engage providers for infrastructure, model processing, payment, support, communications, and analytics under appropriate contracts restricting their processing and requiring security and confidentiality. Synthreo remains responsible for delegated processor obligations under its DPA.

A current subprocessor list is published on our Trust Center and available from privacy@synthreo.ai. We keep the subprocessor list current, update it before a new subprocessor processes customer personal data, notify subscribers to list updates when it changes, and consider objections, as Section 6.2 of the DPA describes. Subcontractors handling PHI follow Section 6 of an executed BAA.

7.2 MSP Partners and distributors

Where you purchase through an MSP Partner, we share the information necessary for authorized account administration, support, billing, and delivery. A distributor receives access only as authorized for its role and documented processing chain. We do not give channel participants unrestricted access to client content merely because they sell Services.

7.3 Customer-selected integrations

Enabling an external integration may transmit information to that service according to your configuration. Its provider’s terms and privacy practices apply to its independent service. This does not remove Synthreo’s obligations for its own processing, integration work, or chosen subprocessors.

We may disclose information where required by law or where necessary for lawful security or rights-protection purposes, subject to applicable contractual and legal restrictions. Where permitted, we notify affected customers before a disclosure required by legal process and limit it to what is required.

Information may transfer to a successor in a merger, acquisition, or transfer of the business, subject to continuing applicable safeguards. We will provide required notice of material changes and available choices.

We do not sell personal information, and we never share customer content or Product Data for cross-context behavioral advertising. If our website marketing technologies are considered sharing under applicable law, you can opt out through the cookie banner as Section 6 describes, or contact privacy@synthreo.ai to have analytics data we can associate with you deleted; opting out does not stop analytics data collected at the start of a page view before your choice is applied. Any other optional disclosure requires an applicable lawful basis and specific consent where required.

8. Transfers and residency

Synthreo hosts customer environments on Azure in the United States and Canada. Customer Data stored by Synthreo, including encrypted backups, remains in Azure regions within the country, the United States or Canada, assigned to the customer’s environment and identified in the account documentation or Quote. Subprocessors that store customer data in another country are identified on the subprocessor list. This regional storage policy applies by default.

Inference processing may occur outside the storage region unless inference region locking has been requested and agreed. Synthreo can provide inference region locking for supported models and configurations; additional charges and model limitations may apply and must be disclosed and accepted before activation. An activated inference restriction applies to automatic routing, fallbacks, and manual model selection. Inference-provider ZDR applies with or without inference region locking. Customer-authorized transfers to independently selected integrations follow their settings and terms.

For restricted transfers, applicable safeguards may include EU Standard Contractual Clauses, UK Addendum, and Swiss adaptations where required. Section 7 of the DPA sets out the mechanism. Request a copy of relevant safeguards from privacy@synthreo.ai.

9. Retention, export, and deletion

9.1 Self-service and assisted exports

Export is a built-in feature available at any time while tenant access continues to every authorized user, within their existing data-access permissions. During a suspension or restriction, export of the suspended or restricted functions follows EULA Section 9.7. Users may export stored data, outputs, and customer-specific logic without contacting support, giving advance notice, or obtaining separate Synthreo approval. Exhausting an AI session or weekly allowance does not itself prevent export of stored data.

For an assisted export, contact help@synthreo.ai. An assisted request received before termination will be delivered within ten calendar days after receipt, including where delivery falls after termination, except as EULA Section 9.7 provides during a suspension or restriction addressing an active security threat to the data requested; PHI under an executed BAA is delivered within ten calendar days without that exception, as BAA Section 11 provides. This deadline applies only to assisted requests. Identify the tenant and scope; we will promptly address authorization questions.

Export does not include Synthreo source code or proprietary platform components and does not guarantee portability of the runtime. Standard export is included; separate migration work may require an agreement.

An export request first received after termination may be accommodated if the data remains available, but export or recovery is not guaranteed unless it is made during the 30-day access-end period in EULA Section 9.7, while the data remains available, by an administrator of that tenant (or, for PHI, the BAA Customer) or law, a DPA, or BAA requires it. Data needed for a timely pre-termination request remains protected until delivery.

9.2 Retention schedule

  • Customer content (Customer Data, Output, and Client Implementations): Deleted from active systems within ten calendar days after termination or receipt of an authorized deletion request identifying the data, whichever occurs first, or, where access ends in the circumstances that start the 30-day access-end period in EULA Section 9.7, within ten calendar days after that period ends (or after a tenant administrator’s earlier deletion request). Customer content that appears in support correspondence, Synthreo’s own security records, or Product Data records is kept only for the periods stated below for those records (for support correspondence, the shorter period stated for customer content in it), and only for the support or security purpose they serve. Send requests to privacy@synthreo.ai. We promptly address authorization and scope questions. Earlier mandatory deadlines, required legal retention, a customer-requested legal hold under EULA Section 9.7, and preservation needed to fulfill a timely export request apply; export-preserved data is deleted promptly after delivery unless further retention is legally required, a customer-requested legal hold under EULA Section 9.7 applies, or the 30-day access-end period in EULA Section 9.7 has not yet ended.
  • Backup copies: Encrypted and retained in the customer’s assigned storage country on a rolling 90-day cycle from creation of each backup, then deleted through rotation. Selective deletion of customer records from existing backups may not be technically feasible and is not part of the ten-day active-data deadline. A new backup does not necessarily erase earlier recovery points. Backups from the active system after deletion reflect the deletion, but older copies may retain the data until expiry. Copies remain isolated from ordinary use and protected; copies created before active deletion may remain for up to 90 days after that deletion, subject to required legal retention and controlling DPA or BAA obligations. If a backup is restored, deletion instructions are reapplied before the data is made available for ordinary use, and restoration does not restart retention. Retention does not guarantee recovery or extend customer access.
  • Account and business-contact records: Retained for the business relationship and then for any billing, security, or legal purpose described in this schedule.
  • Billing and transaction records: Retained for applicable tax and accounting requirements, generally seven years.
  • Support and business correspondence: Retained while needed for the relationship, resolution of the matter, or legal claims; customer content supplied for support remains subject to the DPA or BAA and is kept only while needed to resolve that matter and related service obligations, and longer only under a customer-requested legal hold under EULA Section 9.7 or legally required retention.
  • Identifiable technical, usage, and security records, including Product Data records (other than billing and transaction records): Retained for up to 24 months, unless a shorter contractual requirement, a longer lawful security investigation, a legal hold that law requires, or a customer-requested legal hold under EULA Section 9.7 applies.
  • Non-identifying aggregate Product Data: May be retained while useful for the purposes described in Section 3.3, without customer content or confidential business logic.

We restrict access to retained records and, when their retention purpose ends, delete them; records that contain no customer content and no PHI may instead be aggregated or de-identified so that they no longer identify a customer or individual, as EULA Section 9.3 describes. A DPA, BAA, or mandatory legal duty overrides this default schedule for covered data.

9.3 Deletion and cancellation are different

Individual privacy requests and customer processing instructions do not require subscription cancellation. Send privacy requests to privacy@synthreo.ai. We will refer requests about customer-controlled information to the relevant customer, as Section 8.1 of the DPA describes, and assist with fulfillment.

Send subscription cancellation and non-renewal notices to legal@synthreo.ai under the EULA. Simply stopping use does not cancel a contract. Ending a contract triggers its Customer Data deletion process; it does not eliminate legal recordkeeping duties.

10. Your choices and rights

Depending on applicable law and our role, you may request access, correction, deletion, portability, restriction, objection to processing, withdrawal of consent, or review of covered automated decisions. California residents may also exercise applicable rights to know, limit use of sensitive information, and opt out of sale or sharing; Synthreo does not sell personal information, and website marketing technologies can be declined as Section 6 describes.

We do not discriminate for exercising protected privacy rights. We do not condition purchased service quality on optional research or marketing consent. Necessary processing and lawful retention may continue where another legal basis applies.

Contact privacy@synthreo.ai. We will verify identity proportionately, recognize authorized representatives where required, and respond within applicable deadlines. Response periods depend on the right and applicable law. Access requests are generally answered within one month under GDPR/UK GDPR, 45 calendar days under CCPA/CPRA, and 30 days under PIPEDA, subject to applicable timing rules and lawful extensions. Rights with shorter deadlines, including applicable opt-out or limitation requests, follow those shorter deadlines. An emailed request to delete analytics data deletes the analytics data we can associate with you; it does not opt you out of future analytics, which only the cookie banner records (Section 6). Requests are generally free; any refusal or charge must be permitted by the applicable law.

We acknowledge requests within ten business days, or sooner where required. This acknowledgement period does not extend the deadline to act on a request. You may complain to your relevant privacy regulator, including the applicable EU or UK authority, the Office of the Privacy Commissioner of Canada, or the Office of the Australian Information Commissioner. Requests about customer-controlled data are referred to the customer as DPA Section 8.1 describes, without limiting our duty to assist.

11. Security and HIPAA

Synthreo maintains security controls aligned with the SOC 2 Trust Services Criteria (not a SOC 2 certification or independent audit report) and complies with HIPAA obligations applicable to covered Services and its role. Current security documentation is available on our Trust Center and on request. An executed BAA and a HIPAA-eligible configuration, as the BAA defines it, must be in place before covered PHI processing.

Safeguards include encryption, tenant separation, access controls, multi-factor authentication enabled by default, monitoring, personnel confidentiality, and incident response. No system can guarantee absolute security; this does not disclaim our express contractual safeguards.

We notify affected customers without undue delay after becoming aware of a personal-data breach and provide available information and updates. Applicable law, a DPA, or BAA may require more specific timing. A controller’s deadline for reporting to a regulator is separate from our notice to that controller.

12. Children

Services are for business users who are at least 18 or the age of legal majority, whichever is higher. They are not directed to children. Customer-controlled records about minors may be processed only where the customer has lawful authority and the required safeguards; a record concerning a minor does not make that individual an account user.

Contact privacy@synthreo.ai about suspected unauthorized collection or accounts. We will investigate and take the action required by law and the applicable customer instructions.

13. Changes to this policy

We publish revisions with a revision date and version. We provide at least 30 days’ advance notice of material changes to this policy as it applies to customer accounts and Services, except when an earlier legal change is required, in which case we provide prompt notice. Changes to Section 6 apply to website visits from publication. Subprocessor changes follow Section 7.1 and DPA Section 6.2 and are not changes to this policy. This version (2.0) was published on October 12, 2026. It applies from then to new customers, and to an existing customer’s account and Services from the date EULA Version 2.0 takes effect for them under EULA Section 28.3, including that Section’s rule for post-termination export, retention, and deletion; until then the previous version applies to them, except that this version’s descriptions of how Synthreo, the Platform, and the website operate, namely Sections 4, 6, and 11, apply to everyone from October 12, 2026. For website visitors, prospects, and other individuals whose information is not processed for an existing customer’s account or Services, this version applies from October 12, 2026, and Section 6 applies to every visit to synthreo.ai from that date. We obtain new consent where required.

A policy update does not by itself expand our contractual rights over customer content or Product Data or change a committed subscription. Contract amendments and existing-customer transition follow EULA Section 28.3. Continued use is not a substitute for consent where consent is legally required. Previous versions are available on request.

14. Contact

Synthreo, Inc., Legal Department, 5227 N 7th St, Phoenix, AZ 85014-2802, United States.

The current policy is available at synthreo.ai/terms/privacy-policy.

Book a Demo

Your demo starts here

The first step is a brief discovery conversation to understand your business, goals, and AI priorities. From there, we’ll tailor the product demo to what matters most.

Pick a Time

Prefer email? sales@synthreo.ai

Contact

Talk to Synthreo

Tell us who you are and we will get back to you.

Prefer email? sales@synthreo.ai