Privacy Policy

Last updated: 2026-04-27. This is a placeholder. Replace with the operator's real privacy policy before shipping to a real customer cohort.

1. What we collect

Account data: name, email, phone, KYC attestation reference, payment method metadata (brand, last 4 digits — never the full PAN), MSISDN + ICCID, and your plan + bundle balances.
Usage data: data, voice, and SMS events against your line, used for rating + bundle decrement.
Audit data: every read and write your account incurs is logged in audit.domain_event with timestamp, actor, channel, and (where applicable) the AI model that performed the action.
Chat transcripts: when you escalate via chat, the conversation is hashed (SHA-256) and stored under the resulting case for the CSR's review. Transcripts are archived 90 days after the case closes per our retention runbook.

2. What we do with it

We use your data to provide the service, charge your card on file, comply with telecom and KYC regulations, prevent fraud, and audit our own systems. We do not sell your personal data.

3. Third parties

KYC vendor. A signed KYC attestation issued by a regulated identity provider (e.g. Singpass) is submitted via the channel layer; we record the attestation reference, not the underlying ID document.
Payment processor. Card numbers are tokenised by a PCI-compliant processor; we store only the token, brand, and last 4 digits.
eSIM provisioner (SM-DP+). ICCID + IMSI are exchanged with the eSIM profile manager so your device can download the profile.
AI provider. Chat conversations are sent to an LLM hosted by our model provider (currently OpenRouter routing to a Gemma-class model). The provider does not retain our prompts beyond the policy stated in their data processing addendum.

4. Cookies + sessions

We set one cookie, bss_portal_session, holding an opaque session id. The session is HttpOnly, SameSite=Lax, and rotates past TTL/2. We do not use third-party analytics or advertising cookies.

5. Your rights

You may request a copy of your account data or its deletion at any time. Contact privacy@bss-cli.example (placeholder address). Some data (audit rows, regulatory reports) we are legally required to retain.

6. Security

All inter-service traffic carries an authenticated token; all customer-facing endpoints sit behind HTTPS in production. Login OTPs and step-up codes are HMAC-SHA-256-hashed with a server pepper before storage; we never log plaintext credentials.

7. Changes to this policy

We may update this policy from time to time. Material changes will be communicated via the email on file with reasonable notice.