Privacy Policy – Phone-verif.com

1. Data We Collect

We collect and process the following categories of data:

2. How We Use Your Data

We use your data to:

• Provide and operate our Services.
• Generate verification links and QR codes.
• Improve and secure our platform.
• Detect and prevent fraudulent or unauthorized use.
• Process payments and manage subscriptions.
• Comply with legal obligations.

3. Legal Basis for Processing

We process your data under the following GDPR legal bases:

4. Data Retention

5. Data Sharing

We do not sell your data. We may share data with:

• Service providers, including Lovable for website hosting, Supabase for our application infrastructure, and our payment provider. Country detection also sends the visitor’s IP address to ip-api.com, as described in section 9. The public documentation reviewed does not establish a project-specific data processing agreement or international transfer safeguards for that lookup.
• Legal authorities if required by law.

6. International Data Transfers

International transfers require applicable safeguards, such as an adequacy decision or Standard Contractual Clauses where required. The public provider documentation reviewed does not confirm every processing location or the safeguards configured for this project’s country lookup and hosting logs. Country detection is not a guarantee that data stays in that country or in the EEA. Contact us for information about applicable provider arrangements.

7. Your GDPR Rights

You have the right to:

• Access your personal data.
• Correct inaccurate data.
• Request deletion of your data.
• Restrict or object to processing.
• Request data portability.
• Lodge a complaint with your local Data Protection Authority.

Requests can be made to dpo@phone-verif.com.

8. Security Measures

We implement appropriate technical and organizational measures to protect your data, including encryption, secure storage, and access controls.

9. Cookies & Tracking

We use cookies and similar technologies to operate and improve our Services. You can manage or disable cookies via your browser settings.

Country detection before measurement

On eligible production websites, when no explicit analytics choice is stored, your browser requests a measurement mode from our Supabase function. This request happens before optional journey events are collected. The function takes the first IP address in the network’s forwarded request header and sends it to ip-api.com to estimate your country. This is an approximate IP-based lookup, not GPS location, and it can be inaccurate, for example when using a VPN or proxy. We do not use your browser language or account sign-in location for this decision.

The lookup requests only a country code. Our function uses that code to return “automatic” or “ask for consent”; neither the IP address nor the country code is written to our journey-event tables or explicitly logged by this function. This does not mean the IP is never processed or recorded elsewhere: the browser request passes through network infrastructure, and the lookup transmits your IP to an external provider.

Geolocation provider and transport

The current server-to-server lookup uses ip-api.com’s free HTTP endpoint, so this part of the transmission is not encrypted with HTTPS. According to ip-api.com’s privacy policy and terms, for anonymous API use it keeps the calling client’s network IP in memory for up to one minute for rate limiting, discards other supplied information after responding, and does not log requests. In our setup the calling client is our server, while your IP is supplied as the lookup target. These are the provider’s statements, not independently audited guarantees about every infrastructure log. The free endpoint’s terms restrict it to non-commercial use; its suitability and contractual safeguards for this service require review.

Conditional automatic measurement

The current country rule asks for consent in the European Economic Area (EU countries, Iceland, Liechtenstein and Norway), the United Kingdom, Switzerland and Brazil. For other returned country codes, measurement can start automatically without a banner if you have not already refused it. An unknown country, failed lookup or failed mode request keeps optional measurement inactive until you accept. This configuration describes the current implementation; it is not a determination that every other jurisdiction exempts this particular visitor-to-signup tracking from consent. The legal basis and country rules require jurisdiction-specific review.

Journey events and browser storage

When enabled, measurement records public-site visits, documentation and pricing views, demo clicks, demo starts, interactions and final results, authentication-page views and signup starts. Events contain random event, tab/origin-specific session and browser identifiers, the browser identifier’s expiry, event type and order, page category, page language, demo type, result category and button location; the database adds receipt and update timestamps. These are pseudonymous measurements, not a count of uniquely identified people. A browser counts once within the selected reporting period while its identifier remains retained and unexpired; a returning browser has another recorded visit before or during that period. The browser totals are separate from visit-based conversion rates. We do not send phone numbers, emails, WhatsApp message content, verification tokens, full URLs, IP addresses, user agents or account identifiers in journey-event payloads. Account creation totals are reported separately and are not linked to these sessions.

We use sessionStorage for the random session identifier, last activity time, event sequence and duplicate-prevention markers. A new session starts after 30 minutes of inactivity; the existing entry may remain in browser storage until replaced or the tab is closed. When measurement is enabled, localStorage also holds a random browser identifier with a fixed expiry 30 days after creation, not renewed on return visits. It is shared only across tabs on this website origin, never across domains or devices, and is replaced at the next enabled measurement after expiry. Clearing storage, using another browser or withdrawing consent prevents recognition. Historical identifier-free daily totals cannot reconstruct unique or returning browsers. An explicit acceptance or refusal is stored in localStorage for this website origin, with no application-set expiry, until changed or cleared. The automatic mode is kept in memory rather than saved as explicit consent. Measurement is disabled in development, previews, preproduction and embedded product views.

Retention and refusal or withdrawal

Our Supabase database is configured with a daily cleanup at 00:05 UTC that deletes journey events older than 30 days and daily aggregates older than 12 months. These thresholds take effect on the next successful cleanup, rather than at the exact expiry instant, and do not describe provider logs or backups. Expired browser identifiers are excluded from reporting immediately and cleared from retained events by a separate daily cleanup at 00:10 UTC; identifiers are not retained in the 12-month aggregates. Raw events are restricted to service-side access; aggregate reporting is administrator-only.

Use “Analytics preferences” in the footer and choose “Refuse / withdraw” at any time, including where measurement started automatically. An explicit refusal overrides the automatic mode, stops future journey-event sends, discards queued work and attempts to abort in-flight event requests; it also removes the stored journey session and browser identifier. Your explicit choice itself is counted only as an anonymous daily total, with no session identifier, page category, IP address or other personal data attached, so that aggregate acceptance and refusal rates can be reported; these counters follow the 12-month aggregate retention above. A request already received by the server may still have been recorded. Withdrawal does not automatically erase previously stored events or aggregates; they remain subject to the retention above. Your choice does not affect verification or account services. Clearing localStorage removes the saved refusal, so a later visit may trigger country detection and automatic measurement again.

Separate hosting analytics and operational logs

Lovable’s website traffic analytics and provider-injected scripts are separate from our journey recorder. Lovable and the network delivering the site may process request metadata for delivery, security and traffic reporting; the published site is served through Cloudflare. Supabase documents gateway request logs, Edge Function request/response metadata and function console logs; these can include IP-related headers, request paths, referrers, status codes and timestamps. Avoiding IP addresses in journey-event payloads does not prevent infrastructure logging. Operational account sign-in metadata is also a separate treatment, not reused for this marketing journey measurement.

The journey preference controls our recorder, not provider traffic analytics, injected scripts, geolocation-provider records or infrastructure logs. Supabase log retention depends on the project’s plan and settings; the actual retention, exports and backups for this external project have not been confirmed. We have not confirmed a published-site access-log deletion period or the consent behavior of hosting-injected analytics. A log viewer’s selectable time range is not a deletion guarantee. For provider information, see Lovable hosting documentation, Supabase log fields and Supabase logging and retention documentation. You can contact us using the details below about these outstanding provider-specific checks.

10. Changes to This Policy

We may update this Privacy Policy from time to time. Any changes will be posted on this page with a revised "Last Updated" date.

11. Contact