What Routing Forensics reads, and what it never keeps.

Plain answers to what a security reviewer asks first: what the product reads in your CRM, what it keeps, and what it never keeps.

What we read, and what we keep

What we never keep

• Lead, contact or opportunity records.
• Names, email addresses or phone numbers of your leads and contacts.
• Any free text from your records.

Every finding stores the query that proves it, so you can run it yourself in your own CRM.

What we show on request, and do not keep

When a signed-in person opens a finding and asks to see the records behind it, the app reads up to 50 record Ids and created dates live, through the same read-only connection, and shows them as links into your own CRM. Nothing from that read is stored. It is limited to 60 requests an hour per account.

How long results are kept

Results are kept for 13 months unless you choose otherwise, and older ones are deleted automatically. When an account closes, its data is deleted within 30 days.

How a number earns your trust

• Counts are checked against a second, independent route. If the two disagree twice, the check says it did not reconcile and shows no number.
• A run that cannot measure every check proves no fix and reopens nothing.
• A finding marked fixed stays awaiting verification until the next run proves it gone. A browser cannot mark anything fixed.

Access to the product

• Sign-in is by a single-use email link, valid for 15 minutes and stored only as a hash.
• Roles are Owner, Admin, Fixer and Viewer. The server checks the role on every change.
• Every change and every run is written to an append-only audit log.

The connection itself: security and permissions. Who else handles data: sub-processors.