Data Processing Addendum

In plain English

• You (the customer) decide why and how the personal data in Pulseri is used. We process it for you, only on your instructions.
• We keep it secure and confidential. If there is a breach, we tell you without undue delay and no later than 72 hours after we become aware of it.
• We store it with Google Cloud in Belgium. Our team works from the UAE, and some of our providers are in the US.
• Because Pulseri is a UAE company, the EU Standard Contractual Clauses are built in. The UK and Swiss versions are built in too.
• We use sub-processors, listed on our sub-processors page. We tell you 30 days before adding or replacing one. You can object to a new one, and if we cannot resolve your objection you can cancel.
• AI tags comments and writes weekly summaries on every plan. We remove email addresses and some phone numbers first, and neither we nor our AI provider train AI models on your data.
• We do not sell your data. Where US state privacy laws apply, we act as your service provider.
• We help you answer requests from the people whose data you hold.
• When your account ends, you can read your data for at least 90 days. Then we delete it.
• You can check that we keep these promises: we answer your reasonable questions, fill in security questionnaires for Business and Enterprise customers, and you can audit us once a year by document review.
• This addendum applies automatically when you accept the Terms of Service. Enterprise customers can ask for a signed copy.

This summary helps you read the addendum. The numbered sections and the annexes below are the agreement.

1. Scope and parties

1.1 This Data Processing Addendum (the "DPA") is part of the agreement between STAFFINGG L.L.C-FZ, a company registered in the Meydan Free Zone, Dubai, United Arab Emirates, with its registered address at Meydan Grandstand, 6th floor, Meydan Road, Nad Al Sheba, Dubai, United Arab Emirates ("Pulseri"), and the customer that accepted the Terms of Service or signed an Order Form (the "Customer"). It applies when Pulseri processes Customer Personal Data to provide the Service.

1.2 The Customer is the controller of Customer Personal Data and Pulseri is its processor. If the Customer itself processes the data for another business, as that business's processor, then Pulseri is the Customer's sub-processor. In that case the Customer confirms that it has the right to give the instructions in this DPA and to agree to it.

1.3 Definitions. Words defined in the Terms of Service (for example Customer Data, People, Team Members, Service and Order Form) have the same meaning here. In this DPA: (a) "Data Protection Law" means all data protection law that applies to the processing, including the EU General Data Protection Regulation (Regulation (EU) 2016/679, the "GDPR"), the UK GDPR and the UK Data Protection Act 2018, the Swiss Federal Act on Data Protection, UAE Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (the "PDPL"), the California Consumer Privacy Act (the "CCPA") and similar US state privacy laws, each as amended; (b) "Customer Personal Data" means the personal data in Customer Data that Pulseri processes for the Customer; (c) "Sub-processor" means a provider that Pulseri uses to process Customer Personal Data; (d) "SCCs" means the EU Standard Contractual Clauses for transfers of personal data to countries outside the EU (Commission Implementing Decision (EU) 2021/914); (e) "controller", "processor", "personal data", "data subject", "personal data breach", "processing" and "supervisory authority" have the meaning they have in the GDPR. A "data subject" is the person the data is about.

1.4 What this DPA does not cover. Pulseri is a controller, not a processor, for account, billing, website and sign-in security data about the Customer's organisation and its Team Members. The Privacy Policy covers that data, and this DPA does not apply to it. The account's audit log is different: Pulseri keeps it for the Customer, under this DPA, and the Customer sets how long it is kept.

2. How Pulseri processes Customer Personal Data

2.1 The subject matter, duration, nature and purpose of the processing, the types of personal data, the data subjects and the retention periods are set out in Annex 1.

2.2 Only on instructions. Pulseri processes Customer Personal Data only: (a) to provide, secure and support the Service, in line with the Terms of Service, this DPA and the Customer's documented instructions; or (b) where EU, EU Member State or UK law requires it, or where other law that applies to Pulseri (including UAE law) requires it. For data covered by the SCCs, processing under other law is limited to what the SCCs allow: law that respects the essence of fundamental rights and freedoms and does not go beyond what is necessary and proportionate in a democratic society. In case (b), Pulseri tells the Customer first, unless the law forbids that.

2.3 Instructions. The Terms of Service, this DPA and the Customer's use of the Service's features and settings are the Customer's complete instructions. Further instructions must be reasonable and in writing. If Pulseri thinks an instruction breaks Data Protection Law, it will tell the Customer straight away and may pause that instruction until it is changed.

