Heritage OS.Cloud

Privacy Policy

HeritageOS ("we," "our," or "us") is dedicated to protecting the privacy of institutional operators, curators, and public visitors who interact with our unpowered proximity edge hardware and cloud curation matrices. This Privacy Policy details how data is handled across our multi-tenant SaaS architecture.

1. Architecture Paradigm: Zero-PII Visitor Analytics

Our core framework is fundamentally engineered to deliver localized audio guides and curatorial information without building profiles on public visitors. For general visitors accessing information via our unpowered smart plaques (QR scans or NFC taps) or powered Audio Trigger Boxes:

• No Mobile Application Required: Visitors do not need to download heavy software or sign up for an account.
• Zero Personal Data Collection: We do not pull, scrape, or log Personally Identifiable Information (PII) such as phone numbers, names, device IDs, or MAC addresses from public visitors.
• Telemetry Constraints: Analytical interaction logs capture aggregate telemetry (e.g., localized node interaction frequency, language preference profiles, anonymous facility feedback) to map visitor flow without tracking individuals.

2. Data Collection for Institutional Operators

For authorized museum personnel, stadium curators, and system administrators logging into the HeritageOS Enterprise Console:

• Account Credentials: We log workspace identifiers, operator names, business emails, and cryptographic authentication credentials to secure administrative console routes.
• Operational History: Audit logs record parameter modifications, node text revisions, dynamic QR updates, and infrastructure reports generated by users.

3. Data Sovereignty & Regulatory Compliance

HeritageOS enforces absolute compliance boundaries based on regional operational tenants:

• DPDP Act Compliance (India): All operational tracking logs, infrastructure diagnostic metrics, and athletic pipeline inputs collected within the territory of India sit permanently within secure servers local to India.
• Cross-Border Segregation: Western multi-tenant workspaces (e.g., Canadian, European, or US museum tenants) route through logically isolated cloud nodes running across localized infrastructure zones.

4. Data Retention Parameters

We retain aggregate anonymous interaction data only as long as necessary to feed institutional command panels. Institutional operator account data remains stored securely until explicitly terminated by the subscribing organization or context curator.

5. Communication Channels

For questions regarding our enterprise privacy ledger, automated telemetry isolation, or to file clear operational inquiries, reach our administration team at: privacy@heritageos.cloud.