Privacy Policy

1. Who we are

Claudphic Ads is lead management software with advertising attribution, sold as a monthly subscription to businesses. It captures sales leads together with the advertising click identifiers that produced them, tracks each lead to a real commercial outcome, and reports those outcomes back to Google Ads and Meta so that the platforms optimise toward customers who actually buy rather than people who merely fill in forms.

It is software you subscribe to, not an agency or a managed service. We do not run campaigns on your behalf and we do not take a share of your ad spend.

The service is operated by Claudphic Ads. Claudphic Ads is a product of Claudphic (claudphic.com). You can reach us at contact@claudphic.com or +91 92057 07743.

2. Controller and processor — who decides what

This distinction governs everything else in this policy, so it comes first.

For leads stored in Claudphic Ads, the customer is the Data Fiduciary and Claudphic Ads is the Data Processor, acting on their documented instructions. The business that collected a lead decided to collect it, decided what to ask for, and is responsible for having a lawful basis to do so. We hold and process that data on their behalf and for no purpose of our own. Under GDPR terminology, they are the controller and we are the processor.

For our own customers' account data — the business's name, their users' names and email addresses, their billing details, their usage of the product — we are the fiduciary, because those are our decisions.

The practical consequence is in section 9: if you are a member of the public asking us to delete your lead record, we action it on the customer's instruction and confirm back to you, rather than deleting another business's records unilaterally.

3. What we collect

3.1 Account and billing data (we are the fiduciary)

Your name, work email address, company name, company URL slug, password (stored only as a bcrypt hash, never in a readable form), and the role you have been assigned. Billing details are processed by Razorpay, our payment processor; we store the invoice record and the last four digits of the card, never the full card number.

3.2 Lead data uploaded or captured by customers (we are the processor)

Whatever the customer's own forms ask for. Typically a name, email address, phone number, WhatsApp number and company name, plus any custom fields they configure. This arrives through our landing-page capture script, our REST API, Facebook Instant Forms, Google Lead Forms, WhatsApp and Instagram messages, or CSV import.

3.3 Advertising click identifiers

This is what distinguishes the product, so it is worth naming precisely. When a visitor arrives from an ad and submits a form, we capture the identifiers present in the page URL and in first-party cookies set by the platforms:

• Google: gclid, gbraid, wbraid
• Meta: fbclid, and the _fbp and _fbc first-party cookies
• Others captured for future use: msclkid (Microsoft), ttclid (TikTok), li_fat_id (LinkedIn)
• Campaign context: UTM parameters, campaign, ad set and ad names, the landing page path, referrer, and a device/browser classification derived from the user agent

These identify an ad click, not a person by name. They are what allow a conversion to be matched back to the ad that caused it.

3.4 Visit context on a customer's landing page

Alongside the click identifiers above, a form submission carries a description of the visit itself, used by our customer to understand which kinds of enquiry turn into business. Specifically: the device type, make and model where the browser reports it, operating system and browser with version, screen and window size, language, timezone, connection type and speed class, and how the visit went — time on the page, how far it was scrolled, how long the form took to fill in, and how many times that visitor had been before.

Where the operator of this installation has enabled it, the visitor's IP address is also resolved to an approximate location — country, state, city and the coordinates of that city — and to the name of the network or internet provider it belongs to. The coordinates are the centre of a city, never a precise position: we do not use the browser's Geolocation API, request location permission, or collect GPS data. Where that lookup is switched off, location is inferred only from the timezone the browser reports, which identifies a country and nothing finer. The third parties who may perform that lookup are named on our sub-processors page, and a resolved address is stored against a one-way hash so the cache cannot be read back as a list of visitors.

We do not use canvas, audio or any other form of device fingerprinting, and none of the above is used to track a person across unrelated websites. It is recorded against a single enquiry, on behalf of the business that enquiry was sent to, and is deleted with it.

3.5 Usage logs and support correspondence

Login times, IP address, browser user agent, actions taken in the product, and API request logs — kept for security, abuse prevention and debugging. Emails and messages you send us, kept so we can answer them and refer back to them.

4. What we do not collect, and will not accept

Sensitive and special-category data is prohibited. Customers must not upload, and must not configure forms that collect, any of the following into Claudphic Ads:

• Health, medical or disability information
• Biometric or genetic data
• Financial account numbers, card numbers or credentials
• Government identifiers (Aadhaar, PAN, passport, and equivalents)
• Racial or ethnic origin, religious or political beliefs, trade union membership, sexual orientation or sexual life
• Data about children under 18

This is not only our rule. Both Meta and Google expressly forbid sending such categories through their conversion APIs, and doing so would put the customer's own ad accounts at risk as well as ours. This prohibition is repeated as a binding warranty in our Terms of Service.

We do not sell, rent, broker or enrich personal data. Not to advertisers, not to data brokers, not to anyone, in any form, at any price. We do not build cross-customer profiles and we do not use one customer's lead data to benefit another.

5. How we use data

Account and billing data: to provide the service, take payment, and contact you about your subscription and material changes to the product. Lead data: solely to deliver the features the customer has configured — pipeline management, reporting, notifications, and conversion reporting to the platforms they have connected. We do not use lead data to train machine-learning models.

6. Sending conversions to Meta

If a customer connects Meta, we use the Meta Conversions API to report that a lead reached a sales stage they have mapped to a conversion event.

What is transmitted:

• The event name and the time it occurred
• SHA-256 hashes of the email address and phone number, normalised to Meta's specification before hashing
• Meta's own click and browser identifiers (fbc, fbp), which are not personal details and are passed through as Meta issued them
• For a lead that came from a Facebook Instant Form, the lead_id Meta itself generated, which Meta requires unhashed in order to match it to its own record
• A conversion value and currency, where the customer records one

