Secure web connections
Store Bounty public and account services use HTTPS so information in transit is protected between supported clients and the service.
Security at Store Bounty
Protect the account. Limit access. Report concerns quickly.
Security is shared work between Store Bounty, integrated providers and every business using the platform. This page explains the practical boundaries without claiming certifications we have not published.
Accounts and staff roles
Businesses should give each user appropriate access, remove access that is no longer needed and avoid sharing a single password across a team.
Connected providers
Payment processing is performed through integrated payment-provider flows. Provider charges, terms and controls remain distinct from Store Bounty subscriptions.
Collect with a purpose
Use forms, CRM and messaging only for information the business can justify, protect and handle under applicable privacy and marketing obligations.
Protect every surface
Use operating-system updates, screen locks and controlled physical access on phones, browsers and retail workstations used for Store Bounty.
Report suspicious activity
Send the affected account, time, observed behaviour and safe reproduction details. Never email passwords, private keys or full payment-card data.
Report a security concern →Your security checklist
Small operating habits prevent large avoidable problems.
- Use a unique password and keep recovery details current.
- Create individual staff access rather than sharing credentials.
- Remove former staff and unused devices promptly.
- Verify unexpected payment or account requests through a known channel.
- Report suspected compromise before continuing sensitive activity.
Responsible reporting
Give us enough to investigate safely.
Include the service, account identifier, timestamps, browser or app version and a concise reproduction path. Do not test against another customer’s data or disrupt production systems.
Email security report ↗