Privacy
Your data, plainly.
Last updated 12 November 2026.
Double Dating (doubledating.com) lets you check how many other browsers have searched the same name and phone number. This page explains what we keep and why. It is written to be read, not to hide behind.
What we collect
- What you search for: the first name, optional second name, and phone number you enter. Names are stored so we can count repeat searches for the same pairing. Phone numbers are stored as a keyed cryptographic hash (HMAC-SHA256) plus the last three digits, never as plain text.
- A session identifier: a random token stored in an HttpOnly cookie on your browser. We store only a SHA-256 hash of it on our servers. It is not linked to your name, email or account, because there are no accounts.
- Form drafts on your device: what you type into the search and payment forms is kept in your browser's session storage so a reload does not lose it. It stays in that tab, is not sent anywhere else, and clears when the tab closes.
- Payment details: a keyed hash of the M-Pesa number used to pay, its last three digits, the amount, the Safaricom checkout request ID, the payment result and, on success, the M-Pesa receipt number.
- Basic technical records: timestamps and server logs needed to run and protect the service.
We do not ask for your email, your contacts, your location or your ID. We do not use advertising trackers.
Why we hold it
- To produce the search result you paid for.
- To process and evidence your M-Pesa payment.
- To prevent abuse, fraud and repeated payment attempts.
- To meet accounting and legal obligations.
Who sees it
Access is limited to the service operators and the processors that make the service work: Supabase (database hosting), our web host, and Safaricom through its Daraja/M-Pesa API for payments. We do not sell personal data and we do not publish the names or numbers that have been searched.
One thing is shared: each search contributes to an aggregate count that any user can see. In that limited sense the search is public: it changes a number, not a profile. The underlying name and phone number are never shown to other users.
How long we keep it
Search records are kept while the service operates so that counts stay meaningful. Payment records are kept for as long as tax and accounting law requires. Session identifiers are kept for the life of the cookie and a reasonable period afterwards. You can ask us to delete data linked to your session.
Security
The site uses a single essential HttpOnly cookie, an unguessable session token, hashed session storage, server-only database access and row-level security. Form drafts stay in the browser tab and are not sent anywhere. Phone numbers are hashed with a server-held secret so a copy of the database alone cannot be used to test phone numbers; the M-Pesa callback payload is stripped of the payer phone before it is stored. Payment callbacks are authenticated with a private token. No system is perfect; if you believe something is wrong, tell us.
Your rights
Under the Kenya Data Protection Act 2019 you can ask for access to, correction of, or deletion of personal data we hold about you, and you can object to processing. Email support@doubledating.com and we will respond. If you are the person who was searched and want a record corrected or removed, contact us with enough detail to identify it.
Children
The service is for adults. It is not intended for anyone under 18, and we do not knowingly collect their data.
Cookies
We set one essential cookie, dd_sid, so your browser can see the search it started. It holds a random identifier only: no name, phone number or payment status, and it is HttpOnly, Secure in production, and SameSite=Lax.
Changes
If this policy changes materially, we will update this page and the date above.