Privacy Policy Version History

This page contains an archive of all versions of the Kalum Privacy Policy. We maintain complete version history for transparency. The current version is always available at the main privacy policy page.

All Versions

Version 2026-08-17

Current Version

Effective Date: August 17, 2026

Status: Active

Summary: Corrects and narrows §2.6. The separate website counter described in 2026-08-16 was retired, so the paragraph describing it is removed — no destination lookups are counted on kalum.app at all. §2.6 now also names the three non-identifying dimensions each count carries besides the destination (whether the request came from a verified copy of the app, whether a sign-in token was attached, and whether the device was iOS or Android), states that a small total may reflect a single lookup rather than many contributors, and discloses that one date is kept for the measurement as a whole — when the current counting period began — while no count carries a timestamp. No other privacy practices changed, and nothing new is collected.

Key Points:
  • Website destination counting withdrawn entirely; the paragraph describing it is removed
  • §2.6 now names every dimension a count carries, not only the destination
  • "No timestamp" scoped precisely: no count carries one; one counting-period start date is kept for the measurement as a whole
  • Wording corrected so it remains true of a destination looked up only once
  • No new collection, no new sharing, no change to retention, sub-processors or rights
View Current Version

Version 2026-08-16

Archived

Effective Date: August 16, 2026

Status: Superseded by 2026-08-17

Summary: Documents the aggregate demand measurement added in 2026-08. New §2.6 records that a destination rate lookup increments a per-destination counter holding the country calling code and at most three national digits, with no identifier, no timestamp and no per-event row — and states plainly that because it identifies no one, there is nothing within it to retrieve or delete on request. Also discloses the separate, country-level-only counter for lookups made on kalum.app. Links the NeuEra Apps Data Practices Charter as the governing standard. No other privacy practices changed.

Key Points:
  • New §2.6 "Aggregate Demand Measurement" — what is counted, and what is deliberately not
  • Country calling code plus at most 3 national digits; none at all where the calling code is 4+ digits
  • No identifier, no timestamp, no per-event row — the counts cannot be separated back out
  • States that an access or erasure request has nothing to act on, because the data identifies no one
  • Purpose stated: negotiating better rates on the routes people actually price, including abandoned lookups
  • Website lookups counted separately, at country level only, never combined with the app's counts
  • Links to the NeuEra Apps Data Practices Charter (Tier A) as the governing standard
  • No change to call metadata, transaction data, sub-processors, retention or rights
View Archived Copy

Version 2026-05-24

Archived

Effective Date: May 24, 2026

Status: Superseded by 2026-08-16

Summary: Updated to reflect the rollout of Apple in-app purchases on iOS and additional opt-in flows. Added Apple Inc. as a sub-processor for App Store payment processing, restructured the iOS/Android permissions section to list optional permissions invoked by the Stripe SDK (camera, photo library, biometrics, approximate location) and the new opt-in contact-import flow (iOS Contacts / Android READ_CONTACTS), removed absolute "does not collect" claims that no longer fit the optional flows, and noted that account deletion is now available in-app at Settings → Delete Account.

Key Points:
  • Apple Inc. added as a sub-processor for iOS in-app purchase processing (StoreKit)
  • Stripe role clarified: Android and web only (cards, Google Pay)
  • New §2.5 documents opt-in permission flows (contacts, camera, photo library, biometrics, location)
  • Android READ_CONTACTS added for opt-in "Import from contacts"
  • iOS permission section expanded to list all Info.plist declarations
  • Apple privacy policy added to third-party notices
  • Account deletion now available in-app (Settings → Delete Account)
  • Receipt-validation idempotency added to security controls
View Archived Copy

Version 2026-05-04

Archived

Effective Date: May 4, 2026

Status: Superseded by 2026-05-24

Summary: Aligned the Privacy Policy with the current product. Disclosed Firebase App Check and Firebase Crashlytics, clarified that contacts are manually added in-app (no device address-book import), added GDPR/UK lawful bases and EEA/UK rights, expanded data-retention disclosure for financial records, and enumerated the iOS/Android permissions actually requested by the app (no AD_ID, no location).

Key Points:
  • Sub-processors expanded: Firebase Auth, Firebase App Check, Firebase Crashlytics, Twilio, Stripe, Fly.io
  • Apple Pay and Google Pay disclosed as Stripe-routed payment methods
  • "Manually added" contacts only — no OS address-book import
  • GDPR / UK GDPR rights and lawful bases added
  • iOS and Android permissions explicitly listed; AD_ID confirmed removed
  • Financial-records retention up to 7 years for tax and anti-fraud
  • Standard Contractual Clauses for international transfers
  • No analytics, telemetry, or advertising SDKs
View Archived Copy

Version 2026-02-07

Archived

Effective Date: February 7, 2026

Status: Superseded by 2026-05-04

Summary: Initial privacy policy for Kalum prepaid VoIP calling service.

Key Points:
  • Phone number verification via Firebase Authentication
  • Call metadata collected for billing (destination, duration, timestamps)
  • Payment processing via Stripe (we never see card details)
  • Voice call audio handled by Twilio (we never access call content)
  • No advertising or third-party marketing
  • CCPA compliance for California residents
  • 18+ age requirement
  • Data security with encryption in transit and at rest
View Archived Copy

About Our Version History

We believe in transparency. Every time we update our privacy policy, we:

  • Create a permanent archived copy of the previous version
  • Update the effective date on the new version
  • List all versions on this page for your reference
  • Maintain this archive indefinitely

Our core commitment remains unchanged: we collect only the minimum data necessary to provide our calling service, and we never sell your personal information.