Syntic
Regional Compliance

Global ambition. Local responsibility.

Syntic is building for a global economy. We approach privacy, security and regulation with the ambition to serve businesses across borders, and the discipline to assess what each jurisdiction requires. Explore the frameworks that matter to your market, then talk to us about today's capabilities and tomorrow's roadmap.

How it works

Global vision. Jurisdiction-specific diligence.

Three questions guide every regional discussion: where data is handled, which obligations apply, and which legal entity contracts with the customer. Availability and safeguards are confirmed for each engagement.

Layer 01

Data residency

Where your data is stored and processed. Data residency and deployment requirements are scoped with our team as part of your engagement. Tell us what your jurisdiction requires, and we will tell you plainly what we can support today.

Layer 02

Regulatory framework alignment

Which laws and frameworks apply to your deployment. HIPAA for US healthcare, GDPR for the EU, UK GDPR and DPA 2018, PIPEDA in Canada, DPDP Act in India, Privacy Act in Australia, and LGPD in Brazil, plus industry-specific frameworks like FDCPA, GLBA, FERPA, PCI DSS, and SR 11-7. Requirements are scoped per engagement. SOC 2 Type I, SOC 2 Type II and ISO 27001 are planned milestones, not completed assessments. No FedRAMP authorization is claimed.

Layer 03

Contracting entity

Which Syntic legal entity holds your contract and processes your data under it. Different jurisdictions require different contracting structures — local data processor, local controller, joint-controller arrangements, intra-group data transfer agreements, and local incorporation requirements. We adapt the contracting structure to your jurisdiction's requirements, not the other way around. Where we don't yet have a local entity, we partner with established local entities for contracting, billing, and data handling. The current entity structure is in the Contracting section below.

Compliance by region

Understanding the world's regulatory landscapes.

If your jurisdiction isn't listed, contact privacy@syntic.ai and we'll tell you plainly what we can support today.

United States and Canada

