00d 00:00:00 · Black Friday — 30% off 00d 00:00:00 · Black Friday — 30% off 00d 00:00:00 · Black Friday — 30% off 00d 00:00:00 · Black Friday — 30% off

Data Processing Addendum

Version 1.0 · effective 15/11/2026 · demo text for the prototype, not legal advice.

This Data Processing Addendum (“DPA”) forms part of the agreement between SuperAgent Social and the customer that uses the service. It applies when we process personal data on your behalf. Capitalised terms not defined here take the meaning given in the terms of service. This is demo text for the prototype, not legal advice.

1. Definitions

Affiliate means an entity that controls, is controlled by or is under common control with a party, where control means ownership of more than half of the voting interests.

Agreement means the terms of service, an order form or another written agreement that governs the service, including this DPA.

Customer Data means personal data that we process on your behalf through the service, including the content you upload, the profile data of people you contact and the identifiers needed to publish.

Data Protection Laws means the GDPR, the UK GDPR, the Swiss data protection act, the CCPA as amended, and any other law that applies to the processing described here.

Personal data means information about an identified or identifiable person, and processing covers collection, storage, use, disclosure, deletion and any other operation described by the applicable law.

Security Incident means a breach of security that leads to accidental or unlawful destruction, loss, alteration or unauthorised disclosure of Customer Data on systems we control.

Sensitive Data means government identifiers, full payment card numbers, health, genetic, biometric or criminal data, passwords in clear text, and any data the law treats as a special category. The service is not designed for Sensitive Data and you must not upload it.

Sub-processor means a processor we engage to help provide the service, excluding our own employees and contractors.

SCCs means the standard contractual clauses adopted by the European Commission for transfers of personal data to third countries, as updated from time to time, and the UK addendum where it applies.

Service means the SuperAgent Social website, application and API, including the planner, Studio, inbox, workflows, API and MCP features described on this site.

Workspace means the account area that holds your brands, channels, content and settings.

Business Day means Monday to Friday, excluding public holidays in Vietnam, where our support team is based.

Customer means the entity or person that accepts the agreement and uses the service, including its authorised users and affiliates that use the workspace.

Data Subject means the person whose personal data is processed, including a workspace member, a contact you upload and a person who interacts with content you publish.

EEA means the European Economic Area: the member states of the European Union plus Iceland, Liechtenstein and Norway.

Model Provider means a third party that runs the language or image model used to draft, translate or resize content at your request, under a data processing agreement with us.

Restricted Transfer means a transfer of Customer Data from the EEA, the UK or Switzerland to a country that does not have an adequacy decision for the data concerned.

Third Party means a person or entity other than the parties, their affiliates and their sub-processors, including a network you connect and a provider whose embed appears on your content.

UK GDPR means the GDPR as it forms part of the law of England and Wales, Scotland and Northern Ireland by virtue of the European Union (Withdrawal) Act 2018, together with the Data Protection Act 2018.

2. Roles and responsibilities

Roles. You are the controller of Customer Data and we are the processor. Where you act as a processor for your own client, you confirm that you have authority to appoint us and that your instructions to us have been authorised by the relevant controller. We do not decide why Customer Data is processed; we follow your documented instructions.

Purpose limitation. We process Customer Data only to provide the service, to secure it, to comply with law and as otherwise agreed in writing. The agreement, your settings and your use of the features are your complete instructions. Processing outside those instructions needs a separate written agreement.

Prohibited data. You will not send us Sensitive Data. If you do, we may delete it and we have no liability for it. You are responsible for the accuracy and legality of Customer Data and for having the notices and consents needed to process it, including consent to contact people through the networks you use.

Your compliance. You confirm that your instructions comply with Data Protection Laws, that your content does not infringe third-party rights, and that you have a lawful basis for any contact list you upload. You are the point of contact for your own data subjects; we do not deal with them directly except where the law requires.

Our compliance. We keep a record of processing, train staff who handle Customer Data, and apply the security measures in section 4. If an instruction appears to break the law, we tell you and may pause the processing until it is corrected.

