Consent, audit log and privacy records

Messaging customers creates obligations. These are the records Pingly keeps so you can answer “who agreed to what, and who did what” without going through screenshots.

Consent

When someone accepts your terms and privacy policy, Pingly records the exact wording they accepted — not just that they clicked. The consent log can re-derive a fingerprint of that wording and confirm it has not changed since, which is what makes the record evidence rather than an assertion.

• The version, the time and the raw browser details are all kept.
• Superseded wording is archived, so an old consent stays verifiable.
• A consent record is only ever written when somebody actually accepted something.

The audit log

Settings → Audit Log records administrative actions — who changed a setting, removed a user, exported contacts or altered a number. Keep it in mind for the two moments it matters: investigating something that went wrong, and answering a customer or auditor who asks how their data was handled.

Opt-outs and blocked contacts

• Opted out — excluded from every campaign and sequence automatically, permanently, until they opt back in themselves. See Contacts.
• Blocked — under Blocked Users, for numbers you do not want to hear from at all.

Limiting what your own team can see

Two per-person settings under Settings → Team matter here: hiding full phone numbers from a team member, and whether they may delete messages. Both are useful for outsourced or temporary staff. See Invite your team.

Where the formal detail lives

What Pingly stores, for how long, and how it is protected is set out in the privacy policy and the terms. This page is about the controls; those documents are the commitments.