Privacy Policy

We handle two different kinds of personal data, in two different roles.

• Customer accounts. The people at the companies that use MicroSurveys (product managers and their teams) sign in to our console to build surveys and read results. For this data, MicroSurveys decides how it is used.
• Survey data. Our customers add our SDK to their own apps and websites to show surveys to their own users. For this data, our customer decides what to collect and why. We process it on their behalf and following their instructions.

If you answered a survey inside someone else's app, see If you answered a survey in an app.

When you create and use a MicroSurveys console account, we store:

• Your email address and name.
• If you sign in with Google or Microsoft: your account id with that provider and, from Google, your profile picture URL. We ask those providers only for basic sign-in details (your email address and profile), never access to your mail, files or calendar.
• What you tell us during onboarding, such as your company name, your role, and details about your app.
• Your projects and their settings: surveys, questions, targeting rules, themes, team members and invitations.
• A record of each sign-in attempt, including the IP address and browser user agent it came from. We use it to keep accounts secure and to diagnose sign-in problems.
• Anything you send us from the console, such as issue reports (with the page you sent them from, your browser user agent, and any files you attach) and feature requests.

Sign-in links and codes are stored only as one-way hashes. SDK keys are stored hashed for lookup and encrypted so you can view them in Settings.

If you connect Amplitude

If you connect your project to your own Amplitude account, we store your Amplitude API credentials encrypted, and use them only to import your event and property names so you can pick them when setting up survey triggers and audiences.

When a customer's app shows a survey through our SDK, we receive and store, for that customer:

• An identifier for the person: either the user id the app provides, or a random anonymous id the SDK generates on the device.
• User properties the app chooses to send, such as a plan or a language. The customer decides which properties, if any.
• When a survey was shown, whether it was dismissed, and the answers given, including any free text the person types.
• Device context: the platform (iOS, Android or web), the app's version, the operating system version, the device or browser language, and which in-app event triggered the survey.

The survey records we store do not include the person's IP address, and our SDKs do not collect location, contacts, or advertising identifiers.

Private by architecture

Our SDKs use no cookies. Deciding whether to show a survey, based on in-app events, audience rules and frequency limits, happens on the device itself. The app's events are not sent to us to make that decision.

To work offline and stay consistent across sessions, the SDK keeps on the device:

• the anonymous id it generated, and any user properties the app set;
• a copy of the project's survey configuration;
• trigger progress for that person, such as event counts and when a survey was last shown, so frequency limits hold;
• a short queue of survey views and answers that haven't been sent yet, which is cleared as they upload.

On the web this lives in the browser's local storage. In mobile apps it lives in the app's own on-device storage.

If a customer picks a Google font for their survey theme, our web and iOS SDKs download that font from Google Fonts when a survey is styled. Like any web request, this lets Google see the device's IP address. No survey data is sent with it.

MicroSurveys uses AI to read open-text answers: tagging themes and sentiment and writing summaries for our customers. To do this, we send Anthropic (the Claude API) the survey and question text, the open-text answers, and, to help read them, the same person's ratings in that survey and the platform, app version and in-app event that showed it.

• Before any answer is sent, we automatically remove email addresses (including spelled-out ones), phone numbers, payment card numbers and IBANs (bank account numbers), and replace them with placeholders. Other details a person may type, such as a name or a street address, are not detected.
• We do not send the person's id, their user properties, their language or their OS version to the model.
• Anthropic processes this data under its commercial terms, which do not allow it to train models on our data.

AI insights are on by default. A project's owner can turn them off in the project's Privacy settings, and nothing new is sent after that.

• To provide MicroSurveys: show surveys, store answers, and present results and insights to our customers.
• To run customer accounts: sign-in, security, support, and service emails.
• To keep the service reliable and secure: finding and fixing errors, and preventing abuse.
• To improve our website, docs and console, using the analytics described below.

On microsurveys.ai, our docs and our console, we use a few tools to understand how these pages are used and to catch errors:

• Amplitude, for product analytics: page views, sessions and clicks. Fields that show secret keys are masked.
• Hotjar, for heatmaps and session recordings, on our production sites only. Fields that show secret keys are excluded from recordings, and in the console all text is masked, so survey content, answers and email addresses never appear in them.
• Sentry, for error monitoring in the console. Sign-in tokens and other sensitive values are removed from URLs, and cookies, authorization headers and IP addresses are not sent.

Amplitude and Hotjar may set cookies or use similar browser storage on our own sites. None of these tools are part of our SDKs: they don't run inside our customers' apps and don't see the people who answer surveys there.

We use a small number of service providers (subprocessors) to run MicroSurveys: for hosting, AI insights, email, and the analytics above. They process data only to provide their service to us. The full list, with what each one does, is on our subprocessors page.

If you choose to sign in with Google or Microsoft, that provider confirms your identity to us under its own privacy policy.

Survey data belongs to the customer that collected it. Members of that customer's project can see it in the console.

We keep survey data for as long as the customer's project exists. When a project is deleted, its surveys, survey views, responses and answers are deleted with it. A project's owner can also delete one person's responses and survey views at any time from the project's Privacy settings.

• Copies of the answers we sent for AI analysis, and the replies, are kept for 30 days for troubleshooting, then deleted. They are deleted sooner when the answers themselves are deleted.
• AI survey summaries are replaced as new answers arrive; earlier ones are deleted after 90 days.
• Records of sign-in attempts, with their IP address and user agent, are deleted after 90 days.

We keep account data while the account is active. To have your account deleted, email [email protected].

Data travels to and from MicroSurveys over encrypted connections. Sign-in links and codes are stored only as hashes, SDK keys and connected-service credentials are stored encrypted, and keys are removed from our logs and error reports. Files attached to issue reports are kept in private storage and opened only through short-lived links.

Depending on where you live, you may have the right to access the personal data we hold about you, correct it, delete it, object to or restrict how we use it, and receive a copy in a portable format. You may also have the right to complain to your local data protection authority.

For your console account, email [email protected] and we will respond.

The company whose app or website showed you the survey decides what is collected and how it is used, and is responsible for your data. Please contact that company to access, correct or delete your answers. We help our customers respond to these requests.

We will update this policy as MicroSurveys changes, and change the “Last updated” date at the top when we do.

Questions about this policy or your data: [email protected].