Privacy and your customers

Your portal collects personal data about the people who use your API: their names, email addresses, keys, usage and billing records. This page explains who is responsible for that data and the tools MicroAuth gives you to handle requests about it. It isn't legal advice, so check with your own advisor what applies to your business.

Who is responsible

• Your customers' data. You decide who can sign up on your portal and what you do with their data, so you are responsible for it. MicroAuth runs the portal and stores the data for you.
• Your own MicroAuth account. MicroAuth is responsible for the data about you and your teammates, such as your names, emails and sign ins. The privacy policy covers it.

Your privacy policy

Add a link to your own privacy policy under Portal, Links and code, Privacy policy. The portal shows it on the sign up page and in the footer.

Until you add one, the portal shows a short default notice instead. It names you as responsible for the data, using the business name on your connected Stripe account or "the team behind" your API's name, says MicroAuth runs the portal for you and links to the portal customers section of MicroAuth's privacy policy. The default notice is a fallback, not a replacement for your own policy.

Emails to your customers

MicroAuth emails your customers under your API's name, and only about their own account:

• Always sent. Sign in codes, invites, approval notices, security notices and payment problems, such as a failed payment or an ended plan.
• Payment confirmations. Credit added, automatic top ups, plan payments and refunds.
• Balance alerts. A low balance, and a balance that ran out.

Billing emails go to the team's admins and billing members. Each person can turn off Payment confirmations and Balance alerts under Email notifications on the portal's Account page, or with the Unsubscribe link in the email. Their choices are part of the data they can download. See emails to your customers for when each one is sent.

Saved cards

Card numbers stay with Stripe. For the card that automatic top ups charge, MicroAuth keeps a copy of the brand, the last 4 digits and the expiry month and year from Stripe, along with its Stripe payment method ID and when the cards were last synced.

This copy is cleared when the card is removed in Stripe, the customer is deleted in Stripe, you disconnect Stripe, or you erase the customer. The card appears in your Export data file, and in the portal download for the team's admins and billing members.

Requests from your customers

Most requests can be handled by your customers themselves on the portal's Account page, where they can:

• change their name, and change their email with a code sent to the new address
• see where they are signed in and sign out other devices
• choose which optional emails they get
• download their data as JSON, including their email settings
• delete their account

When someone asks you instead, open the customer under Customers. These tools need the admin or owner role in your workspace, and each use is recorded in the activity log.

Request	What to do
A copy of their data	Export data downloads one JSON file with the customer, its members and their sessions, keys, invites, the saved card, the balance history, daily usage and related activity
Fix their details	Ask them to change it on the portal, or edit the customer name and notes yourself
Delete one person	Remove next to the person under Portal users. Their portal account goes, and the team keeps its keys and billing
Delete the whole customer	Erase customer, described below

Erasing a customer

Erase customer is for deletion requests. It removes:

• the customer, its portal accounts, sessions, keys and invites
• its usage history and balance history
• pending emails to its members

It also replaces the customer's name and its members' names and emails in your activity log with labels such as "a deleted customer" or "Deleted user 4f2a9c", so the history of what happened stays without saying who. Any subscription is canceled.

With Also delete them in Stripe on, which is the default, the customer is also deleted in your connected Stripe account. Stripe keeps past invoices and payments, as it has to for tax and accounting. Turn it off if you need the Stripe customer, for example for an open dispute.

Delete customer is the quicker option for customers you no longer need. It doesn't scrub names from the activity log.

When a customer deletes their account

When the last member of a team deletes their account, the whole customer is erased as above and its customer in your Stripe account is deleted. A team with a paid plan has to cancel it under Billing first. When one member of a larger team leaves, only their portal account goes. Either way, your workspace's owners and admins get an email, unless they turn off Deleted portal accounts.

What we delete on our own

Some data is deleted on a schedule, whatever you do:

• Portal sign ups waiting for approval are deleted after 90 days if nobody approves them.
• The activity log is kept for 400 days, and the IP addresses in it are removed after 90 days.
• Invites are deleted 30 days after they are accepted or expire.

The full list is under retention.

Your own account

The same rights apply to you and your teammates. Under Account in the dashboard you can change your email, see your sessions, download your data and delete your account. See your account.