Last updated 27 October 2026
Subprocessors
The services that receive personal data when QuikSignal runs: what each one gets and why, where it processes it, and what its own terms say about data protection.
A processor handles the data on our instructions. An independent controller decides its own purposes under its own privacy terms. Rows marked as cookie-based run only with your consent where consent is required; see cookies. If you are a customer and want notice before a new supplier is added, ask us at sales@quiksync.com.
Vercel Inc.Processor
- Why:
- Hosting the website and application, running its functions, cookieless page counts
- What it receives:
- Everything the application processes passes through it
- Where:
- United States (functions run in Washington DC, iad1)
- Its terms:
- Data processing addendum incorporated into its terms for Pro plans, with the 2021 EU standard contractual clauses and the UK addendum
Neon (Databricks)Processor
- Why:
- The application database
- What it receives:
- Accounts, workspaces, research, billing records, logs held in the database
- Where:
- Region chosen when the database was created; confirmation pending
- Its terms:
- Databricks data processing addendum incorporated, with the 2021 standard contractual clauses and the UK IDTA
Microsoft (Microsoft 365, Entra ID)Processor
- Why:
- Staff sign-in and the email the service sends
- What it receives:
- Email addresses, names, message content
- Where:
- Microsoft datacentres; this tenant is outside the EU Data Boundary
- Its terms:
- Microsoft Products and Services Data Protection Addendum, which applies through its product terms
ResendProcessor
- Why:
- Backup email delivery
- What it receives:
- Email addresses and message content
- Where:
- United States
- Its terms:
- Data processing addendum binding on acceptance of its terms, with the 2021 standard contractual clauses and the UK addendum
New RelicProcessor
- Why:
- Application logs for fault finding
- What it receives:
- Request paths, error messages and internal identifiers; credentials are removed before sending
- Where:
- United States
- Its terms:
- Data processing addendum applies without signature; EU-US Data Privacy Framework and standard contractual clauses
CloudflareProcessor
- Why:
- DNS for the domain; AI inference (Workers AI)
- What it receives:
- Research text sent for analysis; connection metadata
- Where:
- Global network
- Its terms:
- Data processing addendum incorporated; states customer content is not used to train models
GroqProcessor
- Why:
- AI analysis of research text
- What it receives:
- Research text, questions asked in the product, company names
- Where:
- United States
- Its terms:
- Data processing addendum incorporated; inputs are not used for training unless permitted; logs kept up to 30 days
CerebrasProcessor
- Why:
- AI analysis of research text
- What it receives:
- Research text and questions
- Where:
- United States and other countries
- Its terms:
- Terms state inputs are not used for training or retained; no data processing addendum found on its site
Mistral AIProcessor
- Why:
- AI analysis of research text
- What it receives:
- Research text and questions
- Where:
- EU-based company; default endpoint not region-specific
- Its terms:
- Data processing addendum incorporated by reference
NVIDIA (API catalog)Processor
- Why:
- AI analysis of research text
- What it receives:
- Research text and questions
- Where:
- Not stated by the vendor
- Its terms:
- Trial terms only; no data processing addendum
Google (Gemini API)Processor
- Why:
- AI analysis of research text
- What it receives:
- Research text and questions
- Where:
- Any country Google operates in
- Its terms:
- Google terms for the Gemini API
Z.ai (GLM models)Processor
- Why:
- AI analysis of research text
- What it receives:
- Research text and questions
- Where:
- Singapore, per its API data processing addendum
- Its terms:
- API terms: content is not used to improve the service without the customer's agreement; its API data processing addendum says content is not stored
SambaNova CloudProcessor
- Why:
- AI analysis of research text
- What it receives:
- Research text and questions
- Where:
- United States-based company; region not yet confirmed
- Its terms:
- Vendor terms under review; no data processing addendum confirmed
OmniRoute relayProcessor
- Why:
- Routing AI requests to further model providers when the ones above are busy
- What it receives:
- Research text and questions
- Where:
- Depends on the provider each request is routed to
- Its terms:
- Open-source relay; the terms are those of whichever provider answers
Google (sign-in)Independent controller
- Why:
- Signing in with a Google account, when a person chooses it
- What it receives:
- Name and email address of the Google account
- Where:
- United States
- Its terms:
- Google API Services User Data Policy
Google (Analytics 4)Processor · with consent
- Why:
- Measuring use of the website
- What it receives:
- Pages visited, device and approximate location, an analytics cookie
- Where:
- United States
- Its terms:
- Google Ads Data Processing Terms
Google (Ads conversion tracking)Independent controller · with consent
- Why:
- Measuring which of our ads led to a visit or purchase
- What it receives:
- Page visits from an ad, an advertising cookie, conversion events
- Where:
- United States
- Its terms:
- Google Ads Controller-Controller Data Protection Terms
Meta Platforms IrelandJoint controller (collection) · with consent
- Why:
- Measuring which of our Facebook and Instagram ads led to a visit or purchase
- What it receives:
- Page views, a started checkout, a completed purchase and its amount, an advertising cookie
- Where:
- Ireland and the United States
- Its terms:
- Meta Business Tools Terms, with its controller addendum and data processing terms
Dodo PaymentsIndependent controller
- Why:
- Taking card payments as merchant of record
- What it receives:
- Name, email, billing address, payment details
- Where:
- Card data held on AWS Mumbai
- Its terms:
- Its data processing addendum; acts as an independent controller for payment data
RazorpayIndependent controller
- Why:
- Taking payments in India
- What it receives:
- Name, email, phone, payment details
- Where:
- India
- Its terms:
- Regulated payment aggregator under its own privacy policy
These descriptions summarise each supplier’s own pages as read on 27 October 2026. They are not a statement that any supplier has signed an agreement with us beyond its standard terms.
Who you are contracting with
QuikSync Technologies LLP
GSTIN 27AABFQ0276D1ZJ
LLPIN ABA-5228
020 4123 9608 · 9:00 am - 6:00 pm IST
support@quiksync.com · sales@quiksync.com
Grievance officer
QuikSync Technologies LLP
grievance@hello.quiksynctech.com · +91 70301 31139
Reachable 9:00 am - 6:00 pm IST. Email arrives at any hour and is answered in that window.
Write to them about anything this service did with your data, a charge you did not expect, or content you believe should not be here. Name the workspace and the date and you will get a reply from a person.
When support is open
| APAC | 9:00 am - 6:00 pm | IST |
|---|---|---|
| Europe | 9:00 am - 6:00 pm | CET/CEST |
| USA | 9:00 am - 6:00 pm | ET/PT |
| Global · critical | 24×5 | Follow-the-sun |
Anything that stops the workspace working, on any plan. support@quiksync.com or 020 4123 9608.
See also Terms of Service, Privacy Policy, Refund & Cancellation.