Privacy

    Last updated: 26 September 2026

    This notice describes the data flows that are evidenced in the current RepairHub Global website and application.

    1. Who is responsible for the service

    RepairHub Global is the public product brand. SwiftNest Systems operates repairhub.global and portal.repairhub.global.

    Privacy questions and requests can be sent to support@repairhub.global.

    2. Information collected on the public website

    The public website records page and campaign activity through Google Analytics. It also keeps limited first-touch information in session storage, such as the landing path, referral category or referring domain, and UTM campaign fields. RepairHub does not put complete referring URLs or IP addresses into that first-touch record.

    The pricing currency helper uses browser language and may ask ipapi for a country code. The selected currency and first-touch record are stored for the browser session.

    If you submit a contact, callback or RepairHub Sites form, the submitted details are sent to RepairHub's Supabase backend. Depending on the form, this can include your name, email address, phone number, shop name, message, location, current website and Sites project choices. The Sites form also records limited source and country information used to handle the enquiry.

    3. Information used by the RepairHub application

    Account and shop setup can include names, email addresses, authentication records, business contact details, staff roles, shop settings and subscription status.

    The service stores the operational information a shop enters to run its work, including customer contact details, bookings, repair records, devices, notes, parts, invoices, payment states and customer communications. Each shop chooses the business records it enters and how it uses them in its repair relationship.

    Support requests can include contact details, the issue reported and any information supplied to help resolve it.

    4. How the information is used

    The confirmed service uses are to provide authentication and account access, operate shop and customer workflows, maintain subscriptions and payment records, deliver requested emails, respond to enquiries and support requests, protect the service, diagnose faults, and understand public-site and campaign performance.

    RepairHub does not add a platform transaction fee to a shop's customer payments. Where a shop enables online payments, payment-provider processing and account terms remain separate.

    5. Service providers evidenced in the current product

    Cloudflare serves and protects the web applications. Supabase provides authentication, database, storage and server-function services. Google Analytics measures public-site usage. ipapi supplies the country code used for the pricing-currency suggestion. Stripe is used for RepairHub subscriptions and, where a shop chooses and completes provider setup, for shop/customer payments. Resend is used to deliver service and enquiry emails.

    A provider may receive the information and network data needed to perform its part of the service. A shop may also configure its own customer-payment relationship with Stripe.

    6. Browser storage and analytics

    RepairHub uses session storage for limited attribution and currency preferences. The application also uses local browser storage for interface preferences and similar bookkeeping. Google Analytics is loaded on public pages and may use cookies or similar browser technologies under Google's service operation.

    7. Your information and requests

    You can ask for information about personal data connected with you, ask for inaccurate information to be corrected, or raise a privacy concern by emailing support@repairhub.global. The rights available and any limits on them depend on the law that applies to the particular request.

    If the information belongs to a repair shop's customer record, RepairHub may need to involve that shop because the request concerns the shop's repair relationship and the information it entered.

    8. Changes to this notice

    This page will be updated when the service or its confirmed privacy arrangements change. The date below identifies the published version.