Instructions in the product. Settings you choose in the workspace are instructions: which channels are connected, who may approve a post, how long drafts are kept and whether replies are collected. Changing a setting changes what we process from that point; we do not need a separate signed instruction for each change.

Assistance. We help you meet your obligations under Data Protection Laws, including responding to a data subject, notifying a breach to an authority and carrying out an impact assessment, to the extent the information is available to us and the law requires it. Help beyond the standard features may be charged at our published rates, agreed before the work starts.

No independent use. We do not use Customer Data for our own marketing, for profiling people who appear in your content, or to build a dataset for another customer. Aggregated statistics that cannot identify a person or a workspace may be used to operate and improve the service.

Records. We keep a record of the categories of processing, the sub-processors involved, the transfer mechanisms and the security measures for each customer. The record is available to a supervisory authority on request and to you in summary form. We keep it for the term of the agreement and for the period a regulator may ask about it.

Cooperation with authorities. If an authority contacts us about your workspace, we tell you unless the law forbids it, and we do not hand over Customer Data without checking the request's legal basis. We may charge a reasonable fee for repeated or unusually broad requests that go beyond the standard features.

3. Sub-processing

Authorised sub-processors. You authorise us to engage sub-processors for hosting, payment, email delivery and model inference. The current list is available on request. We notify customers who subscribe to updates at least 10 days before adding a sub-processor that processes Customer Data.

Obligations. Each sub-processor is bound by a written agreement with data protection terms at least as protective as this DPA. We remain responsible for their performance and for any act or omission that breaches our obligations. We do not share confidential sub-processor agreements, but we give you the information you reasonably need about them.

Objection. You may object to a new sub-processor on reasonable data protection grounds within 10 days of notice. If we cannot resolve the objection, you may suspend the affected part of the service or terminate the agreement without penalty for the unused period.

Current list. The categories are cloud hosting, payment processing, email delivery, error monitoring and model inference. Within each category we may use more than one provider for resilience. The list names the provider, the data it can access and the country where it processes; ask support for the current version and we send it within two Business Days.

Onward transfers. A sub-processor may process Customer Data outside the EEA only under a lawful transfer mechanism. We flow down the SCCs and the security terms of this DPA, and we do not allow a sub-processor to further sub-process Customer Data without our written approval.

4. Security

Measures. We encrypt tokens at rest and traffic in transit, scope access per workspace and brand, require strong authentication for staff, log administrative access and every write through the API or MCP, and keep backups with restricted access. We test changes before release and review access when someone leaves.

Confidentiality. Staff and contractors who can access Customer Data are under a written confidentiality obligation that survives their engagement. Access is granted only where a role needs it.

Updates. Security measures change with technology. We may update them provided the overall level of protection does not fall. You are responsible for reviewing the information we publish and deciding whether the service meets your own obligations.

Incidents. If we become aware of a Security Incident, we notify you without undue delay and where feasible within 48 hours, give you the information we have as it becomes known, and take reasonable steps to contain and investigate it. Notification is not an admission of fault. You are responsible for your own notifications to data subjects and authorities where the law requires them.

Your side. You keep your credentials secure, control who can approve posts, and encrypt or back up any Customer Data you hold outside the service. You must not share workspace access with people who do not need it.

Encryption and keys. Channel tokens and stored files are encrypted with keys held in a managed key service, separate from the application database. Keys are rotated on a schedule and after a staff departure that could expose them. Backups are encrypted with the same controls and restored only into a restricted environment.

Monitoring and response. We log authentication, permission changes and publishing jobs, alert on unusual volume and keep an on-call rotation for security events. Access to production data requires a second approval, is time-limited and is recorded. We test the response plan at least once a year.

Physical and supplier security. Our hosting providers control physical access to data centres and publish independent assessments. We review a provider before onboarding and at least once a year after that, and we remove a provider that no longer meets the standard in this section.

Vulnerability management. We scan dependencies, run automated tests on every change and review the result before release. A critical vulnerability is fixed before the next release; a moderate one is scheduled and tracked to closure. We do not deploy a change that would weaken the controls in this section without a written risk decision.

