Skip to main content
Policy Document • Effective September 21, 2026

Privacy Policy for 7esaby (حسابي)

Designed from the ground up as a privacy-preserving, zero-authentication expense-splitting utility for iOS, Android, and Web.

Last Updated: September 21, 2026 • Jurisdiction: Egypt (Law No. 151 of 2020) • Zero-Account Architecture

1. Introduction & Core Philosophy

7esaby ("حسابي", "we", "us", "our") is engineered from the ground up as a privacy-preserving, zero-authentication expense-splitting utility. We believe that sharing a meal, splitting a bill, or settling shared group expenses should never require surrendering your personal identity, telephone number, email address, social media accounts, or passwords.

This Privacy Policy explains how 7esaby handles data when you use our mobile and web applications (the "App"), our optical character recognition ("OCR") receipt analysis services, and our peer-to-peer settlement display interfaces.

Architectural Guarantees:

  • No User Accounts: No passwords, phone OTPs, or social logins are ever collected, required, or stored.
  • Zero Cloud Image Persistence: Receipt images are processed in volatile memory (RAM) and immediately discarded.
  • No Financial Credential Collection: We never collect, process, or store credit cards, bank accounts, or InstaPay PINs.

2. Architecture & Identity Model (Zero-Authentication & Anonymous Device IDs)

  • No Account Registration: 7esaby does not require or support user account creation. We never ask for, collect, or store your email address, phone number, password, government ID, or contact book.
  • Device-Generated Identifier: When you launch 7esaby, a random, pseudo-anonymous Universally Unique Identifier (UUIDv4) is generated and stored solely in your device's local sandboxed storage (localStorage or secure local preferences). This identifier functions as your local device signature to maintain state across active dining rooms.
  • User Handle & Display Preferences: You may optionally specify a display handle (e.g., @handle) and an accent color. These preferences are stored on your device and synchronized to an anonymous database row keyed exclusively to your random device UUID. They are not linked to your legal name, physical identity, phone number, or email.
  • Host Tokens: When you create a bill, an ephemeral cryptographic host token is stored locally on your device. This token allows your device to edit bill items, manage guests, or delete the room without requiring administrative user accounts.

3. Camera, Photo Library & Receipt Image Processing (Zero Cloud Image Persistence)

  • Ephemeral In-Memory Processing: When you use 7esaby’s receipt scanner, you may grant permission to access your device's camera or select an image from your photo library.
  • No Cloud Image Storage: Receipt images are converted to binary data in volatile memory (RAM) and transmitted directly over TLS-encrypted connections to our stateless processing engine (powered by Google Gemini Vision APIs) solely for text and numeric extraction.
  • Immediate Discard: Once the line items, quantities, and totals are extracted into structured text/JSON, the image payload is immediately discarded from server memory (RAM). 7esaby does not operate persistent photo storage buckets, does not archive receipt photographs, and never writes your receipt images to disk or database storage.
  • Extracted Tabular Data: The resulting extracted tabular data (item titles, unit prices, quantities, and computed taxes/fees) is saved as plain text within the temporary bill room record so dining participants can split items.

4. Product Telemetry & Analytics (PostHog Integration)

  • Analytics Engine: We utilize PostHog to analyze product usage trends, measure application performance, and identify runtime exceptions.
  • Event Telemetry Collected: Event-level actions such as opening a room, scanning a receipt, toggling an item claim, or exporting a breakdown.
  • Distinct Identifier: PostHog telemetry is associated with your pseudo-anonymous device UUID (distinct_id). It is never correlated with advertising identifiers (IDFA or GAID), IP addresses (which are discarded upon ingestion), or personally identifiable records.
  • Encryption in Transit: All telemetry data is transmitted using modern TLS (HTTPS) encryption.
  • No Cross-App Ad Tracking: 7esaby contains zero third-party advertising networks, zero tracking pixels, and does not sell, rent, or trade telemetry data to data brokers or marketing platforms.

5. Financial Usernames & Payment Settlement Links

  • Display Only: 7esaby allows bill hosts and participants to save payment aliases (such as an InstaPay username or payment link) to facilitate peer-to-peer settlement.
  • No Financial Credential Collection: 7esaby never collects, processes, transmits, or stores bank account credentials, debit/credit card numbers, CVVs, expiration dates, OTPs, or financial account balances.
  • External Redirection: Tapping an InstaPay link simply launches the InstaPay application or copies the alias to your clipboard. All transactions occur entirely outside of 7esaby on regulated banking networks.

6. Data Retention & Automatic Expiration

  • Ephemeral Bill Rooms: Dining rooms and item breakdown tables are designed for transient social use. Room records and associated item claims are subject to routine database lifecycle purges once inactive or when explicitly deleted by the room host.
  • Local State Purging: You can purge your device identifier, local history, and active sessions at any time using the in-app "Reset Profile & Clear Data" control or our web Data Deletion Portal.

7. Third-Party Service Providers (Sub-processors)

We work with trusted infrastructure providers who adhere to strict data security and encryption standards:

Supabase

Cloud PostgreSQL database hosting for transient room records, item lists, and anonymous device handles.

Google Cloud / Gemini Vision

Ephemeral, stateless in-memory OCR text and numeric extraction (immediate RAM purge).

PostHog

Privacy-first application telemetry, performance metrics, and crash monitoring (EU-hosted).

8. Children's Privacy

7esaby does not knowingly collect or solicit personal data from children under the age of 13 (or under 16 in applicable jurisdictions). Because the App operates on an accountless architecture and does not collect personal identifiers, no child’s personal identity is knowingly stored. If you believe a child has provided data through our platform, please contact us immediately for prompt erasure.

9. Legal Rights Under Egyptian Law No. 151 of 2020 & International Standards

Pursuant to the Egyptian Data Protection Law (Law No. 151 of 2020) and international data protection frameworks, you have the right to request access to, rectification of, or erasure of any records associated with your interaction. You can autonomously exercise your right to erasure via the in-app "Reset Profile & Clear Data" function or submit a request on our Data Deletion Portal.

10. Changes to this Privacy Policy

We may update this Privacy Policy to reflect changes in our legal obligations or application architecture. Updates will be posted to this page with a revised "Last Updated" timestamp.

11. Contact Information & Data Inquiries

If you have questions, feedback, or data privacy requests, reach out to our team:

privacy@7esaby.app legal@7esaby.app support@7esaby.app