FAQ - SecureBin
Common questions about SecureBin security, expiry, and how shares work.
How secure is SecureBin?
Every submission is sealed with 256-bit authenticated encryption, expires by time or views, is audit-logged, and lives in your business's own isolated database.
Can SecureBin staff see my submitted content?
Share payloads are stored encrypted, with no intentional plaintext retention after submission.
What happens when a share expires?
It stops resolving and the data is deleted — cleanup runs on a schedule and again the moment an expired link is opened.
Is SecureBin a payment processor?
No — SecureBin handles the secure hand-off: your customer's details reach you encrypted, screened, and verified. We're not a payment processor; you keep processing payments exactly as you do today, and your existing card-scheme and PCI DSS arrangements continue unchanged.
Why should I trust the claims on this site?
Every security claim maps to a named capability in the product source, and an automated audit fails our release checks when copy drifts from what the product actually does.