Raw email addresses and phone numbers are never transmitted to Meta. They are hashed with SHA-256 on our server before the request is made. A hash cannot be reversed to recover the original value; Meta compares it against hashes of its own users and learns nothing about anyone who does not already match.

Nothing is sent unless the customer has explicitly connected Meta and mapped a pipeline stage to an event. There is no default-on behaviour.

7. Sending conversions to Google Ads

The same arrangement through Google Ads offline conversion import. We send the conversion action name, the time, the value, and either the gclid Google itself issued or SHA-256 hashed email and phone for Enhanced Conversions for Leads. Raw contact details are never sent. As with Meta, this only happens for accounts the customer has connected and stages they have mapped.

8. Lawful basis and consent

Where we are the fiduciary (account and billing data), our basis is the performance of our contract with you, and our legitimate interest in securing and improving the service.

Where we are the processor (lead data), the customer is responsible for obtaining a lawful basis and any required consent from the individual before that data reaches us or the advertising platforms — including consent to onward transmission of hashed identifiers to Google and Meta. This is a warranty every customer gives in our Terms of Service. We provide the tooling; we cannot obtain consent on a customer's behalf, because we are not the party in the conversation with their prospect.

9. Deleting your data

Deletion is free, requires no reason, and is never made deliberately difficult. There are three routes, because there are three different kinds of request:

• Advertisers who connected Facebook or Google can disconnect inside the product, or remove the app from Facebook (Settings → Apps and Websites) or from their Google account. Removing the app from Facebook notifies us automatically and we delete the stored platform identity and all access tokens without you having to contact us. Your leads and your workspace are not affected.
• Members of the public whose details are in a business's CRM should contact that business, or email us at contact@claudphic.com. Because we are the processor and not the fiduciary, we action the deletion on the customer's instruction and then confirm back to you.
• Customers closing an account can request full workspace deletion, with a CSV export provided first.

Requests are acknowledged within 2 working days and completed within 30 days. Live deletion is immediate; encrypted backups expire on an approximately 90-day rotation and are never queried for individual records. Only invoices and tax records required by Indian law, and anything under an active legal hold, survive a deletion request.

Full detail, including how to check the status of a request: claudphicads.com/data-deletion.

10. How long we keep things

Data	Retention	Why
Lead records	While the workspace is active	The customer's business records; deleted on their instruction
Account data after cancellation	90 days	So a workspace can be reactivated without loss, then auto-deleted
Platform access tokens	Until disconnected	Deleted immediately on disconnect or app removal
Security and API logs	12 months	Abuse investigation and debugging
Encrypted backups	~90 days	Disaster recovery; expire on rotation
Invoices and tax records	As Indian tax law requires	Statutory; not discretionary and not linked to lead data
Support correspondence	24 months	Continuity of support

11. Sub-processors

We use a small number of third parties to run the service — hosting, email delivery, payments, and the two advertising platforms. Each is named, with what it does and where it processes data, at claudphicads.com/sub-processors. We give customers at least 30 days' notice before adding a new one.

12. International transfers

Our infrastructure is hosted in India. Two necessary exceptions: conversion data sent to Google LLC and Meta Platforms, Inc. is processed on their global infrastructure, including in the United States. That transfer is inherent to the feature — it is not possible to report a conversion to Google or Meta without sending it to Google or Meta — and only ever contains hashed identifiers and the platforms' own click ids, never raw contact details. Both operate under their own published terms and transfer mechanisms. A customer who does not want this can simply not connect those integrations; everything else in the product continues to work.

13. Security

Encryption in transit (TLS) and at rest, stored access tokens encrypted at the application layer, passwords hashed with bcrypt, role-based access control, and SHA-256 hashing of identifiers before any platform transmission. Each company's data is isolated and scoped on every read and write. We notify affected customers of a personal data breach within 72 hours of becoming aware of it. Full detail, including what we do not yet have, at claudphicads.com/security.

14. Cookies

This marketing website sets no tracking or advertising cookies. Signed in to the product, the application sets a session cookie to keep you logged in and a CSRF cookie to protect forms — both strictly necessary, neither used for tracking. The _fbp and _fbc values described in section 3.3 are first-party cookies set by the customer's own website, not by us; we read them at form submission if present.

15. Your rights

Under India's Digital Personal Data Protection Act, 2023 you have the right to access a summary of your personal data and how it is processed, to correction and completion, to erasure, to nominate someone to exercise your rights if you die or become incapacitated, and to grievance redressal.

If you are in the EEA or UK, GDPR / UK GDPR additionally give you rights of access, rectification, erasure, restriction, portability, objection, and the right not to be subject to solely automated decisions with legal effect. Claudphic Ads makes no such automated decisions about individuals.

To exercise any of these, email contact@claudphic.com. If your data sits in a customer's workspace, see section 2 for why the request is routed through them.

16. Children

Claudphic Ads is a business tool, sold to businesses, and is not directed at anyone under 18. We do not knowingly collect data about children, and customers are contractually prohibited from uploading it. If you believe a child's data has reached us, tell us and we will delete it.

17. Changes to this policy

Material changes are posted here with an updated date, and customers are emailed before changes that meaningfully affect how their data is handled.

18. Contact and grievance redressal

General privacy questions: contact@claudphic.com.

In accordance with the Digital Personal Data Protection Act, 2023 and the Information Technology Act, 2000, complaints about how your data has been handled can be escalated to our Grievance Officer:

Claudphic Ads
Email: contact@claudphic.com
Phone: +91 92057 07743

We acknowledge every grievance within 24 hours and resolve it within 15 days of receipt. If you remain dissatisfied, you may complain to the Data Protection Board of India.