Process Mapper

Privacy Policy

Last updated 4 November 2026

Who is responsible

For the content a company puts into Process Mapper, that company decides what is collected and why, and Ethan Mahabir, trading as Process Mapper processes it on its behalf. For account and sign-in details, and for the running of the service, Ethan Mahabir, trading as Process Mapper is responsible. Questions and requests: privacy@getprocessmapper.com.

We aim to meet the Data Protection Act, 2011 of Trinidad and Tobago, and to treat personal information the same way wherever our users are.

What we keep

  • Owners and Facilitators: email address, the company they belong to and their role, when they were invited and first signed in.
  • Participants: the name and department they type when joining a Workshop, and their Maps. They get a secret return link; we keep only a scrambled form (hash) of it.
  • Content: Workshops, Maps (process steps, who does them, pain points), SOPs and approved versions of Maps.
  • A record of who did what: approvals, edits by Owners and Facilitators, team changes and settings, with the email of the person who did it and when (the audit log).
  • Sign-in and sign-up requests: the email (and company name for sign-ups) and the network address (IP address) they came from, used to stop abuse.
  • Usage counts: how many AI uses and exports each company made, and what the AI uses cost. No content is kept in these.

What we don't keep

Photos and PDFs sent for Capture are read by the AI model and then dropped; they are never saved. There are no passwords. We don't use advertising, tracking or analytics cookies, and we don't sell personal information.

Why we use it

Only to provide Process Mapper: to sign people in, show each company its own work, keep processes and their history, send the emails the service needs (sign-in links, invitations, account approval), keep the service secure, fix errors, and count usage for fair limits and future pricing.

Who else handles it

We use these service providers to run Process Mapper. They process data only to provide their service to us:

  • Vercel Inc. (United States): hosts the website and runs the app.
  • Supabase Inc. (database hosted in the United States, us-east-1): stores the database and handles sign-in.
  • Anthropic PBC (United States): the Claude AI model, used for Capture, suggestions, To-be drafts and SOPs.
  • Resend (United States): sends sign-in links and app emails.
  • Functional Software Inc., trading as Sentry (United States): receives error reports, scrubbed of what people typed, email addresses and IP addresses.
  • GitHub Inc. (United States): runs the nightly backup and keeps the encrypted backups.

This means personal information is stored and processed in the United States.

Cookies

  • Sign-in cookies, so Owners and Facilitators stay signed in; you are signed out after 4 hours without using the app.
  • A Participant's return cookie for each Workshop they join, kept for 60 days, so they can come back to their Maps on the same device.
  • A language cookie, kept for a year, remembering English or Spanish.
  • Your light or dark choice and editor preferences, kept in your own browser only.

Your choices and rights

You can ask to see, correct or delete personal information about you, or object to how it is used, by writing to privacy@getprocessmapper.com. Participants should usually ask the Facilitator or company that ran the Workshop, who can edit their Maps or delete the Workshop; we will help them. We answer within 30 days.

Security

Each company's data is kept apart by rules in the database itself, connections are encrypted, sign-in uses email links rather than passwords, and backups are encrypted. No system is perfectly secure; if a breach affects your data, we will tell the affected Owners promptly.