Privacy and data choices

Updated October 19, 2026. This notice describes MayoCRM and the supporting services operated by Programming Securely.

Information used by this site

We store the contacts, conversation notes, tasks, deals, groups and workspace information you create. Shared workspace records are visible to members according to their permissions. The optional Luma assistant processes selected text to prepare summaries and drafts. If you connect a Google or Microsoft calendar, the app stores encrypted provider credentials and the calendar information you choose to synchronize. Disconnecting a provider prevents future access through that connection; it does not delete your account with the provider.

Supabase Auth handles account identity and sign-in. Session cookies or browser storage keep you signed in. Calendar providers process their own authorization flows; never enter their passwords into a support report.

Site analytics and technical logs

We use self-hosted Umami to understand visits and page usage. Where enabled, the site sends page paths and technical browser/device information through its analytics endpoint; URL query strings and fragments are excluded by the tracker configuration. Hosting, authentication and security services also process technical request information, which can include IP addresses, timestamps and failure details. The API gateway logs request URLs and activity, which can include contact search terms sent by the mobile apps. These logs support service operation, security and troubleshooting.

Software error reports

We use self-hosted Bugsink to investigate technical failures. The integration is configured to remove user identity fields, request headers, cookies, request bodies, URL queries and interaction breadcrumbs from error reports while retaining stack traces. Session replay and performance tracking are disabled. Error messages can still contain information produced by the application, so avoid including private information in report titles.

Support and feature requests

The Support / Feature Request form sends your request type, title, description, optional contact email and technical page context to our central support system. When a verified signed-in session is supplied, the report can also include your account identity. Administrators review requests, and an internal Slack notification can contain the request title and reference. Do not submit passwords, payment credentials, or private information about other people.

Optional beta testing

The Become a beta tester form sends your email address, signed-in account name and identifier, selected projects, consent and technical app context to Programming Securely’s beta interest list. We use this information to contact you about the beta tests you choose. Selecting all current and future projects gives permission to contact you about that wider selection. Joining this list is optional and is not required to use MayoCRM. To ask to leave the list or change your choices, use Support / Feature Request and include the email address you registered; we verify ownership before changing a registration.

Mobile app data

The iOS and Android apps use your MayoCRM account to save contacts you enter, conversation notes and follow-up tasks. Your account identity and these records are stored on the service, and signed-in session information is also kept on your device. Shared workspace access follows the same permissions described above. The mobile apps include the optional support and beta forms described in this notice. The website analytics and software error-report integrations described above are not included in the native apps; their requests still pass through hosting, authentication and security services that maintain technical logs.

Storage and sharing

Information is processed by the application and its hosting, authentication, storage and notification providers as needed for the features described above. Information you deliberately share is visible to the recipients allowed by the relevant feature. Linked third-party services have their own data practices. Access controls help restrict records; they do not make a deliberately public post or shared item private.

Retention and your choices

Use the application’s available delete and sharing controls to manage your own content. Removing a browser session or disconnecting an integration is different from deleting server-side content. Delete your account from Settings or the direct /delete-account page after signing in. This removes your profile, sign-in, personal workspaces and connected-calendar data. Shared records remain with their workspace after your author links are removed; text you contributed may still identify you. Shared workspace owners must have an existing member accept ownership before deletion. To request access, correction or removal of a support submission, use Support / Feature Request and include a contact email and any request reference. We verify ownership before acting; do not send a password. Shared records belonging to other people may need to be preserved or transferred rather than removed.

There is not currently one automatic expiration period for all records. Backups, operational logs and notification copies are separate from active application records and may persist after an item is deleted. We do not promise immediate removal from every copy. Downloaded files and information already received by other people are outside the app’s deletion controls.

This page will be updated when the service or its data controls change.