Privacy Policy

Draft — not yet reviewed by a lawyer

This document describes what TargetIQ actually does today, but it has not had legal review. Points still to be settled are marked below.

This policy describes what TargetIQ collects, where it is stored, who else sees it, and how to have it removed. It is written against the Saudi Personal Data Protection Law (PDPL) and, because the data is stored in the European Union, covers the parts of the GDPR that follow from that. Last updated 2026-09-27.

Who is responsible

TargetIQ is currently operated by Zeineb Khlissa, sole trader, Tunis, Tunisia, acting as the interim data controller. A Saudi company is in the process of registration and will replace this entity as controller; this page will be updated when it does.

For privacy questions or requests, write to targetiqsm@gmail.com.

Two different groups of people

This policy covers two groups, and their situations are not the same. The first is our users: people who create a TargetIQ account. The second is the people whose contact details our users capture — professionals whose LinkedIn profiles or WhatsApp group entries a user saved while viewing them.

Pending legal reviewFor captured contact data, the user who captured it decides why it was collected and what it is used for, and TargetIQ stores and processes it on their behalf. The allocation of controller and processor roles between TargetIQ and its users needs legal confirmation, as does whether a data processing agreement must be offered to users.

What we collect

From our users: full name, email address, a hashed password (never the password itself), preferred language, country, the business they belong to, their plan, and their credit balance and usage history.

Captured lead data, saved by a user through our Chrome extension while they view a LinkedIn profile or a WhatsApp group: name, profile link, job title, company, location, and where the page showed them — email address, phone number, website, address, birthday and the date the connection was made. On WhatsApp Web, also: the member's WhatsApp username when the number is hidden, a link to their profile picture, and the group's name as shown in the chat header. Capture happens only when the user acts; the extension does not collect in the background.

Enrichment results: when a user asks us to find an email address or phone number for a lead, we send that lead’s name, company and LinkedIn URL to our enrichment provider and store what comes back.

Usage records: how many leads were captured and when, credit transactions, daily activity counters, and an audit log of administrative actions. Payment records only if billing is enabled — it is currently switched off, and no card details ever reach our systems.

Where it is stored, and who else sees it

All data is stored in a PostgreSQL database hosted by Neon in eu-central-1 (Frankfurt, Germany). The application itself runs on Vercel, also in Frankfurt.

Third parties that receive data, and why: Neon (database hosting), Vercel (application hosting), FullEnrich in France (only the lead details needed to look up an email address or phone number, and only when a user asks for enrichment), and Stripe (payment processing — only once billing is enabled, which it is not today). We do not sell data and we do not share it for advertising.

Enrichment results are kept per business

Enrichment results are kept per business. A contact one business has unlocked is never served to another; each business pays for its own lookups.

Transfers outside Saudi Arabia

If you are in Saudi Arabia, your data and the data you capture are stored in Germany and, when you request enrichment, processed in France. They do not stay inside the Kingdom.

Pending legal reviewThe PDPL restricts transfers of personal data outside the Kingdom. SDAIA has not published a list of countries deemed to provide an adequate level of protection, so this transfer cannot rely on an adequacy decision. It therefore needs another lawful basis — most plausibly approved standard contractual clauses with Neon, Vercel and FullEnrich, and a transfer impact assessment. This is unresolved and is the single item most in need of legal attention.

Why we are allowed to hold it

For our users’ own account data: to provide the service they signed up for.

Pending legal reviewFor captured lead data, the lawful basis rests with the user who captured it. Our terms require users to have a lawful basis for collecting and contacting the people they capture, but which bases are available under the PDPL for business-to-business outreach — and whether notice must be given to the captured person, by whom, and when — needs legal confirmation.

How long we keep it

Captured leads and account data are kept until the user deletes them or until a deletion request is completed. We do not currently run an automatic retention limit, and we would rather say so than imply one exists. Database backups are kept for a limited period and are deleted on a schedule; a deletion request is applied to live data immediately and to backups as they expire.

Pending legal reviewWhether a defined retention period is required, and what it should be.

Your rights

You may ask what we hold about you, ask us to correct it, ask us to delete it, object to how it is used, or ask for a copy. This applies whether you are one of our users or someone whose details a user captured. Write to targetiqsm@gmail.com, or use our data deletion page. You do not need an account to make a request.

We answer requests within 30 days.

How we protect it

Data is encrypted in transit and at rest. Each business sees only its own data, enforced in the database rather than in the interface. Contact details a user did not collect themselves are hidden until that business unlocks them. The application connects to the database with an account limited to reading and writing data, not to changing the schema.

We do not hold a SOC 2 report or an ISO 27001 certificate, and we do not describe ourselves as certified.

Children

TargetIQ is a business tool and is not intended for anyone under 18. [REVIEW] The correct age threshold and wording under the PDPL.

Questions about this page: targetiqsm@gmail.com

Last updated: 2026-09-27