Skip to privacy policy

Revival Automotive

Your information.
Your privacy.

Who is responsible for your information?

This policy explains how Revival Automotive handles personal information when you browse our website, contact us, enquire about detailing or vehicle consignment, or use My Revival. It is drafted with South Africa’s Protection of Personal Information Act, 2013 (POPIA) in mind.

For privacy questions and requests, email revivaldetailing@gmail.com. This is the privacy contact confirmed by the owner; general enquiry addresses elsewhere on the site remain separate.

Information we collect and where it comes from

  • Enquiries and correspondence: your name, email address, telephone or WhatsApp number, message, requested service and information you choose to share. The contact and consignment links open your email or WhatsApp application; the current contact page does not submit a general contact form.
  • Detailing and appointments: contact and address details, vehicle details, chosen services and extras, preferred or booked dates, prices, customer notes, booking references, status and service history. Available fields depend on the booking flow enabled for your account.
  • Vehicle sales and consignment: vehicle make, model, year, mileage, condition, location, history, photographs and your contact details supplied in conversation. Please avoid sending identity documents, bank details or unrelated personal information in an initial enquiry.
  • Accounts: your name, email, phone, address, account identifier, sign-in provider and profile timestamps. Passwords are submitted to Firebase Authentication for email/password sign-in, rather than stored in the website’s customer profile records. Google sign-in supplies the identity information made available through that sign-in process.
  • My Garage and saved content: vehicle make, model, variant, year, colour, category, size, registration, optional VIN and nickname; saved cars, reviews and watch/read lists. Staff can record vehicle classifications and link detailing records. Private vehicle photographs are supported by an optional feature.
  • Reviews and media: customer review names, ratings, text, source links and publication choices; photographs, videos and vehicle stories supplied to or selected by Revival. Some published reviews come from public Google reviews rather than directly from a website form.
  • Technical information: IP address, browser/device details, requested resources and related service or security metadata may be processed by hosting, authentication, media and other services when your browser connects to them. Local browser storage is described below.

Information may come from you, your sign-in provider, authorised staff recording your instructions or work performed, and public review sources. Only provide another person’s information when you are entitled to do so. Do not submit sensitive personal information unless specifically requested through an appropriate channel.

Why we use information

We use information to respond to enquiries, discuss vehicle representation, arrange and deliver detailing, manage availability and bookings, maintain customer and vehicle records, provide account access and saved lists, send account or service messages, and resolve questions or disputes. Staff use the admin systems to manage these records, review vehicle eligibility and update service history.

Public showroom, gallery and review content supports the automotive and media services described on the site. Account creation or a service enquiry does not itself give permission to publish private contact information, VINs or identifiable customer photographs for marketing.

Where applicable, POPIA permits processing based on consent; steps requested before entering a contract or performance of a contract; a legal obligation; or the legitimate interests of Revival, a customer or another person, subject to the Act’s limits and rights of objection. A lawful basis must fit the particular purpose; submitting an enquiry is not blanket consent to unrelated uses.

What you need to provide

Browsing public pages does not require an account. You choose whether to contact us or supply optional details. Required fields in an enabled form are identified in that form; without the details needed to identify you, respond or arrange a service, we may be unable to fulfil that request. You can ask why information is needed before providing it. The website does not currently collect online card payments through a checkout.

Who receives information

Information is available to authorised Revival personnel for their work and to the services used to provide the website. Their roles vary: some process information for Revival, while services you choose to use, such as social platforms, also process information under their own terms.

  • Google Firebase / Google Cloud: authentication, customer and booking records in Firestore, and optional callable backend services. App Check/reCAPTCHA is available for configured protected services.
  • EmailJS and the connected email service: verification and welcome messages, and appointment notifications where enabled. Name, email, verification codes or relevant booking details are sent for the corresponding message. The owner must confirm the connected mailbox provider and provider-side retention.
  • Spotify/Anchor, YouTube and podcast feed services: media, artwork and feed delivery. The podcast feed can fall back to rss2json, AllOrigins or corsproxy.io. These requests disclose connection metadata to the provider; the feed request is not intended to send your account profile.
  • WhatsApp/Meta, email and external platforms: clicking an enquiry, social or media link takes you to that provider. Messages and attachments you send are then processed by that channel and received by Revival. Apple Podcasts and other linked platforms apply their own privacy terms.