2.4 The Customer's duties. The Customer is responsible for: (a) having a lawful basis to collect Customer Personal Data and use it in the Service; (b) giving data subjects the notices that Data Protection Law requires, and getting any consent it requires (for example to send survey emails); (c) the accuracy and quality of the data; and (d) choosing the Service settings that match its legal duties, for example the audit log retention period and when to delete People.

2.5 AI processing. On every plan, the Service sends the text of written survey answers to an AI provider to tag them by sentiment and theme and to write weekly summaries. AI is part of the Service and cannot be switched off for an account. Before text is sent, Pulseri removes email addresses and some phone number formats from the copy that is sent. This will not catch everything: names and other personal details in comments can still reach the provider. The stored original is not changed. The AI provider is a Sub-processor listed in Annex 3, and its terms do not allow it to use the data Pulseri sends it to train its models. Pulseri does not use Customer Data to train AI models.

2.6 Usage counts. Pulseri may use counts about how the Service is used (for example the number of surveys sent and which features are used) to run, secure and improve the Service. These counts do not identify the Customer or any individual and are not Customer Personal Data.

3. Confidentiality

Pulseri makes sure that everyone it allows to process Customer Personal Data is bound by a duty of confidentiality. It gives access only to people who need it.

4. Security

4.1 Pulseri uses appropriate technical and organisational measures to protect Customer Personal Data against accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access. The measures at the date of this DPA are in Annex 2. They are also summarised on the Security page.

4.2 Pulseri may change the measures, as long as the overall level of protection does not go down.

4.3 The Customer is responsible for the security settings under its control, such as its Team Members' roles, sign-in methods and API keys.

5. Sub-processors

5.1 General authorisation. The Customer agrees that Pulseri may use Sub-processors. The Sub-processors in use are listed in Annex 3.

5.2 Their duties. Pulseri has a written contract with each Sub-processor that gives Customer Personal Data at least the same protection as this DPA. Pulseri stays responsible to the Customer for its Sub-processors' performance of those duties.

5.3 Notice of changes. Pulseri gives at least 30 days' notice before a new or replacement Sub-processor starts to process Customer Personal Data. It does so by updating Annex 3 and emailing the Customer's account owners. Anyone who wants these notices at another address can ask at [email protected].

5.4 Objection. The Customer may object to a new or replacement Sub-processor on reasonable data protection grounds by writing to [email protected] within 30 days after the notice. The parties will then try in good faith to resolve the objection. If it is not resolved by the date the new Sub-processor is due to start, the Customer may cancel the Service as set out in the Terms of Service. Fees already paid are not refunded. Because the Service runs on one shared platform, Pulseri cannot keep a single customer's data away from a Sub-processor that the platform uses; cancelling is the remedy.

5.5 Urgent replacement. If a Sub-processor must be replaced urgently for security or service-continuity reasons, Pulseri may do so before the 30 days end. It tells the Customer as soon as it can, and the objection right in 5.4 still applies.

5.6 Copies of contracts. On request, Pulseri gives the Customer a copy of its data protection terms with a Sub-processor. It may remove commercial terms and confidential information first.