Data minimisation. We ask for the fields the service needs and no more. A channel token is stored once per connection, a contact record holds only what you upload and what the network returns, and logs omit message bodies unless a support case requires them. Test data is synthetic, never copied from a customer workspace.

Staff and contractors. Everyone with access completes privacy and security training when they join and once a year after that. Access is removed on the day someone leaves, and a quarterly review checks for accounts that should no longer exist.

5. Security reports and audits

Audit rights. We give you the information reasonably needed to show compliance with this DPA and allow audits, including inspections, where the law gives you that right. Audits are scheduled in advance, happen during business hours and must not compromise the security of other customers.

Reports. On request, and no more than once a year, we provide a summary of our most recent independent security assessment on a confidential basis. The summary covers the scope of the assessment and the status of material findings.

Questionnaires. We answer reasonable security and due diligence questionnaires. Where a question needs customer-specific detail, we answer under confidentiality rather than in a public document.

Scope and cost. An audit covers the systems that process Customer Data and the controls in section 4. It does not include source code beyond what is needed to explain a control, and it does not include another customer's data. If an audit finds a material gap, we give you a remediation plan with dates and tell you when the work is done.

Confidentiality. Reports and answers are confidential. You may share them with your own auditor or a regulator that requires them, and you tell us before you do unless the law forbids it.

6. International transfers

Locations. Customer Data may be processed in the EU, the United States and Vietnam, where we, our affiliates and our sub-processors operate. We ensure each transfer has a lawful mechanism and that additional safeguards are added where the destination does not have an adequacy decision.

EEA and UK. For transfers out of the EEA we rely on the SCCs; for the UK we rely on the UK addendum to the SCCs. The parties are deemed to have signed the relevant clauses and completed the tables with the information in this DPA.

Switzerland. For Swiss data, the SCCs apply with the modifications needed by Swiss law: the supervisory authority is the Swiss Federal Data Protection and Information Commissioner and the courts of Switzerland decide disputes.

Alternative mechanism. If we adopt a different lawful transfer mechanism, it applies instead of the clauses above for the countries it covers. If a court or authority decides the clauses cannot be relied on, we may add measures reasonably needed to keep the transfer lawful.

Assessment. Before a Restricted Transfer we assess the law and practice of the destination, the sensitivity of the data and the safeguards available. Where the assessment shows a gap, we add encryption, pseudonymisation or a contractual right to challenge a government request. We review the assessment when the law changes or at least once a year.

Government access. We challenge a request that appears unlawful or overbroad, give you the information we can, and disclose only what the law compels. Our support team cannot disclose Customer Data to an authority without legal review.

Localisation. We do not require you to store data in a particular country. If a customer needs a regional workspace, we discuss it before signing and record the location in the order form; the transfer terms in this section still apply to support and disaster recovery access.

Onward transfers. A sub-processor may not transfer Customer Data to another country without a lawful mechanism and our written approval. We keep a list of the countries where Customer Data is processed and review it when a provider changes its infrastructure.

7. Return or deletion of data

On termination. When the agreement ends, you may export Customer Data from the workspace or ask us to return it in a common format. After the retention window we delete it, including copies in active systems, except data we must keep by law or in backups that expire on their normal schedule.

Backups. Backup copies are isolated, protected from further processing and deleted when the backup cycle ends. A deletion certificate is available on written request. Deleting a single item removes it from the workspace immediately and from backups within 90 days.

Export. An export includes content, channel metadata, contacts you uploaded and a list of published items. It does not include channel tokens, which are deleted separately and cannot be exported for security reasons. If you need a format the product does not offer, ask support before you close the workspace; after closure we can only restore from a backup for a limited window.

Legal hold. If a legal claim or an authority requires us to keep data, we isolate it from normal processing, restrict access and delete it when the hold ends. We tell you about the hold unless the law forbids it.

8. Data subject rights and cooperation

Requests. The service gives you self-service tools to access, correct, export and delete Customer Data. If a data subject contacts us directly, we do not respond on your behalf unless the law requires it; we pass the request to you or tell the person to contact you. We help you answer requests to the extent the law requires and the information is available to us.

