Aptiro gives you controls that map to common GDPR tasks for people in your CRM: why you may hold a contact's details, stopping outreach, never re-importing someone, permanently erasing them, and exporting what you hold for a subject-access request. This page says what a customer can do, where, and who may do it. It is not legal advice. Terms and privacy wording for the product are to confirm with Aptiro.
Lawful basis
Every contact can carry a lawful basis: why your organisation may hold and use that person's details.
| Stored value | What you see in the app |
|---|---|
| Legitimate interest | Legitimate interest (B2B prospecting) |
| Consent | Consent (they opted in) |
| Contract | Contract (existing customer or supplier) |
Where you set it:
- On create or edit of a contact (Contacts, or the account's contact form).
- On a CSV import: one basis for the whole batch, applied only to contacts the import creates. A row that updates an existing contact keeps the basis already on file.
- A new contact from a website form is recorded as consent, with the form name as the source.
When the basis is consent, you can also record where consent came from and a consent date. Who may create or edit contacts is controlled by your role's contacts permissions.
Do not contact
Marking a contact Do not contact (with a reason) takes them out of any active sequence enrolment and keeps them out of new outreach that would message them. Calendar invites refuse a do-not-contact address. A later website form from the same email leaves the mark in place.
Where: the contact drawer or contact form (Mark / Remove). Who: anyone who can edit that contact.
Never re-import (suppression)
When you delete a contact you can tick Never re-import this person. When you erase a contact (below), they are always put on that list. Aptiro stores one-way fingerprints (from email, and from name plus company domain), never the email or name themselves. Imports and enrichment skip anyone on the list.
Where you manage the list: Settings > Data protection. The list shows kind (email, or name and company), reason (erased; deleted, never re-import; or dismissed) and date. It never shows who the person was.
Who may list or lift entries: permission to erase contacts (contacts:erase),
which built-in owner and admin roles hold. Lifting an entry lets that person
be imported again.
Erasure
Erase (GDPR) permanently removes the contact and scrubs personal details that other tables held about them (for example activity text, outreach drafts and calendar attendee data tied to that person). The account and its business history stay. Erasure also writes the suppression fingerprints and a record that an erasure happened (without naming who was erased).
Where: the row menu on Contacts (and equivalent contact actions where shown). Who: permission to erase contacts, at a scope that can reach that contact. Built-in owner and admin roles have it; a custom role can be given "Full and GDPR" on contacts. Erase is separate from ordinary delete.
Subject-access export
Subject-access export downloads a JSON file of what Aptiro holds for one contact, for answering a data-subject request. It does not erase the contact.
Where: the row menu on Contacts. Who: permission for subject-access export on contacts (owner and admin by default; custom roles can be granted it).
Related
- Import contacts from a CSV (lawful basis on import, never re-import skips)
- Sync Google Calendar (erasure and calendar sync)
- Invite your team and manage roles
- Set up an authenticator