Privacy Policy
This policy explains how the G2V Email Verifier service processes account, API, verification, and payment-related data.
1. Who operates this service
G2V Email Verifier is operated by LoveMedia Foundation NPC, registration number 2024/122569/08, of 24–25 Marseilles CT, Briardene, Durban, South Africa, 4001. Enquiries and privacy requests may be sent to support@g2v.org.
2. Information we collect
We collect account details such as your name, company, email address, password hash, email-confirmation state, API-key metadata, login and security-event metadata, free and purchased-credit usage, uploaded filenames, submitted email addresses, and verification results. For purchases we retain package, amount, currency, status, expiry, Stripe Customer, Checkout Session, and Payment Intent references needed for fulfilment, reconciliation, fraud prevention, and support. We do not store plaintext passwords, complete API keys, full payment-card numbers, or card security codes.
3. Why we process it
We process information to create and secure accounts, confirm mailbox ownership, provide single and bulk verification, manage free and purchased credit balances, process and reconcile payments, diagnose errors, prevent misuse, deliver service messages, meet legal obligations, and improve reliability. Our legal bases may include performance of a contract, legitimate interests in service security and operation, consent where required, and compliance with law.
4. In-house verification and processors
G2V performs email verification in house. The service checks syntax and mail-routing records, then connects directly to the receiving domain’s published mail server and performs a standard SMTP mailbox handshake without sending message content. Submitted addresses are not sent to an external email-verification service. The receiving mail operator necessarily sees the recipient address and connection metadata needed to answer the check. Stripe processes checkout and card information and stores reusable payment methods against a Stripe Customer when requested during purchase; Stripe provides G2V with references and limited payment metadata rather than full card details. Account mail is processed by our SMTP provider and the application is hosted on infrastructure used to deliver the service. Processors act under our instructions or their applicable service terms. Do not upload an address unless you have a lawful basis to process it.
5. Retention
We retain account, credit, security, and aggregate usage records while your account is active and for a reasonable period required for security, dispute, tax, or legal purposes. Raw addresses submitted through the API and API bulk filenames/results are retained only while processing and for 24 hours after verification or job completion, then redacted automatically. Request IDs, timestamps, aggregate counts, credit records, and non-identifying outcomes may remain as operational and audit logs. Expired unconfirmed registrations and rate-limit events are deleted on a rolling basis. Download results you need before the retrieval window closes.
6. Security
We use transport encryption, access controls, one-way password and API-key hashing, host-only secure sessions, request throttling, least-privilege services, and audit-oriented usage records. No online service can promise absolute security.
7. International processing
Service providers may process data outside your country. Where laws such as the GDPR or South Africa’s POPIA apply, we use appropriate contractual, organisational, and technical safeguards for cross-border processing.
8. Your rights
Depending on your location, you may request access, correction, deletion, restriction, objection, portability, or withdrawal of consent. You may also complain to the South African Information Regulator or your local supervisory authority. We may need to verify your identity before fulfilling a request.
9. Cookies
We use an essential, secure session cookie for authenticated access. We also load Google Tag Manager for site measurement. Browser controls may restrict non-essential storage. Blocking the essential session cookie prevents dashboard sign-in.
10. Changes
We may update this policy as the service evolves. Material changes will be published here with a revised effective date.