Privacy Policy

Revised: 23 October 2026 · This revision applies from publication

1. Who We Are

FuelWatch.ie ("FuelWatch", "we", "us") is operated by Alex Santos, trading as FuelWatch.ie, with service address Lodge Road, Westport, Co. Mayo, Ireland. We are the data controller for the personal data processed through the Service.

Contact: hello@fuelwatch.ie

2. What We Collect

Data	Purpose	Legal Basis
Email address (via Google OAuth, business sign-in or an email link)	Account creation and authentication	Contract performance
Display name	Account display and community identity	Contract performance
Price submissions and their account link	Community reporting, submission history and accuracy checks	Contract performance
Selected price facts and source records for business reports and the Developer API, when enabled	Prepare price statistics and business reports, and supply reported fuel prices for licensed public-app display, without contributor account details	Where personal data is involved, legitimate interests in fuel-price analysis, subject to necessity, balancing and minimisation checks and your right to object
Business contact, organization, order, invoice and payment-status information	Optional business reports and Developer API accounts, purchases, subscriptions, support and tax records	Contract performance; legal obligations for required tax records
Approximate location (if permitted)	Showing nearby stations	Consent
Photos of price boards (if submitted)	Extracting fuel prices via AI	Consent

Photos submitted for price scanning are sent to a third-party AI service (Google) for text extraction. FuelWatch does not store the uploaded image itself. We retain extracted prices, account-linked scan counts and diagnostic logs, including the AI response, to operate and check the scanner. These diagnostics are not included in commercial reports. Avoid photographing faces, number plates or other personal information.

Stripe processes payments for optional Fuel Data & Analytics Reports and Developer API services. FuelWatch stores the limited billing contact, order, invoice and payment-status information needed to provide that service, but not your full card number or CVV. The consumer app is free.

3. What We Do Not Do

FuelWatch does not display advertisements of any kind.

FuelWatch does not sell or rent contributor account details or personal profiles. We share the information needed to operate the service with the providers listed below. Paid reports and the Developer API contain price observations and permitted business details, subject to the safeguards in section 4.

FuelWatch does not use tracking pixels, behavioural analytics, fingerprinting, or any form of cross-site tracking.

4. Data Sources

Station records combine community information, OpenStreetMap, public Revenue registers, supplier and brand websites, and directory sources. Community users submit pump prices. We also periodically collect home-oil and green-diesel prices from suppliers' public websites and online quotation forms. Public access does not mean every source is open-licensed. The Terms of Service explain these source categories.

Price observations may support free comparisons, historical statistics and paid Fuel Data & Analytics Reports products. Business reports can include station or supplier business names, fuel types, prices, observation times and relevant station or quotation-area details. They exclude contributor names, emails, account identifiers, photographs, device-location records, IP addresses and usage histories.

A source price report can still be linked to its contributor account internally for submission history and quality checks. We treat linked records as personal data. Removing direct identifiers from a report does not by itself make every observation anonymous: station, price and time can sometimes be matched with other information. Before enabling this use, we assess whether processing is necessary and proportionate, give notice of a new purpose where required, and consider contributors’ reasonable expectations and rights. We review the selected fields and linkage risk before a paid release, and withhold or reduce detail where necessary. You may object to processing based on legitimate interests by contacting us; we assess the objection under data-protection law.

We do not license contributor profiles or histories of an individual's activity to report customers. Your account profile and submission history are separate from the business report files. Contact us about a price report or business listing that identifies you, or to exercise the rights below.

Developer API: public fuel-price integrations

Licensed developers may display eligible Republic of Ireland petrol and diesel observations in their own websites and apps. The API supplies the latest eligible price per station and fuel within a maximum 30-day window, a Dublin calendar report date, permitted station name/county and qualified station coordinates where available. It does not supply contributor names, emails, account IDs, photographs, device positions, activity histories or exact submission times. A station coordinate identifies a selling premises, not a contributor’s device.

