Legal
Privacy policy
Version 2026-09-12
Controller
The data controller is EPGWise (trading name — registration pending), Registered address pending publication. Contact: supportepgwise.com. You can also use the support form.
Information we use
We process account details, subscription records, and technical logs needed to authenticate you, deliver feeds, prevent abuse, and support the service.
Payments
Payments are handled by Stripe. EPGWise does not store full card numbers; Stripe processes card information under its own privacy policy. EPGWise stores only the provider customer and subscription references needed to collect the agreed recurring subscription charge and to manage your subscription.
Cookies and third-party services
The site uses essential cookies and browser storage to maintain your session and language preference. A functional cookie remembers your selected checkout plan for up to 24 hours. Browser storage also remembers that you dismissed the email-verification reminder for your account on this browser. When you use the language selector, content is translated via Google Translate, which loads scripts from translate.google.com and may set a googtrans cookie and a googtrans entry in localStorage to remember your choice. If you opt in on a support ticket, we send only that ticket message's text (not its email address, account ID, or feed link) to Google Cloud Translation to detect the language. A super-admin may separately choose to send an English reply draft's text to the same service for a requested translation; no translated reply is emailed until a super-admin reviews and sends it. Do not put sensitive information in support messages. We ask before loading advertising measurement tags. If you choose “Allow measurement”, Google, Meta (when configured), OpenAI Ads (when configured), and X (when configured) receive pseudonymous advertising and conversion signals so we can measure which adverts lead to account registrations, trials, or subscriptions. The OpenAI pixel may use its opaqueoppref click reference and browser reference; the server-side conversion feed sends only a SHA-256 hash of the account email. The X tag may use its opaque twclid click identifier; its server-side conversion feed likewise sends only a SHA-256 hash of the account email and, where recorded, the opaque click identifier. These tags remain disabled until that choice is made. If you choose “Essential only”, no advertising measurement scripts are loaded. First-party server logs record coarse purchase funnel events (for example checkout started or a subscription becoming active) without advertising identifiers, feed tokens, or card details. With your measurement consent, we also record one anonymous landing visit per browser session, containing only the landing path, source, medium, campaign, and referring hostname; it contains no IP address, full URL, query string, account identity, or advertising click identifier. When you arrive with campaign tags such as utm_source and allow measurement, we may store a first-touch source, medium, campaign and referring hostname in browser storage and a first-party cookie (up to 90 days), on a newly created account, and on the checkout session so we can tell which channels lead to paid subscriptions. Opaque ad-click references, where supplied, are kept in browser storage, that cookie and checkout/conversion records; they are not stored on the account profile. Advertising tags stay off account and authentication pages. After a consented signup or checkout, a brief confirmation page sends the conversion using opaque references. A secure HttpOnly cookie holds its account-bound context for up to three minutes; a separate cookie keeps up to eight hashed attempt references for 30 days to prevent repeated redirects. Neither cookie grants account or guide access. We also mirror your measurement choice in a first-party cookie for up to a year. We do not store full page URLs or query strings that may contain personal data in our traffic reports. Stripe webhooks remain the authoritative record of conversion. You can change your choice by clearing theepgwise.measurement-consent entry in browser storage and revisiting the site.
Retention and sharing
We retain information only while needed for the service, security, accounting, or legal obligations. Support tickets and translation drafts are retained with the support record for that purpose; you can ask us to review or delete eligible support content. We do not sell personal information.
Your rights and account closure
You may access, correct, export, or delete eligible account information. Closing your account from the dashboard cancels active subscriptions at the payment provider, revokes feed credentials, and removes or anonymises non-essential profile data. A minimal closed account identity is retained so the account cannot be silently re-created and for fraud-prevention purposes; it cannot be used to sign in. Some payment and accounting records must be retained for legal or fraud-prevention reasons; payment data held by Stripe is deleted in line with Stripe’s own retention and regulatory obligations.
Contact
Privacy requests can be sent to supportepgwise.com or through the support form.