Clarity about your information.
How Folio stores your data, publishes your card and handles your account.
Your draft and your account
The card editor automatically saves a draft and optimised images in your browser’s local storage. Account details, password hashes, session records, saved cards, contacts and team memberships are stored in the application database. Clearing browser storage removes the local draft; it does not delete your account.
What you choose to publish
Publishing makes the selected card details and images accessible to anyone with its URL. Hidden contact fields are excluded from the public card response. You can edit, unpublish or delete a card in your dashboard. A downloaded file cannot be withdrawn from someone else’s device.
Contacts and messages
When someone shares details back through your card, the information is saved in your contacts. The form requires permission to share. Contact enquiries are stored for follow-up. Only collect information you have permission to use.
Account protection
Passwords are stored as salted scrypt hashes. Sessions use HttpOnly cookies. Account APIs check ownership and request origin, and apply rate limits. These controls do not constitute a security certification. Keep the application on HTTPS and protect its database and backups.
Visits and cookies
Published card visits are counted once per visitor per card per day using a first-party visitor cookie and a hashed identifier. Login cookies keep your account session active. There are no advertising trackers in this application.
Free features and external services
Available features are free to use. No payment or subscription is created. Google sign-in requires configured OAuth credentials. Native wallet passes, paid plans, automatic CRM sync, SSO and AI enrichment are not included. Third-party tools have their own terms and privacy policies.
Your responsibilities and deletion
Only upload images and information you have permission to use. Do not publish sensitive information you do not want publicly accessible. Delete cards and contacts from your dashboard, or delete your account in Account settings. Deleting an account also removes its owned teams and published cards. Deployed operators must provide their legal identity, support contact, retention policy and jurisdiction-specific terms before commercial launch.