Subsentra / Legal
Data Processing Agreement
Last updated: 14 November 2026
This agreement forms part of our Terms of Service and applies automatically whenever Subsentra processes personal data on your behalf. You don't need to sign anything separately; if you need a countersigned copy, email privacy@subsentra.com.
1. Parties and roles
This Data Processing Agreement (“DPA”) is between the customer that has accepted the Terms of Service (the “Customer”, the controller) and Felix Maru, trading as Subsentra, a sole trader based in Kenya (“Subsentra”, the processor). Terms such as “personal data”, “processing”, “controller”, “processor”, “data subject” and “personal data breach” have the meanings given in Data Protection Law. “Data Protection Law” means the data protection and privacy laws that apply to the processing, for example the GDPR (EU), the UK GDPR, US state privacy laws such as the California Consumer Privacy Act, the Kenya Data Protection Act, 2019, and similar laws elsewhere.
If this DPA conflicts with the Terms of Service, this DPA wins on matters of data protection.
2. Details of the processing
Subject matter
Providing the Subsentra subscription tracking service to the Customer, and, if ordered, the one-off set-up audit.
Duration
For the term of the Customer's account, plus the deletion period in section 11.
Nature and purpose
Storing, organising, displaying, matching, converting and exporting subscription records; sending sign-in codes, invitations and renewal reminder emails to the Customer's users; importing Shopify bill exports and matching bank or card statement rows against the Customer's subscriptions; backing up data; and providing support.
Types of personal data
- Names, work email addresses and roles of the Customer's staff and invited users, and their assignment as owners of subscriptions.
- Vendor contact details the Customer chooses to record (for example an account manager's name and email).
- Statement lines that match, or look like, subscriptions: date, description, amount and currency. Where a statement line names an individual (for example a sole-trader vendor), that name is included.
- Notes and free text the Customer adds to subscription entries.
- Audit log entries and sign-in records linked to users.
The Customer must not upload special category data, criminal offence data, full card numbers or passwords.
Categories of data subjects
- The Customer's employees, contractors and other users.
- Contacts at the Customer's vendors and suppliers.
- Any individual named in a statement line the Customer imports.
3. Processing only on instructions
Subsentra will process Customer personal data only on the Customer's documented instructions. The Terms of Service, this DPA and the Customer's use and configuration of the Service are those instructions. If the law requires other processing, we will tell the Customer first unless the law forbids it. We will tell the Customer if we believe an instruction breaks Data Protection Law.
4. Confidentiality
Everyone authorised by Subsentra to process Customer personal data is bound by a duty of confidentiality, and access is limited to what they need to provide and support the Service.
5. Security
Subsentra will implement and maintain appropriate technical and organisational measures to protect Customer personal data, as required by the security obligations under Data Protection Law. The current measures are described in the Annex. We may update them, but will not reduce the overall level of protection.
6. Sub-processors
- The Customer gives general authorisation for Subsentra to use sub-processors. The current list is on the sub-processors page.
- We will give at least 14 days' notice by email to the account owner before adding or replacing a sub-processor.
- The Customer may object on reasonable data protection grounds within that notice period. We will then work with the Customer in good faith to find a solution. If we cannot, the Customer may terminate the affected Service and receive a refund of prepaid fees for the unused period.
- Each sub-processor is bound by a written contract with data protection obligations no less protective than this DPA. Subsentra remains responsible for its sub-processors' performance.
7. Assisting the Customer
- Data subject requests: the Service lets the Customer view, correct, export and delete data. Where that is not enough, we will help the Customer respond to requests to exercise data subject rights. If a data subject contacts us directly about Customer data, we will pass the request to the Customer and not respond ourselves unless instructed.
- Impact assessments: we will provide reasonable information to help the Customer carry out data protection impact assessments and any prior consultation with a supervisory authority.
- Security and breach obligations: we will help the Customer meet its security, breach notification and impact assessment obligations under Data Protection Law, taking into account the information available to us.
8. Personal data breaches
Subsentra will notify the Customer without undue delay, and in any event within 48 hours, after becoming aware of a personal data breach affecting Customer personal data. The notice will describe, as far as is then known, the nature of the breach, the categories and approximate number of data subjects and records concerned, likely consequences, and the steps taken or proposed. We will provide further information as it becomes available and take reasonable steps to contain the breach.
9. International transfers
Customer data is hosted in the United States (Northern Virginia). Some sub-processors are located in the USA, and Subsentra is operated from Kenya, so access by Subsentra from Kenya may be a restricted transfer under Data Protection Law.
- Where Data Protection Law requires safeguards for transfers from the Customer to Subsentra, including where Subsentra accesses data from Kenya, the parties agree to the standard contractual clauses approved by the relevant authorities (such as the European Commission's Standard Contractual Clauses, Module 2: controller to processor, and their UK equivalent where those laws apply), which are incorporated by reference. The Customer is the exporter and Subsentra is the importer. The details in section 2 and the Annex complete the appendices.
- Subsentra has carried out a transfer risk assessment for access from Kenya and will keep it under review. A summary is available on request.
- Transfers to sub-processors in other countries rely on an adequacy decision or similar recognition where one applies, or otherwise on standard contractual clauses approved by the relevant authorities.
10. Information and audits
Subsentra will make available the information reasonably necessary to show compliance with the processor terms required by Data Protection Law (such as Article 28 of the GDPR), including answers to security questionnaires and this DPA's Annex. If that is not enough, the Customer (or an independent auditor bound by confidentiality) may carry out an audit once a year, on at least 30 days' notice, during business hours, at the Customer's cost, and in a way that does not disrupt the Service or expose other customers' data. Additional audits are allowed after a personal data breach or where a supervisory authority requires one.
11. Deletion or return at the end
When the Customer's account ends, the Customer can export its data from the Service. Within 30 days after the end of the account, Subsentra will delete Customer personal data from live systems, unless the law requires us to keep it. Copies in encrypted backups are removed as those backups expire on their normal cycle and are not used in the meantime except to restore the Service.
12. Liability
Each party's liability under this DPA is subject to the limits and exclusions in the Terms of Service, except where Data Protection Law does not allow that.
Annex: Technical and organisational security measures
- Encryption: all traffic uses TLS. Data is encrypted at rest by our database and storage provider.
- Tenant isolation: every customer table is protected by database row-level security, so one organisation's queries cannot read another's rows. Automated tests check this isolation on every change.
- Authentication: sign-in by emailed one-time code plus a required authenticator-app second factor (MFA) for all users and for every administrative account used to run the Service.
- Least privilege: secrets and privileged keys are kept server-side only, never sent to the browser, and limited to the code that needs them.
- Audit log: changes to subscription entries, users and settings are recorded with who made them and when.
- Backups: daily backups by our database provider, plus a weekly independent encrypted dump stored separately.
- Data minimisation: only statement rows that match or look like subscriptions are stored; whole statements are never kept. Uploads are capped in size and rows.
- Abuse protection: rate limiting on sign-in and other sensitive actions, using only the IP address and a hash of the email address, kept for a short time.
- Browser security: a strict content security policy and no third-party scripts.
- Vendors: sub-processors are chosen for their security posture and bound by data processing terms.