Federal frameworks

  • HIPAA (healthcare): Syntic does not currently offer a Business Associate Agreement (BAA). Customers must not submit, upload, or process protected health information (PHI) subject to HIPAA through Syntic services.
  • GLBA (financial services), supporting controls scoped per engagement
  • FERPA (education), supporting controls available
  • FDCPA (collections), built into the Vertical AI Collections Employee
  • TCPA (telecommunications), built into AI Call Center voice and SMS
  • CAN-SPAM (email marketing), built into outbound email workflows
  • COPPA (children's privacy), supporting controls for K-12 education

State frameworks

  • CCPA and CPRA (California)
  • CDPA (Virginia), CPA (Colorado), UCPA (Utah), CTDPA (Connecticut), and equivalent emerging state privacy laws
  • State telemedicine and telehealth regulations supported

Procurement vehicles

  • GSA Multiple Award Schedule (not currently held)
  • SEWP, ITES, CIO-SP3, OASIS+ partnership paths
  • State and local NASPO ValuePoint, GovBuy, regional cooperatives
  • Subcontracting and teaming with established primes available

Canada

  • PIPEDA federal compliance
  • Provincial frameworks PHIPA (Ontario), Act respecting Health Services (Quebec), HIA (Alberta)
  • English and French requirements assessed per engagement

European Union and United Kingdom

EU framework

  • GDPR, DPA requirements subject to contractual review
  • Standard Contractual Clauses (SCC 2021 module 2) for cross-border transfers
  • EU representative requirements under Article 27, where applicable
  • Schrems II analysis documented per customer engagement
  • ePrivacy Directive alignment for electronic communications
  • AI Act compliance scoping in progress, with enforcement timelines aligned to phase-in dates

UK framework

  • UK GDPR and Data Protection Act 2018
  • UK representative requirements, where applicable
  • International Data Transfer Agreement (IDTA) for non-UK transfers
  • ICO registration requirements, where applicable

Member state frameworks

  • Netherlands NEN 7510 for healthcare
  • Spain ENS (Esquema Nacional de Seguridad) for public sector
  • Italy AgID Cloud Marketplace alignment

Public sector

  • EU NEGOMETRO and member state procurement frameworks
  • ENISA framework alignment

Industry-specific

  • DORA (Digital Operational Resilience Act) for financial services
  • NIS2 Directive for essential and important entities
  • MDR (Medical Device Regulation), noting Syntic is not a medical device and maintains clinician-in-the-loop framing

Asia-Pacific

Australia

  • Privacy Act 1988 and Australian Privacy Principles
  • My Health Records Act for healthcare
  • ISM (Information Security Manual) alignment

Japan

  • APPI (Act on the Protection of Personal Information)
  • Healthcare data handling under MHLW guidance

Singapore

  • PDPA (Personal Data Protection Act)
  • Banking Cybersecurity Guidelines (MAS TRM)
  • Healthcare data under the PDPA Healthcare Sector Advisory

South Korea

  • PIPA (Personal Information Protection Act)

India

  • DPDP Act 2023
  • IT Act 2000 and SPDI Rules
  • MeitY framework alignment for government
  • RBI data localization for regulated financial services
  • HIS (Health Information Standards) for healthcare engagements

Hong Kong

  • PDPO (Personal Data Privacy Ordinance)
  • HKMA cybersecurity guidelines for financial services

China (Mainland)

  • Syntic does not currently offer direct commercial services in mainland China. Customers with operations in China can contact privacy@syntic.ai to discuss their requirements.

Middle East and Africa

United Arab Emirates

  • UAE Federal Data Protection Law (PDPL)
  • ADGM Data Protection Regulations
  • DIFC Data Protection Law
  • TEJARI procurement vehicle for government engagements
  • Arabic-language requirements assessed per engagement

Saudi Arabia

  • PDPL (Personal Data Protection Law)
  • SDAIA framework alignment
  • NCA Essential Cybersecurity Controls
  • Arabic-language requirements assessed per engagement

Israel

  • Privacy Protection Law and Regulations

South Africa

  • POPIA (Protection of Personal Information Act)

Egypt, Kenya, Nigeria, Morocco

  • Local privacy framework alignment per engagement

Latin America

Brazil

  • LGPD
  • ANPD registration requirements, where applicable
  • Brazilian healthcare data under CFM guidance
  • Portuguese-language requirements assessed per engagement

Mexico

  • LFPDPPP
  • LGPDPPSO for public sector
  • Spanish-language requirements assessed per engagement

Argentina, Colombia, Chile, Peru

  • Local privacy framework alignment per engagement
  • EU adequacy decisions recognized where applicable

Honduras and Central America

  • Local privacy framework alignment per engagement
  • Spanish-language requirements assessed per engagement
Industry-specific frameworks

The regulatory requirements that follow your industry across every jurisdiction you operate in.

The following frameworks help shape our discussions with regulated organizations. Their inclusion does not mean Syntic is certified, authorized or compliant with every requirement listed.

Healthcare

  • HIPAA US, GDPR special category data EU, PHIPA Ontario, DPDP healthcare India, MHLW guidance Japan, Privacy Act health Australia, POPIA health South Africa
  • Data Processing Agreements (DPAs) are available where applicable. Syntic does not currently offer a Business Associate Agreement (BAA) or equivalent healthcare-specific data processing agreement.
  • 42 CFR Part 2 for substance use disorder treatment data in the US
  • Clinician-in-the-loop framing enforced, Syntic not marketed as a medical device

Financial services

  • SR 11-7 US Federal Reserve
  • PRA SS1/23 UK
  • BaFin MaRisk Germany
  • MAS Technology Risk Management Singapore
  • APRA CPS 234 Australia
  • OSFI guideline E-23 Canada
  • RBI master directions India
  • DORA EU

Collections and recovery

  • FDCPA US federal
  • State-level fair debt collection acts
  • FCA CONC UK
  • Australian Consumer Law Schedule 2
  • EU Consumer Credit Directive
  • All built into the Vertical AI Collections Employee

Public sector cross-region

  • FedRAMP, DoD IL, CJIS, StateRAMP US
  • NCSC, G-Cloud, OFFICIAL UK
  • C5, SecNumCloud, ENS EU member states
  • IRAP, ISMAP, MTCS, K-ISMS, MeitY APAC

Education

  • FERPA US
  • GDPR education sector guidance EU
  • UK GDPR education provisions
  • DPDP educational data India
  • Provincial education privacy frameworks Canada

Payment processing

  • PCI DSS scoped per engagement
  • PSD2 EU and Open Banking
  • RBI payment system guidelines India
  • MAS PSN02 Singapore
Data transfer and cross-border

When your data needs to cross a jurisdiction boundary.

Cross-border processing requires a clear understanding of data flows, applicable law and contractual safeguards. No particular residency arrangement is guaranteed without review.

Map the data flows

  • Identify where customer information is stored, processed and accessed, including relevant service providers.

Review legal requirements

  • Assess applicable privacy and sector-specific obligations.
  • Determine whether cross-border transfer restrictions apply.

Agree appropriate safeguards

  • Review relevant contractual mechanisms and available deployment options.
  • Confirm any residency commitments before use.

Respond responsibly

  • Government and law-enforcement requests are evaluated under applicable law.
  • Customer notification depends on legal and contractual obligations.
Contracting and entity structure

A global company. Clear contracting arrangements.

The legal contracting party and any regional arrangements are confirmed in the applicable customer agreement.

Syntic AI, Inc. (Delaware, USA)US-incorporated company. The contracting party for each customer is identified in the applicable agreement.
Regional arrangementsAny additional entity, local partner or jurisdiction-specific contracting structure must be confirmed individually. No unverified subsidiary is represented as operational.
For procurement and legal teams

Built for serious procurement conversations.

Talk with our team about available documentation, contractual requirements and the diligence appropriate to your deployment.

Standard documentation
  • Region-specific Data Processing Agreement
  • Standard Contractual Clauses and UK IDTA
  • Country-specific privacy law addendums
  • Subprocessor list with regional breakdown
  • Data flow diagrams per region
  • Schrems II transfer impact assessment template
Under NDA
  • Region-specific security pack
  • Compliance gap analysis versus local frameworks
  • Customer-specific compliance scoping documents
  • Regional incident response procedures
On Business and Enterprise
  • Live calls with our compliance team
  • Custom regional compliance scoping
  • Validation evidence packages per jurisdiction
  • Region-specific service level agreements
Request a region-specific compliance pack
Frequently asked questions

The questions procurement, legal, and security teams ask.

Data residency, regulator requests, and emerging AI frameworks.

How do I select my deployment region?

Talk to our team about your data residency and deployment requirements. We will tell you plainly what we can support today and what is not yet available.

What happens if a regulator requests my data?

We require proper legal process — a court order, subpoena, or equivalent legal instrument in the relevant jurisdiction — before complying with any government or law enforcement request for customer data. We do not voluntarily disclose customer data to any authority. Where the law permits us to notify the customer before complying, we do so. Where we cannot notify, we log the request. We publish aggregate government request counts in our annual transparency report. If you receive notice of a legal process requiring your data from Syntic, contact privacy@syntic.ai immediately.

What if my region isn't listed?

Contact privacy@syntic.ai with your jurisdiction. If we can support your jurisdiction today, we'll tell you that. If we can't yet, we'll tell you that honestly and give you a realistic timeline.

How do you handle the AI Act in the EU?

Syntic AI is scoping compliance with the EU AI Act aligned to its phase-in timeline. The AI Act classifies AI systems by risk category — the majority of Syntic's use cases fall in the limited or minimal risk categories. Where Syntic deployments touch higher-risk categories — certain HR use cases, some public sector deployments, and some healthcare applications — we are documenting conformity requirements and will publish our approach as the relevant provisions enter force. Our clinician-in-the-loop framing for healthcare and our human-in-the-loop platform controls for high-stakes decisions are designed to be consistent with the Act's requirements for human oversight. Contact privacy@syntic.ai for EU AI Act scoping on your specific deployment.

Do you support sovereign AI for non-US governments?

Talk to our team about deployment requirements. Government and regulated-industry engagements are scoped individually, and we will tell you plainly what we can support today.

What about emerging frameworks like Canada AIDA, the EU AI Act, and the US AI Executive Order?

We monitor regulatory developments in the jurisdictions we serve and update our compliance posture as frameworks finalize. Customer-facing changes are communicated 30 days in advance for Business and Enterprise.

What if I have a custom regulatory requirement?

Most regulatory requirements are scopable into our existing framework. Contact privacy@syntic.ai with your specific framework and we'll assess fit and propose a path.

Get in touch

Building for the world. Starting with your requirements.

Every compliance engagement starts with a conversation. Tell us where you operate, what industry you're in, and what frameworks your procurement or legal team requires. We will scope what we have today, what's in progress, and what we'd need to build for your specific deployment.

Compliance questions
privacy@syntic.ai
Data subject rights
privacy@syntic.ai
Government and public sector
sales@syntic.ai
Legal and contract questions
privacy@syntic.ai
Response time
Share your requirements and timeline. Our team will review your request and discuss next steps.