Security & data

Security and data handling at AntCards

Clear, verifiable protection information

This page describes controls and behaviours that are present in the AntCards application today. It does not claim certifications or protections that are not configured in the product.

Encrypted connections

Production traffic is configured to redirect to HTTPS. HSTS, secure cookies, HTTP-only session cookies, and strict referrer handling are enabled by default when debug mode is off.

Passwords and form protection

Django stores account passwords using its PBKDF2 password hasher. Forms use Django CSRF protection, and public lead forms also use CAPTCHA, throttling, and duplicate-submission controls.

Role-based company access

Company workspaces use Owner, Admin, Manager, and Member roles. Management, approval, billing, and settings actions check the signed-in user's membership and required role.

Exports

Authorized users can export filtered captured leads as an XLSX file. Public card contact details can be downloaded as a vCard. A general company-data or event-analytics export is not currently available.

Company trial expiry

The Company trial lasts 30 days. When it expires, the subscription changes to expired and Company-paid features lock until a paid subscription is started. The expiry process does not delete existing company, card, lead, or event records.

Analytics choices

When analytics consent is required, optional GA4 and Microsoft Clarity scripts remain unloaded until the visitor accepts analytics. Advertising pixels are not currently loaded.

Need a security or data-handling detail that is not covered here? Contact AntCards support.