Security & Trust

We use reasonable technical and organizational measures designed to protect information entrusted to Creeper OS. Depending on the surface (website, web app, mobile app or desktop app), those measures may include:

• Encryption in transit for network connections where the platform is designed to use HTTPS or equivalent protected channels.
• Encryption at rest where the underlying cloud storage and managed services provide it.
• Authenticated access to application features and data.
• Access controls so that customer workspaces are separated in ordinary operation.
• Least-privilege principles for internal access to production systems.
• Hosting on protected cloud infrastructure rather than unmanaged local servers for the cloud-connected product.

These controls reduce risk; they do not eliminate it. Retail teams also play a part by choosing strong credentials and limiting who can open, void or export sensitive records.

A shop floor has many roles. A cashier should not have the same reach as an owner, and a store manager should not automatically control every branch. Creeper OS is designed around user accounts, roles and permissions so retailers can match access to actual responsibility.

• Strong authentication practices for signing in to cloud-connected accounts.
• Role-based access so billing, inventory, procurement, finance and administration can be separated.
• User permissions that merchants can grant, change or revoke as staff join or leave.
• Administrative controls for inviting users and managing who can change sensitive settings.
• Session handling designed to keep signed-in use practical without leaving accounts open indefinitely.
• Password, PIN and similar credential practices appropriate to the login method configured for a user.

We recommend unique logins for each person rather than shared owner passwords at the counter, and prompt removal of access when employment ends.

Application security is treated as part of how Creeper OS is built and maintained. Our practices may include:

• Secure development habits such as reviewing changes that affect authentication, permissions or data access.
• Keeping dependencies reasonably current when updates address known issues.
• Validating and constraining input on sensitive actions.
• Authorization checks so users only reach the records and actions their role allows.
• Security-focused testing when we change high-risk areas of the product.
• Error handling that aims to avoid exposing unnecessary internal detail.
• Logging and monitoring of operational and security-relevant events where implemented.

We do not claim that every release is independently penetration-tested or that testing runs continuously. When we undertake additional reviews, we do so as part of ordinary product hardening.

Creeper OS uses cloud infrastructure and managed services designed to provide scalable availability and security controls. The cloud provider’s facilities, identity services, storage and networking form part of the environment in which customer data is hosted.

Provider-level certifications describe that provider’s environment. They are not the same as an independent certification of Creeper OS itself. We configure and operate our application on top of those services, including access restrictions, environment separation where used, and operational logging.

Desktop and mobile applications may also keep local operational data to support counter-side use, including periods of limited connectivity. Protecting those devices — physical access, OS updates and who can open the app — remains part of store security.

We use backup and recovery practices intended to restore platform data if an infrastructure or operational incident affects availability. Backups exist to support Creeper OS continuity, not to replace a retailer’s own statutory or business-record copies.

Recovery steps depend on the nature of the incident. We do not publish fixed recovery-time or recovery-point numbers on this page. If your procurement process requires a discussion of continuity, our team can walk through the current operating model.

Security and operational events may be monitored and investigated. Coverage is not described here as a 24/7 security operations centre unless that capability is separately confirmed for your account.

When a suspected incident affecting Creeper OS is identified, our working process is:

1. 1

   Detection

   Identify unusual access, errors, reports from customers, or other signals that something may be wrong.

2. 2

   Investigation

   Determine scope, affected systems and whether customer information or store operations are involved.

3. 3

   Containment

   Limit further impact, including credential resets, access changes or service restrictions where needed.

4. 4

   Remediation

   Remove the cause as far as practicable and restore safe operation of the product.

5. 5

   Customer communication

   Notify affected customers when required by law or when we reasonably believe they need to take action.

6. 6

   Post-incident review

   Capture what happened and what should change in product, process or configuration afterwards.

Security is how we protect information. Privacy is how we explain collection, use, sharing and rights. They work together: technical controls are incomplete without a clear account of why data exists in Creeper OS in the first place.

Retailer-controlled customer records are especially important. A merchant decides what shopper information to store; we process it to provide the product. That distinction is explained in the Privacy Policy.

Read Privacy Policy →

If you believe you have discovered a security vulnerability affecting Creeper OS, please report it responsibly rather than publicly disclosing the issue. Responsible reports help us protect retailers and their customers.

Send a clear description of the issue, the affected surface (website, web app, mobile or desktop), and steps that are reasonably needed for us to understand it, to blastoutsolutions@gmail.com. Please do not access data that is not yours, disrupt service, or attempt to exploit a finding beyond what is needed to demonstrate it.

Creeper OS does not currently operate a public bug-bounty programme. We still appreciate good-faith research and will work to acknowledge and address valid reports.

Some functionality depends on third-party infrastructure or service providers, such as cloud hosting, communications or device platforms. Those organisations operate their own security programmes.

We do not claim that every vendor is certified to a particular standard, or that a vendor’s certification automatically extends to Creeper OS. We select and use providers as part of delivering the product, and we expect them to protect information according to their terms and our operational needs.

Security practices evolve as Creeper OS, its infrastructure and the threat landscape change. We update application versions, configuration and internal processes when doing so is a reasonable way to reduce risk.

Retailers can help by installing application updates when prompted, keeping store devices patched, and reviewing user lists after staff changes.

For security reports, trust questionnaires or related questions:

• BlastOut Solutions
• Email: blastoutsolutions@gmail.com
• Phone: +91 7010 537 325