Data & security
A CRM that reads your mail should be explicit about what it reads.
Macklore only works because it sees sales activity. That makes the scope of access a product decision rather than a footnote. This page sets out exactly what is tracked, what it is used for, who can reach it, and what the system will never do on its own.
What is tracked
Four categories, each with a stated purpose and a stated limit.
If a signal does not help answer whether a deal is still alive, there is no reason to collect it.
Email metadata and thread content
How it is used
Used to detect replies, reply gaps, unanswered questions and who is engaged on a deal.
What stays out
Mail unrelated to a tracked deal or contact is not stored, and personal correspondence is never scored.
Call and meeting records
How it is used
Connection status, duration, attendees and whether a meeting was held, moved or dropped.
What stays out
Macklore does not record, transcribe or listen to call audio.
Document view events
How it is used
Opens, repeat opens and forwards of proposals, quotes and decks shared through Macklore links.
What stays out
No tracking is applied to documents you did not share through Macklore.
Contact and account records
How it is used
Names, roles, company details and engagement history, so a deal's stakeholder map stays accurate.
What stays out
No enrichment from third-party data brokers and no scraping of personal social profiles.
Ownership
Your pipeline data stays yours, and leaving is not a negotiation.
A CRM holds the record of every relationship your company has built. Treating that as a hostage is both wrong and bad business.
- Your pipeline, contact and activity data belongs to you, not to us
- Full export in open formats is available on demand, on every plan
- We do not sell, licence or share your data with third parties
- Your data is not used to train models for other customers
- On cancellation your data stays exportable for ninety days, then is deleted
- Deletion requests for individual contacts are honoured across records and backups
Stated plainly
Engagement scores are decision support. Nothing closes, drops or sends itself.
A score is a reading for a person to act on. It never triggers an irreversible action inside your pipeline, and it never puts a message in front of your customer without one of your reps reading it first.
No deal is auto-closed or auto-dropped by the system
No stage change happens without a named user behind it
No follow-up is sent without a rep pressing send
No forecast is submitted to anyone on your behalf
Practices
Encryption and access control, described without the badge wall.
These are the practices in place today. Where a formal certification is relevant to your procurement process, the contact page is the right place to ask about current status.
Encryption
Data is encrypted in transit with TLS 1.2 or higher, and encrypted at rest with AES-256. Mailbox access tokens are stored in a separate, restricted key store rather than alongside application data.
Access control
Role-scoped access with rep, manager and admin levels. Internal access to customer data is restricted to named staff, requires a logged reason, and is reviewed on a schedule.
Separation and backup
Each customer's records are logically separated. Backups are encrypted, kept to a defined retention window and tested by restore rather than assumed to work.
Least privilege on connections
Mailbox and calendar connections request the narrowest scope that makes activity capture possible. Sending happens from your own mailbox, only when a rep presses send.
The legal detail on processing, retention and your rights sits in the privacy policy.
Open the privacy policyQuestions
What security reviews ask first.
No. The connection is scoped to mail involving contacts and deals you track in Macklore. Threads that do not involve a tracked contact are not stored or scored, and there is no sweep of unrelated personal correspondence.
On managed infrastructure with encryption at rest, in a region agreed at onboarding. Enterprise agreements can pin a specific region where a residency requirement applies.
Yes, at any time and without asking us first. Deals, contacts, accounts, activity history, scores and score history export in open formats. Nothing about the export is gated behind a retention conversation.
No. Engagement scores are decision support. No deal is auto-closed, auto-dropped or silently re-staged, no follow-up is sent without a person pressing send, and no forecast is submitted on your behalf.
Yes. Enterprise agreements include support for your security questionnaire, architecture questions and any custom data processing terms your legal team needs.
Every score in this sample board can be traced to timestamped signals.
Bring your security questionnaire. We would rather answer it before you commit than after.
Architecture questions, data processing terms and residency requirements are handled by the people who built that part of the product, not by a form letter.
- Hexfield Interiors moved to at risk
- Varun Steelworks flagged hot
- 4 follow-ups queued for review