Assessments. We provide the information in this DPA and the security summary so you can carry out a data protection impact assessment or a prior consultation. If that is not enough, we provide reasonable additional help at your cost.

Verification. When a request reaches us, we check that it comes from the account email or from someone the workspace owner has authorised. We do not disclose one person's data to another member of the same workspace without the owner's confirmation.

Deletion limits. We cannot delete a post that a network already published on its own systems; you must remove it there. We can delete the copy in the workspace, the schedule and the token that would let it publish again.

Automated assistance. Where you ask the agent to classify a reply or suggest a time, the result is a suggestion shown to you. It is not used to make a decision about the person who wrote the message, and you can turn the feature off for a workspace. A person remains responsible for what is published.

9. Jurisdiction-specific terms

Where Customer Data is protected by the law of a jurisdiction described in Annex B, the terms in that annex apply in addition to this DPA. If they conflict with the rest of the DPA, the jurisdiction-specific term prevails, but only for that jurisdiction and only to the extent of the conflict.

If you are established in a jurisdiction not listed in Annex B, the DPA still applies and the law your agreement names governs it. Tell us if a local rule requires a specific term and we will discuss an addendum before you sign rather than after a regulator asks.

10. Limitation of liability

Liability under this DPA is subject to the exclusions and limits in the agreement. Claims are brought by the customer entity that signed the agreement. Nothing in this DPA limits the rights of a data subject under Data Protection Laws, and nothing excludes liability that cannot be excluded by law.

Where a party is liable for a fine imposed by an authority, the other party cooperates in challenging it and the liability follows the agreement's allocation. A party that settles a claim without the other's consent does not bind the other party for the settled amount.

11. Relationship with the agreement

This DPA stays in force while we process Customer Data and until the data is returned or deleted. It replaces any earlier data processing agreement between us for the same service. If documents conflict, the order of precedence is: the SCCs, then this DPA, then the terms of service. Apart from the changes here, the agreement stays as it was.

If a clause of this DPA is invalid, the rest remains in force and the invalid clause is replaced by one that comes closest to its purpose. A failure to enforce a clause is not a waiver. The DPA is governed by the law named in the agreement unless a mandatory data protection rule requires otherwise.

The DPA does not create rights for anyone who is not a party, except where the law gives a data subject a right. A party may transfer its rights under the DPA only with the other party's written consent, except as part of a merger or acquisition where the successor agrees to the same obligations.

12. Contact us

Data protection questions: privacy@superagent.social. Security reports: security@superagent.social. Post: the address on the contact page. We answer DPA questions within five working days, and a request for the sub-processor list or a copy of the transfer safeguards is handled by the same team. Include the workspace name so we can find the agreement without asking you twice.

13. Annex A — Details of data processing

(a) Data subjects. The people whose data is processed are workspace members, the contacts whose details you upload, and people who reply to or interact with content you publish. It does not include people whose data you have no right to process.

(b) Categories of data. For members: name, email, role, login metadata and billing country. For contacts: name, handle, email or phone where you provide it, the content of messages, and the public profile data a network returns. For both: technical data such as IP address, device, timestamps and error logs.

(c) Sensitive data. None is requested or intended. The service is not designed for special category data, and you must not upload it. If it appears in content you submit, you are responsible for the lawful basis and for telling us so we can delete it.

(d) Frequency. Continuous while the workspace is active and while content is scheduled or published. Some processing happens only when you use a feature, such as an export or an API call.

(e) Nature and purpose. Storage, formatting, drafting, scheduling, publishing, reply collection, analytics about your own content, security monitoring and support. We do not use Customer Data for advertising or to train a model for other customers.

(f) Duration. For the term of the agreement plus the retention periods in section 7 and the privacy policy. Backups expire within 90 days; billing records are kept as long as tax law requires.

(g) Sub-processors. Hosting, payment, email delivery and model providers, listed on request and notified under section 3. Each is bound by terms at least as protective as this DPA.

(h) Security measures. Encryption at rest and in transit, scoped access, audit logging, backup and restore testing, staff confidentiality, vendor review and an incident response plan. Section 4 describes the measures in full.

