法的情報
Data Processing Addendum
最終更新日: 2026-10-26
この文書は英語で作成されており、英語版が適用されます。
This Data Processing Addendum ("DPA") is part of the Terms of Service between Anatolii Hlushko ("ViralShaker", the processor) and the customer that owns a workspace ("Customer", the controller). It applies automatically when ViralShaker processes Customer Personal Data subject to the EU GDPR, the UK GDPR, the Swiss FADP or similar laws ("Data Protection Law"). If you need a countersigned copy, email support@viralshaker.com.
1. Definitions
"Customer Personal Data" means personal data in Your Content or in workspace data that ViralShaker processes for the Customer. "Controller", "processor", "data subject", "personal data breach" and "processing" have the meanings given in Data Protection Law. Other capitalised terms have the meaning given in the Terms.
2. Roles and instructions
The Customer is the controller of Customer Personal Data, and ViralShaker processes it as a processor. ViralShaker processes Customer Personal Data only on the Customer's documented instructions. The Terms, this DPA, and the Customer's use of the Service's features and settings are those instructions. If ViralShaker believes an instruction breaks Data Protection Law, it will tell the Customer.
ViralShaker is a separate controller for account, billing, security and analytics data, as described in the Privacy Policy.
3. Details of the processing
| Subject matter | Providing the Service under the Terms |
| Duration | The term of the Terms, plus the deletion period in section 10 |
| Nature and purpose | Hosting, storing, analysing and transforming content; generating content with AI models; publishing to platforms the Customer connects; showing analytics; support |
| Categories of data subjects | The Customer's team members; people who appear in the Customer's uploads, including staff, customers, models and creators; people whose likeness is used for AI influencers; the Customer's social media audience, as reflected in aggregate post metrics |
| Categories of personal data | Names, images, video, voice recordings, likeness, testimonials and other content the Customer uploads; social account identifiers and handles; aggregate engagement metrics |
| Special categories | None intended. The Customer must not upload special category data unless it has a lawful basis and has told ViralShaker in writing. |
4. ViralShaker's obligations
ViralShaker will:
- make sure that everyone authorised to process Customer Personal Data is bound by confidentiality;
- implement the security measures in section 11;
- use subprocessors only as described in section 5;
- help the Customer, taking into account the nature of the processing, to respond to data subject requests, and to carry out data protection impact assessments and prior consultations;
- notify the Customer of a personal data breach affecting Customer Personal Data without undue delay, and within 48 hours of becoming aware of it, with the information the Customer needs to meet its own obligations;
- delete or return Customer Personal Data at the end of the service, as described in section 10;
- make available the information needed to show compliance with this DPA, and allow audits as described in section 9.
5. Subprocessors
The Customer gives general authorisation for ViralShaker to use subprocessors. The current list is at Subprocessors. ViralShaker will:
- bind each subprocessor to data protection terms that are at least as protective as this DPA;
- give the Customer at least 14 days' notice before adding or replacing a subprocessor, by email to the Customer if it has asked for notices at support@viralshaker.com, and by updating the Subprocessors page;
- remain responsible for its subprocessors' performance.
The Customer may object to a new subprocessor on reasonable data protection grounds within that notice period. The parties will then discuss it in good faith. If they can't resolve the objection, the Customer may terminate the affected part of the Service and receive a refund of prepaid fees for the unused period.
6. AI providers
Customer Personal Data sent to AI providers is used only to produce output for the Customer. ViralShaker doesn't use Customer Personal Data to train AI models, and doesn't allow its AI subprocessors to do so.
7. The Customer's obligations
The Customer is responsible for having a lawful basis for the processing and for giving data subjects the information required by law. That includes obtaining consent from anyone whose face or voice is used in an AI influencer, character swap or voice-over, and keeping a record of it. The Customer is also responsible for its own instructions complying with Data Protection Law.
8. International transfers
ViralShaker and its subprocessors may process Customer Personal Data outside the EEA, the UK and Switzerland. Where a transfer goes to a country without an adequacy decision, the parties agree that:
- for EU and EEA data, the Standard Contractual Clauses adopted by Commission Implementing Decision (EU) 2021/914 apply, Module Two (controller to processor), and are incorporated by reference. Clause 7 (docking) applies. In Clause 9, Option 2 applies with the notice period in section 5. In Clause 11, the optional wording doesn't apply. In Clauses 17 and 18, the governing law and courts are those of Ireland. Annex I is completed by section 3 of this DPA, and Annex II by section 11;
- for UK data, the UK International Data Transfer Addendum to those Clauses applies;
- for Swiss data, those Clauses apply with references to the GDPR read as references to the FADP, and the Swiss Federal Data Protection and Information Commissioner as the competent authority.
Where a recipient is certified under the EU–US Data Privacy Framework (or its UK and Swiss extensions), ViralShaker may rely on that instead.
9. Audits
ViralShaker will answer the Customer's reasonable written security questionnaires once a year. If that isn't enough to demonstrate compliance, or if a supervisory authority requires it, the Customer may carry out an audit at its own cost, on 30 days' notice, during business hours, through an independent auditor bound by confidentiality, and without accessing other customers' data.
10. Deletion and return
The Customer can download its content from the Service at any time while the workspace is open. When a workspace is closed, ViralShaker deletes Customer Personal Data in it within 30 days, and from backups within a further 30 days, unless the law requires it to be kept. ViralShaker will confirm deletion in writing on request.
11. Security measures
- Encryption: TLS for data in transit. Social account tokens encrypted at rest. API keys stored as hashes.
- Access control: production access limited to staff who need it, with separate admin credentials. Staff access to customer workspaces for support is logged in an audit trail.
- Isolation: every workspace's data is scoped to that workspace in the application and database. Roles control what each member can do.
- Network: the database and cache accept local connections only. Outbound requests to customer-supplied URLs are checked to block internal addresses.
- Resilience: nightly database backups, and backups before every release. Releases roll out one instance at a time.
- Abuse protection: rate limits per user, per API key and per workspace. Prompts are checked automatically before generation.
- Monitoring: error monitoring and structured logs.
- People: staff and contractors are bound by confidentiality.
12. Liability and precedence
Each party's liability under this DPA is subject to the limits in the Terms, except where Data Protection Law doesn't allow it. If this DPA conflicts with the Terms, this DPA prevails for the processing of Customer Personal Data. If it conflicts with the Standard Contractual Clauses, the Clauses prevail.