GoGreen EVs — Mainnet Privacy Policy

Applies to the GoGreen EVs Mainnet application at mainnet.gogreenevs.com · Last updated: 20 September 2026

This Policy covers the Mainnet application. A separate Testnet may process separate test activity. This Policy describes GoGreen EVs data practices; third-party services have their own policies.

GoGreen EVs verifies EV mobility activity and maintains related reward and utility records. This Policy explains the information used to operate, secure and improve that service.

1. Who is responsible

The GoGreen EVs project operates the application and is responsible for the processing described here to the extent required by applicable law. For privacy, account or data requests, use Profile → Contact & report → Privacy / data request while signed in.

GoGreen EVs is independent from Pi Network and third-party taxi providers. Those services process information under their own terms and privacy policies.

2. Information we process

3. Information we do not ask for

GoGreen EVs does not ask for your Pi wallet seed phrase, private key or passphrase. Never provide those through a support message, receipt or any GoGreen EVs field.

We do not require your phone contacts or microphone for the core service. If a browser/device permission is requested, the permission prompt controls whether that device capability is available to the app.

4. Why information is used

5. Location and active rides

Precise location is required for GPS ride verification. GoGreen EVs attempts to collect location while an eligible ride is actively being recorded, including when browser/device capabilities permit the ride session to continue while the app is not in the foreground. Mobile operating systems and browsers may suspend or limit background location, so continuous collection is not guaranteed.

GoGreen EVs does not intentionally track your location when no ride is active. You can revoke location permission through your browser or device settings. Doing so can prevent or interrupt ride verification and may leave part of a route unverifiable.

6. Receipts and evidence

Ride evidence can contain personal information, including information printed on a receipt or visible in an uploaded image. Submit only evidence you are entitled to provide and avoid including information that is unnecessary for verification. Evidence may be analyzed for ride/provider consistency, duplication, fraud and eligibility.

When Receipt Intelligence V2 is enabled, the retained receipt image may be sent server-side to OpenAI for automated visual extraction. GoGreen EVs sends the receipt image and extraction instructions; it does not intentionally send the rider's Pi username, raw GoGreen account identifier, GPS route, GGT balance or selected provider as model-side truth. The OpenAI request is configured with response storage disabled. Extracted image facts are then compared by GoGreen EVs against server-held ride and provider records. If image analysis is unavailable, unclear or conflicts with those records, the ride remains eligible for the ordinary review path rather than being automatically rejected.

7. Analytics, cookies and local device storage

GoGreen EVs uses essential session technology to keep accounts signed in and may use local browser/device storage for ride continuity, queued data, preferences and reliability. These mechanisms are part of operating the service and are not intended for third-party advertising.

GoGreen EVs currently uses Amplitude for limited product analytics. The analytics user profile may include the verified Pi username and a coarse ISO country code so authorized operators can locate account-specific support or operational cases. Analytics events use a pseudonymous internal analytics identifier and are designed not to send precise GPS coordinates, city/locality, receipt contents, GGT balances, wallet secrets, raw GoGreen account IDs or raw Pi credentials. GoGreen EVs does not sell personal information or use behavioral advertising trackers.

8. When information is shared

Information is disclosed only as reasonably necessary to operate or protect the service, including to infrastructure, hosting, database, security, analytics and receipt-analysis providers acting for GoGreen EVs (including OpenAI when Receipt Intelligence V2 is enabled); to Pi Network when interacting with Pi authentication/payment services; when you direct or authorize a feature that requires sharing; or when disclosure is required by applicable law or necessary to protect legal rights, users or service security.

GoGreen EVs does not sell your personal information to advertisers. Taxi providers are not automatically given your GoGreen EVs ride history merely because you select their provider name in the app.

9. International processing

GoGreen EVs is available across countries and uses online infrastructure providers. Information may therefore be processed or stored in countries other than the country where you use the service. Where applicable law requires safeguards for international transfers, GoGreen EVs will use legally recognized mechanisms appropriate to the service and provider.

10. Retention

Retention depends on the purpose of the record. Account, ride-verification, reward, ledger, transaction, fraud-prevention and dispute records may need to be retained to preserve programme integrity, financial/transaction history, security and legal obligations. Session, diagnostic and routine technical data should be retained only as long as reasonably necessary for their operational or security purpose.

A deletion request does not require deletion of information that must lawfully be retained, is necessary to prevent fraud or resolve disputes, or forms part of an integrity/transaction record that applicable law permits or requires us to keep. Where appropriate, data may instead be restricted, de-identified or disconnected from ordinary account use.

11. Your privacy choices and rights

Depending on where you live, applicable law may give you rights to request access, correction, deletion, restriction, objection, portability or information about processing. These rights can have legal exceptions and may require identity verification.

Submit a request through Profile → Contact & report → Privacy / data request. Provide enough detail to identify the request, but never include a wallet passphrase or private key. You may also control location and notification permissions through your device/browser and may stop using the service at any time.

12. Security

GoGreen EVs uses technical and organizational safeguards such as server-side authorization, restricted data access, session controls, rate limiting, origin controls, anti-abuse checks and sanitized error handling. No internet service can guarantee absolute security. If you believe your account or data is at risk, report it through the in-app Contact & report feature.

13. Children

GoGreen EVs is not directed to children who are not legally permitted to use the connected Pi account/services or consent to the relevant data processing. If you believe a child has provided personal information contrary to applicable requirements, submit a privacy request so it can be reviewed.

14. Automated verification

GoGreen EVs uses automated rules and signals to assess ride and reward eligibility and to detect abuse. Receipt Intelligence V2 may use an AI model to extract visible facts from a receipt image, but the model itself does not approve, reject or credit a ride. GoGreen EVs applies separate deterministic checks against the provider selected at ride start, server-recorded GPS facts, duplicate-evidence controls and EV-specific evidence requirements. Only a narrow set of high-consistency cases may be automatically verified; ambiguous, conflicting or unsupported cases are routed to review, and the AI extraction layer has no automatic-rejection outcome. Where the app offers a review or support route, you may use it to provide additional information. Rights relating to automated decisions, where applicable in your jurisdiction, may also be raised through a privacy request.

15. Changes to this Policy

This Policy may be updated when features, providers, security practices or legal requirements change. The date above identifies the current version. Material notice will be provided where required by applicable law.