Skip to content

Trust centre

Subprocessors

Last updated

Bizisy is operated by Wisely Lda (NIPC 516845128), Rua de S. Pedro 12A, 4720-092 Amares, Portugal. As the processor of the HR data our customers put into Bizisy, Wisely Lda uses the subprocessors below. This list is the one our privacy policy and Annex III of our data processing agreement print: they come from one register in our code.

Before a new subprocessor handles customer personal data, we update this page and email each organization’s owners at least 30 days in advance. An organization can object on reasonable data protection grounds within that time, as the data processing agreement describes.

1. Subprocessors

They handle customer personal data for us while we provide Bizisy.

Subprocessors
ProviderWhat forWhere
Google Cloud (Google)Cloud Run (our application servers), Firestore (our database, where all Bizisy data is stored), Cloud Storage (profile photos, company logos, documents and the CVs candidates send) and Document AI (reads the text of bank account proofs, for organizations with Verified bank details, of CVs sent as pictures, for organizations that use Hiring, and of the policies and contracts HR adds to Renewals from a document; nothing is kept by Google)europe-west1, Belgium (EU); Document AI in the EU multi-region
Google Identity Platform (Google)Sign-in: passwords, Google and Microsoft sign-in, in one sign-in tenant per organization and separate tenants for developer accounts and for partner accounts (the people of partner firms)Google’s global infrastructure
Google Cloud Secret Manager, Cloud Logging, Cloud Monitoring, Cloud Scheduler (Google)Service credentials (no personal data), server logs, alerts to us about failed background jobs (no personal data), scheduled jobsGoogle’s infrastructure
CloudflareDNS, content delivery, edge routing and security, and forwarding of email sent to our @bizisy.com addressesCloudflare’s global network
Resend (a US company)Sends Bizisy’s transactional emaileu-west-1, Ireland (EU)

2. Providers for Bizisy’s own operations and billing

They serve our website and app files, or handle our own billing (for which we are the controller). They are not subprocessors of your HR data.

Providers for Bizisy’s own operations and billing
ProviderWhat forWhere
Firebase Hosting (Google)Serves the files of the web app, the developer site and the partner consoleGoogle’s global network
Google Fonts (Google)Serves the Geist typeface the Bizisy app uses (on your organization’s address); your browser fetches it from Google. The bizisy.com website serves its own fonts.Google’s global network
Stripe (Stripe Payments Europe, Ireland)Takes payments, by a saved card or on its invoice payment page, and keeps the payment method when an owner or admin saves one. For fraud prevention and its legal and regulatory duties Stripe also acts as an independent controller, under its own privacy policyEU, with transfers to Stripe, Inc. in the United States
VIES (European Commission)Checks that an EU VAT number is valid (the VAT number only); a separate recipient, not our processorEU
Moloni (Portugal)Issues certified invoices (faturas) with the billing details, as Portuguese tax law requiresPortugal (EU)

3. Tools your organization connects

These receive data only when your organization connects them. Each is your organization’s own tool, under its agreement with that provider: a recipient your organization chooses, not our subprocessor.

