Security & proof, in plain terms

🧾How the proof works

When your client taps Approve, we record three things: the exact post they saw (caption and media), the moment they approved it as a UTC timestamp, and a SHA-256 content hash of the post.

Those become a PDF certificate. Change a single character of the post afterwards and the hash no longer matches — that is what tamper-evident means: the proof shows precisely what was signed off, not a vague "they said ok."

The client's IP is stored only as a salted hash for fraud-resistance. The raw IP address is not kept.

→ See the full anatomy of an approval proof, and a live sample you can verify

🇪🇺Where your data lives

• Media files are stored in EU object storage (Western Europe).
• The database is backed up continuously to EU storage, so a single server failure can't lose your records.
• SMMapprove is operated from Portugal (EU); processing is under GDPR.

⏳What we keep, and for how long

Your approval record — who approved, when, and the content hash — is kept as your proof.

The media itself (images and video) is removed after 7 days. The certificate and hash remain, so your proof survives without us holding large files longer than needed — which is also what data-minimisation under GDPR asks for.

🔒Your client's privacy

Your client approves on a normal web link — no account, no app, no tracking login. We collect the minimum needed to record the approval.

The approval page shows a short consent line with links to the Terms and Privacy Policy before anything is recorded.

🛡️Access & accounts

• Sensitive integration keys are encrypted at rest.
• Email is sent through an EU-authenticated sender (SPF, DKIM and DMARC aligned), so notifications land and can't be spoofed.
• No card is required to start, and your client's link is never a bot — always a plain web page.