Superbime
Data Collection & Storage Architecture
Effective Date: October 1, 2026
This Data Collection and Storage Architecture Document establishes a technical, structural, and legal disclosure regarding the ingestion, processing, multi-tenant isolation, cryptographic protection, storage, retention, and purge routines enforced across the Superbime Enterprise B2B Platform operated by Superbime Pvt Ltd and its corporate affiliates. This document functions as a technical and architectural companion to the Superbime Enterprise Privacy Policy and the Superbime Enterprise Terms of Use. While this document delineates the underlying technical data flows, encryption mechanics, and infrastructure safeguards, readers, enterprise procurement officers, and compliance auditors must refer directly to the Privacy Policy and Terms of Use for the complete legal framework governing statutory data subject rights, subscription licensing rules, administrative liability boundaries, acceptable use constraints, and contractual dispute resolution mechanisms.
1. Data Classification and Statutory Processing Capacities
Superbime operates under a strict bifurcated data capacity model in alignment with global data protection frameworks, including the General Data Protection Regulation, the UK General Data Protection Regulation, and the California Consumer Privacy Act as amended by the California Privacy Rights Act. With respect to all Customer Content submitted, processed, or generated within the platform, encompassing task state machines, ticketing records, form entries, file attachments, real-time messaging assets, and operational performance metrics, Superbime acts strictly as a Data Processor or Service Provider. The Customer organization acts as the sole Data Controller or Business, maintaining full legal ownership, administrative control, and responsibility for directing the scope of processing operations.
Superbime operates as a Data Controller solely with respect to a minimal dataset comprised of account administrative contact details, corporate billing records, and infrastructure security logs collected directly from Customer representatives and Authorized Users. This minimal data collection is executed under the statutory legal bases of contract performance, legitimate security interests, and legal recordkeeping compliance. All Customer Content, private messaging streams, and operational analytics are encrypted using AES-256 standards at rest and TLS 1.3 in transit, with data cryptographically isolated per tenant as detailed in Section 2: Data Ingestion, Processing, Storage, Access, and Lifecycle Across System Capabilities. Account and identity data, including passwords hashed via salted algorithms, are maintained within encrypted persistent storage volumes. Infrastructure security logs are segregated within isolated, write-once logging environments subject to automated rotation schedules ranging between ninety and one hundred eighty days.
2. Data Ingestion, Processing, Storage, Access, and Lifecycle Across System Capabilities
The platform operates an integrated microservices architecture executing within deterministic tenant isolation boundaries, where data ingestion varies dynamically based on administrative toggles and active platform features configured by the Customer. Within identity and access workflows, data is ingested directly during workspace setup, directory synchronization, user provisioning, or Single Sign-On SAML and OAuth assertion handshakes via TLS 1.3 encrypted API endpoints, as well as via passive client-side agent headers when conditional access tracking is explicitly activated by the Customer administrator.
The dataset processed within identity operations includes Authorized User legal names, professional work email addresses, corporate telephone numbers, job titles, departments, profile avatar binaries, SAML assertion tokens, salted password hashes utilizing Argon2id or bcrypt algorithms for non-SSO accounts, Role-Based Access Control permission maps, and signed JSON Web Token session claims. Where security logging features are enabled, the system automatically records technical device telemetry, including hardware device identifiers, internet protocol addresses, operating system version builds, browser user-agent strings, referring URLs, login timestamps, interaction timing, and session duration logs.
This identity data is processed strictly to authenticate user identities, enforce role-based authorization vectors, execute conditional access controls, maintain session security, and provide automated threat detection. All identity records are stored in AES-256 encrypted relational database schemas and high-speed in-memory session caches hosted in secure tier-four cloud data centers operated by AWS, GCP, and Azure, with profile images persisted in server-side encrypted object storage buckets. Access to identity data is governed strictly by tenant-scoped API gateways validating cryptographically signed JWT claims and RBAC maps, ensuring zero administrative or analytical access by cloud infrastructure hosts. Upon contract termination, all account credentials, identity maps, and user profiles are permanently erased and rendered unrecoverable within fifteen calendar days via tenant storage key destruction, while transient security logs are segregated in isolated logging environments and shredded on a rolling ninety to one hundred eighty-day lifecycle, or immediately wiped via an emergency cryptographic purge in the event of an age floor breach.
Within core task and workflow features, data is ingested in real-time as Authorized Users create tickets, submit custom forms, reassign workflow items, upload file attachments, and transition state machines across secure HTTPS and WebSocket endpoints. Data processed as Customer Content within this domain includes user task assignments, ticketing state machine updates, custom form entries, assignment matrices, SLA compliance tracking logs, operational approval records, file attachment properties, and project association trees. This data is processed exclusively to serve as the enterprise system of record for Customer project management, workflow automation, SLA tracking, and ticket lifecycle orchestration.
All core workflow data is persisted across AES-256 encrypted database tables and document stores in secure cloud data center regions, with file attachments residing in server-side encrypted object storage buckets assigned explicit tenant identifiers. Access to workflow records is strictly restricted to authenticated Authorized Users belonging to the contracting Customer Workspace whose assigned RBAC permissions grant explicit visibility into the target project group or ticket state. Customer administrators retain self-service deletion rights over task items during the active term, and upon Master Services Agreement termination, all core task records, schema entries, and attachments are cryptographically purged within fifteen calendar days through the destruction of the tenant's primary encryption keys.
Within real-time messaging capabilities, data is ingested via real-time WebSocket streams and secure REST API calls as Authorized Users transmit synchronous and asynchronous channel communications, direct chat messages, thread replies, presence indicators, and interactive ticket card interactions. Ingested data includes direct message contents, channel chat logs, thread interaction trees, file attachment properties, online or offline presence status indicators, and embedded interactive card objects. This data is processed solely to enable synchronous and asynchronous team collaboration, real-time presence awareness, and context-driven operational discussions. Messaging data is encrypted at rest using AES-256 standards within dedicated, cryptographically isolated messaging stores and memory caches situated across secure cloud data center regions.
Access to messaging data is restricted exclusively to active human participants in the specific conversation thread or channel within the native application user interface. All real-time messaging assets are ingested as cryptographically shielded private user assets that are completely isolated from administrative export tools, corporate compliance dumps, and court-order extractions. Under no circumstances—including corporate management demands, internal audits, civil litigation, criminal proceedings, or binding judicial subpoenas—shall Superbime extract, decrypt, or disclose employee messaging data to Customer management, government bodies, or third parties. Messaging assets are retained according to workspace policy during the active subscription and are completely destroyed within fifteen calendar days of contract termination via automated tenant cryptographic key destruction.
The platform compiles organizational analytics and performance metrics by passively ingesting time-series event streams off the internal system event bus, processing time-stamped telemetry generated during ticket state changes, task updates, and workflow resolutions. Data processed within this statistical domain includes ticket resolution velocity, task completion rates, Key Result Area monitoring outputs, and operational productivity analytics. Within the platform architecture, these statistical metrics are directly attributed and tied to individual Authorized Users inside the system environment rather than utilizing aggregated or proxied data models, enabling precise internal productivity evaluation. These metrics are processed solely to calculate and display operational performance statistics to designated Customer administrators within the native platform user interface.
Analytics data is stored in AES-256 encrypted time-series databases and analytical caches located in isolated secure cloud data center clusters. Access to these metrics is strictly restricted to authorized Customer administrators within the secure native application panel. Built-in application guardrails prohibit these individually attributed metrics from being exported, extracted, downloaded, queried via external APIs, or transmitted outside the secure application interface, and Superbime personnel hold zero access rights to these statistics. All organizational analytics and performance metrics are cryptographically erased alongside all tenant workspace data within fifteen calendar days of Master Services Agreement termination through automated storage key destruction.
General administrative and billing data is ingested directly from Customer corporate representatives during workspace onboarding, subscription ordering, feature enablement selection, and billing transactions. Data processed includes workspace resource quotas, feature enablement matrices, subscription tier configurations, designated billing contact names, corporate email addresses, physical office addresses, tax identification numbers, payment transaction metadata, global security policy toggles, system health logs, and administrative audit trails. This data is processed to provision workspace accounts, enforce subscription tiers, execute billing obligations, maintain system health, and fulfill legal accounting mandates.
Administrative data is stored in encrypted relational databases and isolated security logging volumes located in primary secure cloud hosting facilities. Access is restricted solely to authorized Customer administrators and designated Superbime billing and security personnel operating under strict RBAC constraints. Corporate billing transaction records are retained in isolated accounting vaults for statutory retention windows mandated by applicable tax and corporate recordkeeping laws. System health and administrative audit logs are overwritten on a rolling ninety to one hundred eighty-day lifecycle.
3. System-Wide Offboarding, Backup Destruction, and Emergency Purge
Master Services Agreement termination triggers an automated, system-wide offboarding pipeline executing cryptographic key destruction within fifteen calendar days, rendering all database schemas, active volumes, and persistent storage mathematically unrecoverable across the entire workspace boundary. Secondary tenant data residing within automated rolling system backups is rendered unreadable instantly upon primary tenant key destruction, with underlying backup media permanently overwritten pursuant to automated cloud backup rotation lifecycles. Furthermore, Superbime maintains an overarching system safeguard: if verified notice confirms an age floor breach under Section 2, Superbime reserves the right to execute an immediate, unilateral emergency cryptographic purge, permanently deleting the violating workspace database without prior notice or financial liability.
4. Subprocessor Oversight, Judicial Protocols, and Escalation Channels
Superbime maintains a list of vetted infrastructure subprocessors operating under binding data protection agreements. Superbime provides enterprise Customers with at least thirty days' administrative notice prior to engaging any new subprocessor to host or process Customer Content, during which Customers may object on reasonable data protection grounds within fourteen days. Where Superbime is served with a binding judicial court order, search warrant, subpoena, or mandatory statutory directive requiring data production, legal compliance is contractually and technically limited strictly to base operational data, ticket state records, and task metadata processed exclusively by the Core module. Direct messages, channel communications, and thread interactions are treated as cryptographically shielded private assets that shall not be extracted, decrypted, or disclosed to any third party, government authority, judicial body, or Customer management representative under any circumstances.
In the event of a confirmed Security Incident resulting in verified unauthorized access or exposure of Customer Content, Superbime shall notify the Customer’s primary administrative point of contact without undue delay and no later than seventy-two hours following internal confirmation. Superbime provisions dedicated operational and privacy contact channels to enterprise Customer organizations with specific contact addresses communicated during workspace onboarding and set forth on all official billing invoices. Formal legal correspondence and physical service of process are directed to the regional corporate physical address designated on the Customer's official billing invoice or Master Services Agreement.