(i) Transfers. Customer Data may be processed in the EEA, the UK, the United States and Vietnam. Transfers rely on an adequacy decision or the SCCs with the additional measures described in section 6.

(j) Retention. Content and account data are kept for the term of the agreement and the periods in section 7. Billing records follow tax law, security logs are kept for twelve months and backups expire within 90 days.

(k) Special categories. No special category data is requested. If content you upload contains it, you confirm you have a lawful basis and tell us so we can restrict the workspace or delete the item. We do not use it for any other purpose.

(l) Automated decisions. The service suggests times, captions and replies, but a person approves what is published unless you switch on a rule that publishes without review. We do not make decisions that produce legal effects about a data subject, and we do not profile contacts for advertising.

(m) Frequency and volume. Processing is continuous while a workspace is active. The volume depends on how many channels, brands and posts you run; the plan limits are the practical ceiling and are shown on the pricing page.

(n) Third-party disclosures. We disclose Customer Data to the networks you connect at your instruction, to sub-processors under section 3, and to an authority only as described in section 6. We do not disclose it to a data broker or an advertising network.

(o) Source of data. Account data comes from you. Contact data comes from what you upload or from a network when you connect a channel. Technical data comes from your browser and our servers. We do not buy contact lists or enrich your contacts from a third-party database.

(p) Consequences of not providing data. If you do not provide an account email and the channel authorisation, we cannot create a workspace or publish. Optional fields can be left empty without losing a core feature. A feature that needs a new field explains why before it asks.

14. Annex B — Jurisdiction-specific terms

Europe

Objection to sub-processors. You may object to a new sub-processor within 10 days of notice on reasonable data protection grounds. If we cannot reach a commercially reasonable resolution, we will either not appoint the sub-processor or let you terminate the affected part of the service without penalty.

Government requests. We do not voluntarily give government agencies access to Customer Data. If we receive a compulsory request, we review its legality, try to redirect the agency to you, notify you where the law allows, and disclose only the minimum permitted. If the law forbids notice, we use best efforts to obtain a waiver.

Your rights. Nothing in this annex limits your rights under the GDPR, including the right to lodge a complaint with a supervisory authority in the country where you live, work or where the alleged breach happened. We cooperate with that authority as the law requires.

Representative. If we are required to appoint an EU or UK representative, the name and address appear on the contact page before the service is offered in that market. The representative can be contacted about this DPA and about data protection questions, in addition to our privacy team.

California

For the CCPA, “controller” includes “business”, “processor” includes “service provider”, “data subject” includes “consumer” and “personal data” includes “personal information”. We process Customer Data only for the purposes in this DPA and do not sell it or share it for cross-context behavioural advertising. We help you answer consumer requests and impose the same restrictions on our sub-processors.

We do not combine personal information received from you with personal information from another source, except to provide the service. If you receive a request to delete, we delete the data at your instruction and confirm in writing. We notify you if we determine we can no longer meet the CCPA's requirements.

Where the CCPA gives a consumer the right to know, delete or correct, you are responsible for receiving and verifying the request; we provide the data and the tools. We do not discriminate against a consumer for exercising a right, and we do not use the data for a purpose that the CCPA treats as a sale or share.

Canada

For PIPEDA, we ensure sub-processors are bound by written terms at least as protective as this DPA, use appropriate technical and organisational measures, and notify you of a breach as described in section 4. You remain responsible for your own privacy obligations to the people whose data you upload.

If a Canadian authority requires us to disclose Customer Data, we notify you unless the law forbids it and we disclose only what the request compels. You can ask for the privacy contact named in the agreement for anything this annex does not cover.

Accountability. We keep records of the processing we carry out for you, the sub-processors involved and the safeguards applied to a transfer. Those records are available to a regulator on request and to you in summary form. If we transfer Customer Data to a sub-processor in another country, we remain accountable for the protection of the data under Canadian law.

Breach reporting. Where a breach creates a real risk of significant harm, we give you the information you need to report it to the Office of the Privacy Commissioner of Canada and to the people affected. We do not wait for a formal finding before telling you what we know.