RepairFlow · Updated 4 November 2026

Privacy information

This page describes how the current RepairFlow deployment handles information. The repair business chooses which customer records to enter and who may access them. Its own privacy information also applies to the repair service.

Information used by the app

• Sign-in identity: an account identifier and, when provided through sign-in, your name and email address.
• Shop records: customer contact details, device descriptions, repair notes and dates, photos, quotes, costs, payment entries, invoices, warranty records and activity history.
• Business operations: branches, staff access, stock, suppliers, purchases and expenses.
• Browser preferences and session state, plus hosting and network diagnostics used to operate and troubleshoot the service.

These records support repair management, access control, customer tracking, stock management, reports and backup exports. Supabase handles sign-in and verification emails. Do not enter your email password or verification codes in a repair record.

Where information is handled

Vercel hosts the current independent application and its server endpoints. Supabase provides authentication, PostgreSQL record storage and private photo storage. This project's database is configured in Frankfurt, Germany. Staff invitations are stored with the application's access records. Earlier deployments or downloaded backups may retain separate copies; moving to this deployment does not by itself delete those copies.

Hosting, authentication, email delivery and storage providers may process service data in other locations according to their own terms. This page does not claim that every copy, log or photo stays in Germany.

Connecting a Shopify store

If you connect a Shopify store, RepairFlow verifies the store and its owner, and records the store identifier, domain, name, currency, owner user identifier and installation state. It can display product variants, quantities and this app's subscription status from Shopify. Viewing the catalog does not copy products into RepairFlow stock or change Shopify quantities. Checking subscription status does not create a charge.

Shopify ID tokens and online access tokens are used during requests and are not saved in RepairFlow records or browser preferences. Uninstalling disables the Shopify connection; it does not delete the existing standalone RepairFlow workspace. Customer access/deletion and shop deletion notifications enter a durable processing queue. The shop owner reviews which manually entered records belong to the requester. Processing can remove personal details and photos, redact related financial snapshots, and prepare a private data export. Financial amounts and minimal replay-prevention records remain. Prepared privacy exports stop being accessible after seven days. Automatic request processing and physical cleanup depend on the scheduled worker running successfully; a stopped worker can delay cleanup even after access to an export has expired. A received notification or an empty request list does not prove that processing is complete. Shop records are not automatically purged on a fixed commercial schedule; supported deletions remain under the shop owner's control, subject to financial, legal, security and provider-backup retention requirements.

Who can see records

Owner accounts can access their workspace. Staff access depends on the role, branch and assignment set by the owner. Providers and the deployment administrator have the technical access needed to operate the service.

A person with a valid tracking link can view the repair reference, device description, repair status, relevant dates and shop contact details. That view excludes the customer's contact details, internal costs and payment ledger. Treat tracking links as private, and avoid entering sensitive information in the device description.

Retention, exports and deletion

The application does not automatically expire shop records after a fixed number of days. Signing out, exporting a backup or disabling a staff member does not delete the underlying records. Some operational records can be deleted in the interface; financial, invoice and stock history have restrictions, and copies may remain in related history, invoices, exports or service backups.

Owners can export shop records from Settings. A full v2 shop backup includes available repair photos as well as records and payment ledgers. Full recovery is restricted to the same owner and an empty workspace; it does not merge with an operating shop. Legacy v1 shop backups and ticket-only copy backups exclude photo files. A dedicated privacy export includes photo contents that are still available; an unavailable photo must be reviewed before the request is fulfilled. Downloaded exports are stored wherever you save them, outside the app's access controls.

Browser storage and demo mode

The app stores language preferences and sign-in session credentials in local browser storage so you can return to your account. Temporary sign-in verification state is stored in the browser session. Use Sign out to remove the saved session from this browser; closing a tab alone may leave you signed in. Demo records are held in the browser session and are separate from live shop records. Shared devices and downloaded files need their own protection.

Questions about your information

If you are a repair customer, contact the repair business using the details on your receipt or tracking page to request access, correction or deletion of your customer information. The business must consider the request together with its record-keeping obligations. Shop owners can export and correct supported records in the app and control staff access.

Service operator: Akrama George Keyrouz, trading as AGK RepairFlow. Support and privacy contact: akramakeyrouz@icloud.com. Prepared privacy exports stop being accessible after seven days; cleanup of the stored export requires the worker to run successfully. RepairFlow otherwise keeps shop records until the shop owner uses a supported deletion or the service processes an applicable deletion request; financial, invoice, stock, security and provider-backup records may remain where operational or legal retention requires them. This page describes the service's current handling and does not by itself claim compliance with every privacy law.