AuthenticationMemberstack and the GDPR: agreement, role and data location.
Memberstack is a authentication tool. Most customers use it as a processor, it explains how to get its data processing agreement, and the data location depends on your account. Below: what to check and how to declare it.
Prefilled for you · Free to set up · No credit card
In short
- Category
- Authentication
- Usual role
- Usually a processor
- Data location
- Set per account or project
- Agreement
- Obtained through the vendor
What does Memberstack do with personal data?
Manage website member accounts, sign-in and access to restricted content. That is how Privacyboard describes a typical use of Memberstack, as a starting point you can edit.
The data usually involved: member names, email addresses, account identifiers, membership details and authentication metadata.
Is Memberstack a processor or a controller?
Most customers use Memberstack as a processor: it handles personal data on their instructions, for the purposes they set. That is the common reading for authentication tools and it is what Privacyboard suggests.
As a processor, it needs a written agreement with you under Article 28, and you should know which subprocessors it uses. Confirm the role against your own agreement, because the way you use a tool can change it.
Where does Memberstack store personal data?
Memberstack does not have one fixed location for every customer. Usually the US.
How to find yours: Memberstack’s documentation describes data storage.
Even when the main location is in the EU, ask whether subprocessors or support access involve a transfer outside the EEA, and record it if so.
Does Memberstack have a data processing agreement?
Checked on 1 November 2026. Vendors change their pages, so check the date.
Memberstack does not publish the full text of its data processing agreement on a public page. The reference page explains how a customer gets or signs it, usually from inside the account. Article 28 of the GDPR still requires a written contract, so get it and keep a copy.
What we noted when we opened the page: Hosted on the Memberstack docs domain. A separate U.S. DPA article exists.
A page that exists does not mean you are covered. Whether the agreement applies to you depends on your plan and on what you accepted, so record the decision yourself in your vendor list.
Open the Memberstack reference pageHow to declare Memberstack
- 1
In your privacy policy
Name Memberstack as a recipient, say what it is used for (manage website member accounts, sign-in and access to restricted content) and mention any transfer outside the EEA. Articles 13 and 14 ask you to tell people who receives their data.
- 2
In your vendor list
Add Memberstack with its purpose, the data involved, its role, its region and a link to the agreement. Privacyboard prefills all of this, you confirm or correct it.
- 3
In your processing register
Link Memberstack to the activities that use it, so each record shows its recipients. Article 30 asks the register to list the categories of recipients.
What to check before relying on Memberstack
- Confirm where user records are stored and whether you can choose the region.
- Check how long sign-in logs are kept and how users are deleted.
- Keep the provider in your privacy policy as a recipient of account data.
- Review the provider’s security documentation for the controls you rely on.
Questions, answered.
Is Memberstack GDPR compliant?
Privacyboard does not certify vendors. Compliance depends on how Memberstack is configured and used, on the agreement you have with it and on your own practices. What can be checked is documented here: it explains how to get a data processing agreement, the usual role and the data location. Read the agreement itself before relying on it.
Does Memberstack have a DPA?
Memberstack does not publish the full text of its data processing agreement on a public page. The reference page explains how a customer gets or signs it, usually from inside the account. Article 28 of the GDPR still requires a written contract, so get it and keep a copy. The reference page is https://docs.memberstack.com/hc/en-us/articles/11419466621083-Data-Processing-Addendum-DPA.
Is Memberstack a data processor?
Usually, yes. Most customers use Memberstack as a processor that acts on their instructions. Check your own agreement and how you use the tool, because the role can differ.
Where does Memberstack store data?
Memberstack does not have one fixed location for every customer. Usually the US. How to find yours: Memberstack’s documentation describes data storage.
Do I need to mention Memberstack in my privacy policy?
Yes, if Memberstack handles personal data for you. The GDPR asks you to tell people who receives their data (Articles 13 and 14). Name the vendor or its category, say what it is used for and mention any transfer outside the EEA.
How do I add Memberstack to my vendor list?
In Privacyboard, pick Memberstack from the catalog. The purpose, the data, the suggested role and a link to its agreement are prefilled, and you confirm each one. Creating a workspace is free.
Privacyboard is not affiliated with Memberstack. Names and logos belong to their owners and are used only to identify the tool. This page summarises public documents as checked on 1 November 2026; it is guidance, not legal advice, and it does not certify any vendor.