Tools your organization connects
ProviderWhat forWhere
TalentLMS, 360Learning, Docebo or the organization’s own Moodle, only when an organization connects themReceive learner accounts (name, work email and, where the platform has them, job title, manager and team groups) and course enrolments, and tell Bizisy who completed a course. Each is the organization’s own tool, under its agreement with that provider: a recipient chosen by the organization, not our processorWhere the organization’s platform keeps its data
Atlassian (Jira, Jira Service Management), Linear and Asana, only when an organization connects themReceive the checklist tasks the organization chose to have done there (title, details, due date, labels, and the public and job details of the person the template names) and are asked which user has a work email, to assign them. Each is the organization’s own tool, under its agreement with that provider: a recipient chosen by the organization, not our processorWhere the organization’s Atlassian site, Linear workspace or Asana workspace keeps its data
Xero, Exact Online, Holded, Odoo and Moloni ON, only when an organization connects oneReceive the names of the organization’s teams, and when the organization turns them on, people’s names and work emails as suppliers and the monthly pay totals per team it approved. Each is the organization’s own accounting tool, under its agreement with that provider: a recipient chosen by the organization, not our processorWhere the organization’s account with that tool keeps its data
Slack (Salesforce) and Microsoft Teams (Microsoft), only when an organization connects themReceive the announcements the organization chose (name, job title, team, manager) in the organization’s own Slack workspace or Teams channel; Slack is also asked which member has a person’s work email, to mention them. Each is the organization’s own tool, under its agreement with that provider: a recipient chosen by the organization, not our processorWhere the organization’s Slack workspace or Microsoft 365 tenant keeps its data
Google Chat (Google), Mattermost, Discord and Rocket.Chat, only when an organization connects themReceive the announcements the organization chose (name, job title, team, manager) at the webhook the organization created in its own Google Chat space or Mattermost, Discord or Rocket.Chat channel; nothing else is sent to them. Each is the organization’s own tool, under its agreement with that provider (or on its own server, for self-hosted Mattermost and Rocket.Chat): a recipient chosen by the organization, not our processorWhere the organization’s Google Workspace, Discord server or Mattermost or Rocket.Chat server keeps its data
Google Calendar (Google Ireland) and Outlook Calendar (Microsoft Ireland), only when an organization connects oneReceive the invitations for a new hire’s first-day meetings (and, if turned on, onboarding task due dates): meeting title, the hire’s name, time, the organization’s note, and the invited people’s names and work email addresses, on the organization’s own calendar account. Each is the organization’s own tool, under its agreement with that provider: a recipient chosen by the organization, not our processorWhere the organization’s Google Workspace or Microsoft 365 account keeps its data
Staffology (IRIS Software Group), Xero Payroll (Xero Limited) or Silae (Silae SAS), only when an organization connects its own account and sends a locked pay periodReceive what HR reviewed and sent: employees’ names, contact and payroll details, pay and variable pay (Silae: variable pay only). The organization’s own payroll tool, under its agreement with that provider (the organization’s processor, not ours)United Kingdom (Staffology), Xero’s hosting (Xero Payroll), EU (France, Silae)
Yousign (Yousign SAS, now Youtrust), only when an organization connects its own accountReceives the documents HR sends for signature and each signer’s name, email address, language and, for advanced or qualified signatures, phone number; sends back the signed copy, the audit trail and status updates. The organization’s own e-signature provider, under its agreement with Yousign (the organization’s processor, not ours)EU (France)
Pleo, Moss (Nufin GmbH), Payhawk and Spendesk, only when an organization connects themReceive what the organization’s spend management sync sends (names, work email, team, team lead as approver, card blocks for leavers, as each tool’s API allows), and answer Bizisy’s reads of their people and teams. Each is the organization’s own tool, under its agreement with that provider: a recipient chosen by the organization, not our processorWhere each tool keeps the organization’s data
Segurança Social (Instituto da Segurança Social, Portugal), only when an organization enters its access and HR sends a noticeReceives the hire and leave notices HR confirms for the organization’s Portuguese legal entities, as the law requires of the employer; a public authority and separate recipient, not our processorPortugal (EU)
Nmbrs (Visma Nmbrs) and Loket.nl, only when an organization connects themReceive the joiners, changes and leavers of the legal entity the organization chose (pay never). Each is the organization’s own payroll tool, under its agreement with that provider: a recipient chosen by the organization, not our processorWhere the organization’s payroll tool keeps its data
Okta, Teamtailor and Greenhouse, only when an organization connects themOkta receives the accounts the organization keeps in step with HR (name, work email, job title, team, manager, groups, whether the account is active or suspended); Bizisy reads from Teamtailor or Greenhouse the candidates hired there (name, own email, job title, department, start date). Each is the organization’s own tool, under its agreement with that provider: a recipient or source chosen by the organization, not our processorWhere the organization’s Okta, Teamtailor or Greenhouse account keeps its data
Jamf Pro (Jamf), Microsoft Intune (Microsoft), Kandji and Workwize, only when an organization connects themBizisy reads the organization’s devices or equipment from its own tool (device details, and the name and email of the user the tool lists); nothing about people is sent to them. Each is the organization’s own tool, under its agreement with that provider: a source chosen by the organization, not our processorWhere the organization’s tool keeps its data
DocuSign (DocuSign, Inc. and its affiliates), Dropbox Sign (Dropbox, Inc.), Signaturit (Signaturit Solutions, S.L., a Namirial company) and Skribble (Skribble AG or Skribble Deutschland GmbH), only when an organization connects its own accountReceive the documents HR sends for signature and each signer’s name, email address, language and, where the chosen level needs a code by SMS, phone number; send back the signed copy, the audit trail and status updates. The organization’s own e-signature provider, under its agreement with that provider (the organization’s processor, not ours)Where the organization’s account with that provider keeps its data (for example DocuSign’s EU environment, Signaturit in Spain, Skribble in Switzerland or Germany)

4. Transfers outside the EEA

Where a provider processes personal data outside the European Economic Area, the transfer is covered by the European Commission’s Standard Contractual Clauses included in that provider’s data processing terms, or, for providers certified under it, by the EU-U.S. Data Privacy Framework.

Questions about this list: privacy@bizisy.com.

Questions? Write to privacy@bizisy.com about privacy, or hello@bizisy.com about anything else.