Where these records remain personal data, the purpose is fuel-price comparison and transparency through licensed integrations that support the service, relying on the assessed legitimate interests described above. Public display widens the audience, so the API uses day precision, a latest-price view, no contributor-search facility, restricted source linkage and short-lived snapshots. Customers must not attempt to identify contributors or reconstruct their activity. We assess objections and revealing business listings individually; we do not assume all earlier contributors accepted a later notice or that identifiers alone make a record anonymous.

We keep business account details, key names/prefixes and one-way key hashes, request counters, accepted terms versions and payment references to authenticate access, meter the plan, prevent abuse and provide billing/support. The full API key is shown once and is not stored in our key table. API snapshots expire after two hours; routine refresh removes snapshots that have been expired for more than a day. Source records and necessary payment/security evidence have their separate retention purposes. A copied result can remain in a customer’s short-lived cache until refreshed or removed; downloaded data cannot be recalled remotely.

Contact hello@fuelwatch.ie to object, request correction or report an identifying observation. We can restrict affected source/snapshot access while reviewing a credible rights concern and instruct customers to remove affected data. Your GDPR rights and the response periods below apply. The API licence explains permitted display, caching, corrections and business records.

5. Third-Party Services

FuelWatch uses the following third-party services to operate:

Service	Purpose	Data shared
Supabase	Database and authentication	Email, display name, submissions, scan diagnostics, business account, order and access records
Google OAuth	Sign-in	Email, name (from Google account)
Clerk (FuelWatch Data)	Business account sign-up, sign-in and email verification	Email, account identifier, profile information you provide, and authentication/session information
Stripe	Web payment processing	Business billing contact, order and payment information; card details are collected by Stripe
Resend (Fuel Data & Analytics Reports)	Account, purchase and report-notification emails when the business service is enabled	Recipient email, message content and delivery status
Vercel	Website hosting	Standard server logs (IP, user agent)
Google (AI services)	Photo price scanning	Photo content for extraction; FuelWatch retains extracted results and diagnostic responses, not the uploaded image

Each third-party service processes data in accordance with their own privacy policy. FuelWatch does not control how these services handle data beyond what is necessary for the Service to function.

6. Data Retention

Account information is retained while needed to provide your account. Price observations may be kept as a historical dataset. Linked source records remain subject to data-protection requirements; they are not treated as anonymous simply because names are omitted from exported files.

On account deletion, we remove the account, profile and original account-linked price submissions and scan history. Previously compiled price observations, statistics and released reports are separate records and may remain; deleting the account does not automatically erase those copies. If retained information can still identify you, it remains subject to your data-protection rights and we review any further removal or restriction needed. We respond to rights requests within the applicable legal time limit, normally one month.

Optional business report and Developer API accounts have separate order, access and tax-record retention needs, described in section 7 of the report terms and section 8 of the API terms. Keeping required transaction records does not justify keeping all contact details or delivery logs indefinitely.

7. Your Rights (GDPR)

Under the General Data Protection Regulation, you have the right to access the personal data we hold about you, to request rectification of inaccurate data, to request erasure of your data, to restrict or object to processing, to data portability, and to lodge a complaint with the Data Protection Commission (dataprotection.ie).

To exercise any of these rights, email hello@fuelwatch.ie. We normally respond within one month; if a lawful extension is needed, we will explain it within that first month.

8. Children

The Service is not directed at anyone under the age of 16. We do not knowingly collect personal data from children under 16. If we become aware that we have collected data from a child under 16, we will delete it promptly.

9. Data Security

We use industry-standard security measures to protect your data, including encrypted connections (TLS), secure authentication via OAuth, and row-level security policies on our database. However, no system is completely secure and we cannot guarantee absolute security.

10. International Transfers

Your data may be processed by third-party services (Supabase, Stripe, Vercel) whose infrastructure is located outside the European Economic Area. These services maintain appropriate safeguards including Standard Contractual Clauses or equivalent mechanisms as required by GDPR.

11. Changes to This Policy

We may update this Privacy Policy from time to time. The effective date at the top of this page indicates when it was last revised. We will bring material changes in personal-data use to your attention before they take effect and seek consent where required. This notice is not a waiver of your rights. Read the 7 October 2026 edition or Read the previous policy, last updated 8 April 2026.