5.7 Not Sub-processors. Two kinds of provider are not Sub-processors under this DPA: (a) integrations the Customer chooses to connect (for example Slack, Microsoft Teams, Zendesk, the Customer's own Stripe account, the identity provider it uses for single sign-on, or an AI assistant app it connects). The Customer instructs Pulseri to exchange data with them, and the Customer's own terms with them apply; and (b) providers that Pulseri uses for its own business as a controller (for example to take payments from the Customer). They are listed separately on the sub-processors page, and the Privacy Policy covers them.

6. International transfers

6.1 Where data is processed. Pulseri is a company established in the United Arab Emirates. It stores Customer Personal Data with Google Cloud in Belgium (EU). Pulseri's team accesses it from the UAE. Sub-processors process it in the countries listed in Annex 3, which include the United States.

6.2 EU Standard Contractual Clauses. Where the Customer's processing of Customer Personal Data is subject to the GDPR, the parties enter into the SCCs, which are incorporated into this DPA by reference. Because Pulseri is established outside the EU, the SCCs apply to every transfer of that data to Pulseri, including when Pulseri's team accesses data stored in the EU from the UAE. Pulseri's onward transfers to Sub-processors follow section 6.5. The parties make these choices: (a) Modules. Module Two (controller to processor) applies where the Customer is a controller. Module Three (processor to processor) applies where the Customer is a processor. The Customer is the "data exporter" and Pulseri is the "data importer". (b) Clause 7 (the docking clause, which lets other parties join) applies. (c) Clause 9(a): Option 2 (general written authorisation) applies, with the 30-day notice period in section 5.3. (d) Clause 11(a): the optional wording does not apply. (e) Clause 13 (supervisory authority): where the Customer is established in an EU Member State, the competent supervisory authority is the one responsible for the Customer there. Where the Customer is not established in the EU but has appointed a representative under Article 27 of the GDPR, it is the authority of the Member State where that representative is established. Where the Customer does not have to appoint a representative, it is the authority of the Member State where the data subjects concerned are located, as Clause 13(a) provides. (f) Clause 17: Option 1 applies, and the SCCs are governed by the law of Ireland. Clause 18(b): disputes go to the courts of Ireland. (g) Annexes: Annex I of the SCCs is Annex 1 of this DPA, Annex II is Annex 2, and the Sub-processor list in Annex 3 is given for information under Option 2. (h) How some clauses work in practice: audits under Clause 8.9 are carried out as section 11 sets out; Pulseri confirms deletion in writing on request (Clause 8.5); and the Customer's acceptance of the Terms of Service, or its signature of an Order Form, counts as its signature of the SCCs, including Annex I.A. (i) If the SCCs conflict with this DPA or any other part of the agreement, the SCCs win. (j) If an adequacy decision or another lawful transfer tool later covers a transfer, the SCCs stop applying to that transfer to that extent.

6.3 UK. Where the Customer's processing is subject to the UK GDPR, the parties also enter into the UK International Data Transfer Addendum to the SCCs (version B1.0, issued by the Information Commissioner under section 119A of the Data Protection Act 2018). Its Table 1 is completed from Annex 1, Table 2 from the choices in section 6.2, and Table 3 from Annexes 1 to 3. For Table 4, either party may end the Addendum as its Section 19 allows. The competent supervisory authority for UK data is the Information Commissioner's Office.

6.4 Switzerland. Where the processing is subject to the Swiss Federal Act on Data Protection, the SCCs apply with these changes: references to the GDPR mean that Act; the Federal Data Protection and Information Commissioner is the competent supervisory authority for those transfers; "Member State" in Clause 18(c) includes Switzerland, so data subjects in Switzerland can bring claims where they normally live; and where a transfer is subject only to the Swiss Act, Clause 17 refers to Swiss law and Clause 18(b) to the Swiss courts.

6.5 Onward transfers to Sub-processors. For each Sub-processor that processes Customer Personal Data outside the EU, the UK or Switzerland, Pulseri uses a valid transfer tool: the SCCs (Module Three, with the UK and Swiss versions where needed), an adequacy decision (including the EU-US Data Privacy Framework for certified providers), or another tool Data Protection Law allows. Annex 3 lists the safeguard for each.

6.6 Government requests and local laws. For data covered by the SCCs: (a) Pulseri tells the Customer about any request or order from a public authority for Customer Personal Data, unless the law forbids it; challenges it where there are reasonable grounds; and discloses only the minimum the request requires (Clause 15); and (b) as Clause 14 requires, Pulseri assesses the laws and practices of the UAE and the other countries involved, documents that assessment, gives the Customer a summary on request, and tells the Customer if its view changes.

6.7 If a transfer tool stops working. If a court or authority rules that a transfer tool used under this section is invalid, the parties will work together to put a valid one in place.

7. Help with data subject requests

7.1 Tools. The Service lets the Customer find, read, correct and delete Customer Personal Data, through the dashboard, the API and the assistant (MCP) connection. The Customer is responsible for using them. Single survey answers cannot yet be deleted in the Service; Pulseri deletes or redacts them on request at [email protected].

7.2 Requests that reach Pulseri. If a data subject contacts Pulseri about Customer Personal Data, Pulseri will not answer the request itself, except to tell the person to contact the Customer. It will pass the request to the Customer without undue delay, unless the law requires otherwise.

7.3 Further help. Taking into account the nature of the processing, Pulseri gives the Customer reasonable help to answer requests that the Customer cannot answer with the tools in the Service. Help with deleting or redacting answers (7.1) and with getting data out (section 10) is free. For other help that goes beyond what the Service provides, Pulseri may charge reasonable costs if it tells the Customer the cost first.

7.4 Deleting a Person. When the Customer deletes a Person in the Service, Pulseri: (a) removes the Person's name, email address and traits, replaces the ID the Customer gave the Person with a meaningless label, and deletes the Person's profile picture; (b) scrubs the content of the events it stored about the Person; (c) deletes the Person's survey delivery records, after adding them to totals that contain no personal data; (d) keeps the Person's survey answers, including written comments and their sentiment and theme tags, linked to the now anonymous record, so the Customer's trend history is not broken. Weekly AI summaries that were already written also stay. Comments and summaries can still contain personal data. If the Customer needs specific comments removed, it can ask at [email protected]; (e) if the Person's email address was blocked (for example because they unsubscribed), keeps a one-way hash of the address (a scrambled code that cannot be turned back into the address), so that the address is never emailed again; and (f) records in the audit log that the Person was deleted and by whom, without any details about the Person. Other records that mention the Person, such as logs of alerts and webhook deliveries, expire on the schedule in Annex 1. Copies that have already left the Service, for example alerts the Customer had sent to Slack or email, are under the Customer's control.

8. Personal data breach

8.1 Notice. Pulseri will tell the Customer about a personal data breach affecting Customer Personal Data, including one at a Sub-processor, without undue delay and no later than 72 hours after becoming aware of it. An Order Form may set a shorter time. Pulseri "becomes aware" when it has a reasonable belief that a breach has happened.

8.2 Who is told. Pulseri sends the notice to the email addresses of the Customer's account owners, and to any other address the Customer has asked Pulseri, by writing to [email protected], to use for breach notices. The Customer keeps these addresses up to date.

8.3 What the notice says. The notice includes, as far as then known: what happened; where possible, the categories and approximate number of data subjects and records concerned; the likely consequences; what Pulseri has done or proposes to do about it; and a contact point for more information. Where not everything is known at first, Pulseri sends what it knows and adds the rest as it learns it.

8.4 Containing the breach and helping the Customer. Pulseri will take reasonable steps to contain the breach, reduce its effects and stop it happening again. It will help the Customer meet its own duties to notify supervisory authorities and data subjects. Pulseri will not notify them about the Customer's data on the Customer's behalf unless the law requires it or the Customer asks. A notice from Pulseri is not an admission of fault.

8.5 This section is how Pulseri meets its duty, under the GDPR, the PDPL and other Data Protection Law, to inform the Customer as controller.

9. Assessments, consultation and records

9.1 Taking into account the nature of the processing and the information available to it, Pulseri gives the Customer reasonable help with data protection impact assessments and with prior consultation of supervisory authorities about the Service.

9.2 Pulseri keeps a written record of the processing it carries out for its customers, as Article 30(2) of the GDPR and the PDPL require, and makes it available to a supervisory authority on request.

10. Return and deletion

10.1 During the term. The Customer can read Customer Personal Data in the dashboard and through the API and the assistant (MCP) connection, and can delete it in the Service. Pulseri does not offer a bulk export tool. If the Customer needs help getting its data out, Pulseri gives reasonable help on request.

10.2 After the subscription ends. The account becomes read-only for at least 90 days. During that time the Customer can still sign in and read its data in the dashboard and through the API. Pulseri also gives reasonable help getting the data out on request, including where the Terms of Service allow it to withhold access after a serious breach of the Acceptable Use Policy. Pulseri emails the Customer 30, 7 and 1 days before deletion. During this period Pulseri only stores the data and gives the Customer access to it. The Customer may ask at [email protected] for its data to be deleted sooner.

10.3 Deletion. At the end of the read-only period, or sooner on request, Pulseri deletes Customer Personal Data from its live systems, including the audit log. Copies in database backups are gone within 14 days after that, and copies in server disk snapshots within 7 days. Server logs are kept for up to 30 days.

10.4 Legal hold. If the law, a court or a legal dispute requires Pulseri to keep some Customer Personal Data (a "legal hold"), Pulseri pauses deletion of that data only, keeps it protected, uses it only for that purpose and deletes it when the hold ends.

10.5 On request, Pulseri confirms the deletion in writing.

11. Information and audits

11.1 Information. Pulseri makes available to the Customer the information needed to show that it meets this DPA and Article 28 of the GDPR. Normally it does so by providing this DPA's annexes, the Security page and summaries of its relevant policies, and by answering the Customer's reasonable written questions. Business and Enterprise customers can also ask Pulseri to fill in their own security questionnaire. Pulseri does not currently hold third-party certifications such as SOC 2 or ISO 27001 and does not claim them.

11.2 Remote audit. If that information is not enough to show compliance, the Customer (or an independent auditor that it appoints, that is bound by confidentiality and is not a competitor of Pulseri) may audit Pulseri's compliance with this DPA by remote review of documents. The Customer gives at least 30 days' written notice, may audit once in any 12 months, and pays its own costs.

11.3 On-site audit. An audit at Pulseri's premises is available only where a supervisory authority requires it, or after a personal data breach at Pulseri where documents cannot show compliance. It takes place during normal business hours, on at least 30 days' written notice unless the authority requires less, without access to other customers' data, and without unreasonably disrupting Pulseri's business.

11.4 Costs if a breach is found. If an audit finds that Pulseri has materially breached this DPA, Pulseri pays the reasonable costs of that audit and fixes the breach promptly.

11.5 Audit rights under the SCCs are exercised as this section sets out. Nothing in this section limits the powers of a supervisory authority.

12. US state privacy laws

12.1 Where the CCPA or a similar US state privacy law applies to Customer Personal Data, Pulseri acts as the Customer's service provider (or "processor" or "contractor", as that law calls it). The business purposes for which the Customer discloses the data to Pulseri are the purposes listed in Annex 1.

12.2 For that data, Pulseri will: (a) not sell it or share it (in the CCPA, "sharing" means passing it on for advertising based on a person's activity across different businesses' websites and services); (b) not keep, use or disclose it for any purpose other than the business purposes in Annex 1, or outside the direct business relationship between the Customer and Pulseri, except as the law allows; (c) not combine it with personal information that Pulseri receives from others or collects itself, except as the law allows; (d) comply with the law that applies to it as a service provider and give the data the same level of privacy protection that the law requires of the Customer; (e) tell the Customer if it decides it can no longer meet these duties; (f) let the Customer, after giving notice, take reasonable and appropriate steps to stop and fix any unauthorised use of the data, including the steps in sections 7, 10 and 11; and (g) pass these same duties on to its Sub-processors by written contract.

13. UAE data protection law

13.1 Where the PDPL applies to Customer Personal Data, Pulseri, as processor: (a) processes the data only on the Customer's instructions, for the purposes in Annex 1 and for no longer than the periods in Annex 1 and section 10; (b) protects the data with the measures in Annex 2; (c) keeps a record of the processing it carries out for the Customer (section 9.2); (d) gives the Customer the information it needs to show compliance (section 11); (e) tells the Customer about a breach as section 8 sets out; and (f) deletes the data when the processing ends, or returns it as section 10 sets out.

13.2 Pulseri will tell the Customer about any PDPL requirement it learns of that affects transfers of Customer Personal Data into or out of the UAE.

14. Liability

Each side's liability under or in connection with this DPA, including under the SCCs as between the parties, is subject to the limits on liability in section 15 of the Terms of Service. Nothing in this DPA limits either side's liability to data subjects, or data subjects' rights, under the SCCs or Data Protection Law.

15. Term, order of priority and law

15.1 Term. This DPA lasts as long as Pulseri processes Customer Personal Data for the Customer. Sections that by their nature should continue after it ends, such as confidentiality and deletion, do so.

15.2 Order of priority. If documents conflict, this order applies, highest first, as in section 1.5 of the Terms of Service: a signed Order Form; the SCCs, where they apply; this DPA and the sub-processors page; the Terms of Service; the Billing and cancellation page and the pricing page; then the Acceptable Use Policy. An Order Form cannot change the SCCs or reduce the protection they give data subjects.

15.3 Law and courts. This DPA is governed by the law and courts set out in the Terms of Service (the law of England and Wales and the courts of the Dubai International Financial Centre), unless a signed Order Form says otherwise. The SCCs are governed by the law and courts chosen in section 6, and any other choice that Data Protection Law requires also applies.

15.4 Changes. Pulseri may update this DPA to reflect changes in law or in the Service by giving 30 days' notice. The SCCs cannot be changed this way. A change that the law requires may apply sooner. If the Customer objects on reasonable grounds within the 30 days, the parties will talk in good faith. If they cannot agree, the Customer may cancel without penalty before the change takes effect, and the old DPA then applies until the end of the period it has paid for.

15.5 Signing. This DPA applies when the Customer accepts the Terms of Service. Enterprise customers can ask for a countersigned copy at [email protected].

15.6 Notices. Notices to Pulseri about this DPA go to [email protected], with a copy to [email protected] for notices that end the agreement or claim a breach. Notices to the Customer go to the email addresses of its account owners. An email notice counts as received one business day after it is sent.

Annex 1: Details of processing

Retention

Annex 2: Technical and organisational measures

These are the measures in place at the date of this DPA.

1. Hosting and location. The Service runs on Google Cloud in Belgium (EU): the application server, the database, file storage and the secrets store. Database backups are kept in Google's EU locations.
2. Customer separation. Each customer's data sits in a separate logical tenant. Every database query is limited to one customer, and the database also enforces row-level security (rules that limit each query to one customer's rows) as a second safeguard. A request for another customer's item is answered as "not found". Automated tests check this separation against a real database.
3. Network protection. All traffic to the app and the API passes through Cloudflare, which provides a web application firewall, attack protection and rate limiting. To do this, Cloudflare decrypts the traffic it passes on. The server's firewall accepts web traffic only from Cloudflare. The database has no public internet address and is reachable only on Pulseri's private network.
4. Encryption in transit. Connections between browsers or API clients and Cloudflare use TLS 1.2 or higher. Connections from Cloudflare to the app and API servers are encrypted, and the server's certificate is checked. Connections from the application to the database are encrypted, and production refuses unencrypted database connections. One exception: the logo files that customers upload for their surveys and widget are public by design, and on the last step between Cloudflare and Google's file storage they travel without encryption. Profile pictures and other files are stored privately and are not served this way.
5. Encryption at rest and secrets. Google encrypts stored data by default, including the database, files and backups. Sensitive secrets (integration credentials, webhook signing secrets, single sign-on secrets and identity verification secrets) are encrypted again by the application before they are stored. Passwords and secret API keys are stored only as one-way hashes. Public widget keys are not secret by design: they appear on the Customer's website and can only send events. Application secrets are kept in Google Secret Manager, not in code.
6. Access control for customers. Role-based permissions that the Customer configures; optional two-step sign-in with an authenticator app; a check of new passwords against lists of passwords exposed in known breaches; signing in again before sensitive actions; API keys with defined scopes; and, on plans that include them, single sign-on (SAML and OIDC), SCIM user provisioning (automatic syncing of users from the Customer's directory) and session limits.
7. Administrative access. Pulseri staff reach the server only through Google's Identity-Aware Proxy, with their individual Google accounts. There is no public SSH access. Access is limited to the people who need it.
8. Audit log. The Service keeps an audit log of security-relevant actions, including the IP address and browser details of the person who acted. The database refuses changes to log entries; entries are removed only by the automatic retention purge at the end of the Customer's retention period (including after a downgrade grace period), or when the account is deleted. The Customer can read the log in the dashboard, and through the API on plans that include it.
9. Backups and recovery. The database is backed up daily; the last 14 backups are kept, and point-in-time recovery covers the last 7 days. The server disk is snapshotted daily and snapshots are kept for 7 days. The database runs in a single zone, without automatic failover to another zone, so an outage of that zone can make the Service unavailable until it is restored. Automated monitoring alerts Pulseri when the API stops responding.
10. Webhooks and integrations. Outgoing webhooks are signed so the receiver can check they came from Pulseri. Incoming messages from providers (for example email delivery events) are checked for a valid signature. Outgoing destination addresses are checked before data is sent.
11. AI processing. Before written answers are sent to the AI provider, email addresses and some phone number formats are removed from the copy that is sent. This does not remove all personal data. The stored original is unchanged.
12. Development. Automated tests run against a real database, including tests of customer separation.
13. People and incidents. Staff and contractors are bound by confidentiality duties. Personal data breaches are handled and notified as section 8 sets out.

Annex 3: Sub-processors

The Sub-processors are the providers listed in the first section of the sub-processors page: the providers that process Customer Personal Data. For each one, the page gives the legal entity, what it does, the data it receives, where it processes the data and the transfer safeguard. That section is part of this DPA and is updated under section 5.3.

The other sections of that page, listing the providers Pulseri uses for its own business and the integrations customers choose to connect, are not part of this Annex (see section 5.7).