Sub-processors
Last updated: 9 October 2026.
A sub-processor is a company we use to process personal data as part of running SPSync's website, licensing, support or the earlier hosted private preview. In every current edition of SPSync itself (desktop app, command line, In your Azure), your SharePoint data goes straight from Microsoft Graph to your own database. No SPSync-operated infrastructure or sub-processor sits in that path at all. The table below covers everything else: what we operate around the product, and, since we are switching several of these on as the business grows, exactly which ones are actually processing anything today rather than only planned to.
| Sub-processor | What for | Status today |
|---|---|---|
| Cloudflare | Hosting, CDN and DNS for spsync.io, and the form/event functions the site runs on | In use. Every visit to this site, and anything you submit through a form here, passes through Cloudflare's infrastructure. That covers visitor traffic (including IP addresses in server logs) and whatever a form collects. |
| HubSpot | Marketing email (newsletter, downloads, trial and demo requests) and, separately, support ticketing | Not yet. No HubSpot portal or form is configured, so a form submission on this site currently fails with "not configured yet" rather than reaching HubSpot (once a booking page is live, the demo request form is the exception: it skips straight to the booking page and stores nothing); a "Send diagnostics" ticket falls back to a locally-generated reference instead of a real HubSpot ticket. Once configured, marketing forms will send HubSpot what you submit (typically your work email, and for some forms your name, company name, phone number or use case), and diagnostics tickets will send it your message, contact email, customer name and the bundle's URL. |
| Microsoft Bookings | Scheduling a "book a call" demo | Not yet. There is no live scheduling page yet, so the "book a call" page shows no booking link and nothing can be booked through Microsoft Bookings today. Once there is one, it will collect the name, email and time you choose when booking. |
| Microsoft Azure | Storage for diagnostic bundles you send us; infrastructure for the earlier hosted private preview | Not yet. No Azure Storage account is connected, so a diagnostic bundle you send today is logged and discarded rather than uploaded and kept. The private preview has never had a live deployment either, so no existing tenant's SharePoint data is currently processed there. Once each is live: diagnostic bundles will be held in Azure Blob Storage as described in the privacy notice, and a deployed preview will process the SharePoint data its tenant chose to replicate. |
| Resend | Transactional email: customer-facing notifications (a failed run, a stalled schedule) for a hosted deployment, and, as a fallback if HubSpot ticketing is not configured, the "Send diagnostics" email-to-support route | Not yet. No Resend account is configured, so no notification or diagnostics-ticket email is currently sent through it (both fall back to being logged only). Once configured, it will send whichever recipient addresses you have set as notification recipients, or your contact email and message if you send diagnostics without HubSpot configured either. |
| Supabase | Control-plane database and sign-in for the private preview, and activation records for licensing (machines, and managed-application deployments in your Azure) | Not yet. This is unconfigured and the activation service is not deployed, so no preview sign-in, tenant metadata or licence-activation record currently reaches Supabase. Once live, it will hold private-preview tenant metadata and sign-in identity, and, for licensing, a one-way hash of your machine's hardware identifier plus hostname, OS and app version. The raw identifier is never held. |
SPSync in your Azure (the managed application offered to new
customers) runs inside your own Azure subscription and your list content and
credentials stay there. The one exception is licence activation: the worker calls
our licensing service at licensing.spsync.io when a container starts
without a cached activation (in practice each new replica or revision; periodic
refresh is not wired yet), sending either the licence key (BYOL) or its plan and
region, plus the Azure resource group id (which contains your subscription id),
subscription id, hostname, operating system and app version. The call succeeds only once the activation
service is live. That
record is stored in Supabase (listed above) and nothing from SharePoint or your
databases is included.
We will update the "status today" column on this page as each service above is actually switched on, rather than describing it as live in advance, and give reasonable notice before adding a new sub-processor to any of the processing activities above. See the data processing agreement for the roles and safeguards that apply to each one.