This Privacy Policy explains what personal data Clikgen collects, why we collect it, how long we keep it and what rights you have. It covers both our website and the Clikgen platform. Where we process personal data on behalf of a customer, we do so as a processor and the customer's own privacy notice governs that data — see section 3.
1. Two different roles
Our obligations differ depending on whose data is involved, so it is worth being precise:
- Controller: when you visit this website, request a demo, email us or administer a workspace, we decide why and how your data is processed. This policy describes that processing.
- Processor: when our customers store their own leads, contacts, conversations and recordings inside the platform, they decide the purpose and we act on their instructions. If you are a contact of one of our customers and want your data removed, please contact that business — though you may also write to us and we will forward the request.
2. What we collect as controller
Information you give us
- Identity and contact data: name, business email, phone or WhatsApp number, company name, role.
- Enquiry content: the message you send through a form, by email or on a call, including what you tell us about your sales process.
- Account data: workspace name, configured region, billing contact where applicable.
- Support correspondence: tickets, screenshots and diagnostic information you share.
Information we collect automatically
- Usage data: pages viewed, features used, timestamps, referring URL and approximate location derived from IP address.
- Device data: browser type and version, operating system, screen size and language.
- Log data: IP address, request paths, error traces and security events.
- Cookies and similar technologies, as described in our Cookie Policy.
We do not knowingly collect special-category data (health, biometric, religious or political data) through our website, and we do not collect data from children under 18.
3. Customer data inside the platform
Customers upload and generate data about their own leads and customers — names, phone numbers, email addresses, conversation transcripts, call recordings, notes and commercial records. We process this strictly to operate the service.
- We do not sell it, rent it, or share it with advertisers.
- We do not use it to train general-purpose machine-learning models.
- We do not access individual records except where necessary to provide support you have requested, to investigate a security incident, or where compelled by law — and such access is logged.
- AI features send content to the model provider whose API key the customer configured; that provider's terms then apply to the request.
4. Google user data
Clikgen lets you connect your own Google accounts. When you do, Google shows you exactly what access Clikgen is asking for, and you can refuse. This section explains what Google user data we access, why, and what we never do with it. It applies to every Google API we use and takes priority over any other part of this policy.
What we access and why
| Google service you connect | Google user data accessed | Used only to |
|---|---|---|
| Google Calendar and Google Meet | Your calendars, events and free/busy times | Show your availability on booking pages, create, update or cancel the meetings you book in Clikgen, and add a Google Meet link to them. |
| YouTube | Your channel details and the videos and statistics of your channel | Upload the videos you schedule in Clikgen to your channel, and show you how those videos perform. |
| Google Business Profile | Your business locations, posts and their performance | Publish the posts you create in Clikgen to your Business Profile, and show you how they perform. |
| Google Ads | Your ad accounts, campaigns, campaign results and lead form submissions | Bring leads from your Google lead form ads into your CRM, show your campaign results next to your sales results, and send the conversions you choose back to your own Google Ads account. |
| Google sign-in details | The name and email address of the Google account you connect | Show which Google account is connected to your workspace. |
We only use Google user data to provide and improve these user-facing features inside your own workspace. We access a Google service only after you connect it yourself, and only the people you give access to in your workspace can see the data.
Limited Use
Clikgen's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.
AI and machine learning: the use of raw or derived user data received from Google Workspace APIs and all other Google APIs will adhere to the Google User Data Policy, including the Limited Use requirements. Clikgen does not use, transfer or sell Google user data — raw, aggregated or derived — to create, train or improve foundational or generalized AI or ML models, and Google user data is not sent to the AI features inside Clikgen.
What we never do with Google user data
- We never sell Google user data.
- We never use Google user data for advertising, retargeting, personalised ads or interest-based ads, and never use it to market our own products to you or anyone else.
- We never use Google user data for analytics, profiling or research that is not part of the feature you are using.
- Google user data, including data received from Google Workspace APIs, is not used to develop, improve or train generalized or non-personalized artificial-intelligence (AI) or machine-learning (ML) models, and we do not send it to AI providers.
- We never sell or transfer Google user data to data brokers, information resellers or any other third party, and never use it to build databases or lists for any purpose other than the feature you are using.
- We never use Google user data to judge creditworthiness or for lending.
- No person at Clikgen reads your Google user data, unless you ask us to in a support request, it is needed for security (for example investigating abuse), or the law requires it.
Who we share Google user data with
We do not share, transfer or disclose Google user data to third parties, except: (a) our cloud hosting provider, which stores it on our behalf under a written contract and cannot use it for anything else; (b) where the feature itself needs it and you asked for it, for example the attendees you invite receive the meeting details; (c) where the law requires it; or (d) as part of a merger or sale of our business, in which case you will be told first and this policy will continue to apply.
How we protect it
Google access tokens are encrypted at rest with AES-256-GCM, and all data is sent over encrypted TLS connections. Only the systems that run the features listed above can read the tokens, and access by our staff is restricted and logged.
How long we keep it, and how to delete it
- We keep Google access tokens only while the Google service is connected to your workspace.
- You can disconnect a Google service at any time from your workspace settings. This deletes the stored tokens at once and stops all access.
- Data we pulled from Google (for example synced calendar events or campaign results) is deleted when your workspace is deleted, or within 30 days of you asking us to delete it.
- You can also remove Clikgen's access from your Google account at https://myaccount.google.com/permissions.
- To ask us to delete all your Google user data, use our Data Deletion page or our contact form. We will confirm when it is done.
If this changes
If we ever change how we access, use, store or share Google user data, we will update this section first and tell you in the app and by email before the change takes effect. Where the change needs new permission, Google will ask you again and you can say no.
5. Why we process data, and our legal basis
| Purpose | Data used | Legal basis |
|---|---|---|
| Providing and operating the platform | Account, usage, customer data | Performance of a contract |
| Responding to enquiries and demos | Identity, contact, enquiry content | Legitimate interests / pre-contract steps |
| Support and troubleshooting | Account, log, correspondence | Performance of a contract |
| Security, fraud and abuse prevention | Log, device, usage | Legitimate interests / legal obligation |
| Product improvement and analytics | Aggregated usage data | Legitimate interests |
| Marketing communications | Identity and contact | Consent (withdrawable at any time) |
| Legal, tax and accounting records | Account and billing | Legal obligation |
Product improvement, analytics and marketing above use only data about how people use our own website and app, never Google user data. Google user data is used only as described in section 4.
7. International transfers
Data is stored in the region selected at workspace creation. Where personal data is transferred outside that region — for example to a support engineer or a sub-processor in another country — we rely on appropriate safeguards including Standard Contractual Clauses, adequacy decisions where they exist, and supplementary technical measures such as encryption in transit and at rest.
8. How long we keep data
- Website enquiries: 24 months from last contact, unless you become a customer.
- Account and workspace data: for the life of the workspace, then 30 days for export, then deletion within a further 30 days from live systems and 90 days from backups.
- Call recordings: for the retention period the customer configures, defaulting to 12 months.
- Security and audit logs: up to 24 months, or longer where required for legal defence.
- Financial records: as required by applicable tax law, typically 8 years in India.
9. Your rights
Depending on where you live, you may have the following rights. We will respond to any request within 30 days and will not charge a fee except where a request is manifestly unfounded or excessive.
- Access — obtain a copy of the personal data we hold about you.
- Rectification — correct data that is inaccurate or incomplete.
- Erasure — ask us to delete data where there is no overriding lawful reason to keep it.
- Restriction — ask us to pause processing while a dispute is resolved.
- Portability — receive your data in a structured, machine-readable format.
- Objection — object to processing based on legitimate interests, including profiling.
- Withdraw consent — at any time, without affecting prior lawful processing.
- Complain — to your supervisory authority, or in India to the Data Protection Board.
To exercise any right, message us on WhatsApp on +91 96304 70438 with enough detail for us to identify you.
10. Security
We apply technical and organisational measures proportionate to the risk, including TLS 1.3 in transit, AES-256 at rest, role-based access control, least-privilege internal access, audit logging, encrypted backups and periodic review. No system is perfectly secure, and we describe our practices honestly rather than absolutely — see the Security page for detail.
11. Changes and contact
We will post any change to this policy on this page with a revised date, and will notify customers by email where the change is material. Questions, requests and complaints should go to WhatsApp on +91 96304 70438, or by post to Clikgen, 82 JLPL, Mohali, Punjab, India.