Publicly published vehicle listings, photographs and reviews can be seen by visitors, search engines and sharing platforms. Information may also need to be disclosed where lawfully required, to protect legal rights, or to advisers engaged for a specific matter. This does not authorise unrestricted sharing.

Storage and retention

Account, Garage, saved-content and booking records are stored in Firebase services. Enquiries sent by email or WhatsApp are also held in those communication systems and may be recorded by staff for service delivery. Media is stored or delivered through the website’s assets and configured image services. Backups, logs, message copies and provider records may have separate retention arrangements.

Removing a Garage vehicle archives it in the current implementation; it does not erase its historical service references. Removing a customer profile through the admin interface does not itself delete the Firebase Authentication account. There is no verified automatic deletion schedule for all personal records.

The retention approach to be approved is to keep identifiable information only while needed for its stated purpose or a lawful retention requirement, then delete, de-identify or restrict it as appropriate. This draft does not assert that a complete retention/deletion programme is already implemented.

Cookies, browser storage and embedded media

No Google Analytics initialization, advertising pixel or similar marketing tracker was found in the inspected application. A Firebase measurement ID in configuration does not by itself mean Analytics is running. This finding does not establish what a live hosting proxy or third-party service may add.

Firebase sign-in can keep authentication state in browser storage so you remain signed in. The service worker caches public site resources for performance and offline use; private account and admin responses are excluded by the application’s cache policy. The podcast feed uses a public-content cache with a 30-minute freshness window. Spark booking, when enabled, uses session storage for an account identifier, request reference and payload digest to help avoid duplicate requests; it clears the entry after a successful booking or an explicit reset.

Embedded Spotify and YouTube players connect to their providers and may use cookies or similar technologies. The podcast’s featured Spotify player and a review’s YouTube player can connect when their content is displayed; lazy loading is not a consent control. Podcast detail players load when expanded. YouTube uses its privacy-enhanced embed domain, which does not mean that no personal information is processed. External artwork and feed requests can also disclose your IP address.

You can manage cookies and site data in your browser; clearing sign-in data can sign you out and clearing caches removes local copies. Blocking services may affect login or playback. External platform links are an alternative way to access media under that platform’s terms.

Processing outside South Africa

The website uses international service providers. Information may be processed outside South Africa, including by their hosting infrastructure and subprocessors. Some configured backend functions target the us-central1 region; the repository does not establish the location of all database, email, media or backup processing.

POPIA section 72 restricts transfers to foreign recipients. The appropriate basis must be established, such as adequate protection under law or a binding agreement, qualifying contractual necessity, or valid consent where applicable. Naming a provider is not proof that a transfer satisfies these requirements.

How information is protected

The code includes Firebase sign-in, owner-scoped database access rules, restrictions on customers changing privileged profile fields, and administrator checks. Optional private photograph operations have additional authorization; production callable endpoints are configured to require App Check. The browser application uses Firestore’s in-memory data cache rather than a persistent Firestore disk cache.

These are application controls, not a guarantee of security or proof of production configuration. Access management, deployed rules, provider settings, backups and incident procedures require ongoing operational review. Please keep your credentials private, sign out on shared devices and avoid sending passwords in enquiries.

Your rights and how to make a request

Subject to POPIA and applicable access procedures, you may ask whether we hold personal information about you; request access, correction or deletion of information that is inaccurate, irrelevant, excessive, out of date, incomplete, misleading or unlawfully obtained; request destruction of records we are no longer authorised to retain; and object to qualifying processing. Where processing relies on consent, you may withdraw it for future processing without invalidating earlier lawful processing. You may object to direct marketing and ask that it stop.

Email revivaldetailing@gmail.com with the subject “Privacy request”, describe your request and give a safe way to reply. Please send only the information needed to locate the relevant account or enquiry. We may need proportionate proof of identity before releasing or changing records; do not send identity documents until a suitable verification method is agreed. Some records may need to be retained where law permits or requires it, and the reason should be explained.

You may complain to South Africa’s Information Regulator. Its published enquiries contact is enquiries@inforegulator.org.za and 010 023 5200; consult its website for current complaint procedures and forms.

Back to top ↑