GDPR and your subscription app: roles, responsibilities, and requests
If your app sells subscriptions and you handle data about people in the EU, GDPR obligations apply to you.
This page explains the split of responsibility when you use this subscription platform: the platform operates as a processor of end-user personal data, while you — the developer running the app — are the controller. It also covers where deletion requests and privacy questions go, and which documents to read before you ship. The processor role statement and the compliance contact are supplied by the owner: [processor role statement] and [compliance contact].
Who is the controller and who is the processor
Under GDPR, the controller decides why and how personal data is processed; the processor handles that data on the controller's instructions. When you send personal data about your end users to this subscription platform, the platform is the processor. You remain the controller of your application's data. The owner supplies the processor role statement: [processor role statement]. A useful way to test your own setup is to ask whether you can name, in one sentence, what end-user data you send and why — if you cannot, the processor relationship is not yet documented well enough on your side. That split has a practical consequence: because you are the controller, you are responsible for disclosing the personal user information you share with the platform in your own privacy policy. The platform does not write that disclosure for you.
Controller checklist before you ship
- Confirm your app's privacy policy names the subscription platform as a processor and describes the end-user data you send to it.
- Identify which user identifiers your app passes to the platform so a deletion request can be matched to a person.
- Keep a record of the lawful basis you rely on for processing subscription and purchase data.
- Know your escalation path: deletion requests and privacy questions go to the compliance contact, not to general product support.
- Read the privacy policy and the Data Processing Addendum so your own disclosures match the contractual terms.
Sending a deletion request
If a customer asks you to delete their data, you can send the request to the owner-supplied compliance contact: [compliance contact]. A useful request identifies the app, the end user, and the specific data to be removed, so the processor can locate the record without a back-and-forth. Treat this as distinct from a general privacy question: a deletion request is an action on a specific person's data, while a policy question is about how the service works. As a worked example, a request might read: app name, the user identifier your app passes to the platform, and the data categories to remove — nothing more is needed to start the lookup.
Documents to read
Two owner-supplied documents set out the terms: the privacy policy at [privacy policy URL] and the Data Processing Addendum at [DPA URL]. Read both before you finalize your own disclosures, because your controller obligations depend on what you actually send to the processor. A practical check is to compare the data categories listed in the addendum against the fields your app actually transmits; any gap is a disclosure you still owe your users.
Where to send privacy questions
Questions or concerns about privacy or GDPR go to the owner-supplied compliance contact [compliance contact] rather than to general support. Use that channel so the message reaches the team that handles data-protection matters. Keep the message specific: the app, the data category, and the question you need answered.
| Responsibility | Controller (you, the developer) | Processor (the subscription platform) |
|---|---|---|
| Decide why end-user data is processed | Yes | No |
| Publish a privacy policy disclosing shared data | Yes | No |
| Handle end-user data on the controller's instructions | No | Yes |
| Receive and action deletion requests | Routes the request | Processes the deletion |
| Sign or reference a Data Processing Addendum | Yes | Yes |
This map reflects the roles described on this page; it is not legal advice. Confirm your obligations with qualified counsel.
Frequently asked questions
Does using the subscription platform make me GDPR compliant?
No. The platform can be used by developers who fall under GDPR requirements, and it acts as a processor. Compliance depends on your own practices as the controller, including your privacy policy and how you handle end-user data.
Who is responsible for telling users their data is shared?
You are. As the controller of your application's data, you are responsible for disclosing the personal user information you share with the processor in your own privacy policy.
How do I request deletion of a customer's data?
Send the request to the owner-supplied compliance contact [compliance contact]. Include enough detail to identify the app and the end user so the record can be located.
Where can I find the Data Processing Addendum?
It is available at the owner-supplied URL [DPA URL], alongside the privacy policy at [privacy policy URL]. Read both before finalizing your own disclosures.