GrowthMateBack to home

Legal

Data Deletion Policy and Instructions

GrowthMate Data Deletion Policy and Instructions

Effective date: 24 July 2026 Last updated: 24 July 2026

This Data Deletion Policy and Instructions document explains how users may disconnect integrations, delete imported data, close an individual GrowthMate account or delete an entire GrowthMate Workspace.

GrowthMate is operated by:

QOPTERVZN INFOCOM PRIVATE LIMITED

Plot No. 19, At – Khokarla Balaji Nagar, Behind Bhaiyaji Nagar Bhupali Duplex Bhandara, Maharashtra India – 441904

In this document:

  • “GrowthMate,” “we,” “us” or “our” means QOPTERVZN INFOCOM PRIVATE LIMITED.
  • “Services” means the GrowthMate Website, Application, integrations, reports, recommendations, action-management tools and related services.
  • “Website” means growthmate.net.
  • “Application” means app.growthmate.net.
  • “User,” “you” or “your” means an individual or organization using GrowthMate.
  • “Workspace” means the GrowthMate environment through which users, integrations, data, reports and actions are managed.
  • “Connected Service” means a third-party service connected to GrowthMate, including Google Analytics, Google Search Console, Google Ads or Umami.
  • “Connected Data” means data imported or synchronized from a Connected Service.
  • “Derived Data” means reports, metrics, recommendations, summaries, implementation briefs or other information generated from Connected Data.
  • “OAuth Credentials” means access tokens, refresh tokens, authorization codes and related authorization information used to connect a third-party service.
  • “Active Systems” means GrowthMate’s live databases, application storage, caches, queues and systems used during normal operations.
  • “Backup Systems” means restricted backup copies maintained for security, disaster recovery and business continuity.

This document should be read together with the GrowthMate Privacy Policy, Terms of Service, Google API Data-Use Disclosure, Cookie Policy and Subprocessor List.

1. Available deletion and disconnection choices

GrowthMate provides different controls depending on what the user wants to remove.

Users may request one or more of the following:

1. Disconnect a Connected Service while retaining historical data. 2. Disconnect a Connected Service and delete the data imported from that service. 3. Delete imported data from a previously disconnected service. 4. Delete an individual GrowthMate account. 5. Delete an entire GrowthMate Workspace. 6. Revoke Google or another provider’s authorization. 7. Request deletion by email when an in-application control is unavailable.

These operations have different effects.

Disconnecting a service is not the same as deleting previously imported data.

Deleting an individual user account is not necessarily the same as deleting an organization’s Workspace.

2. Disconnecting an integration without deleting historical data

A Workspace owner or other authorized administrator may disconnect a Connected Service while retaining historical information already imported into GrowthMate.

When a Connected Service is disconnected:

  • GrowthMate stops requesting new data from that service;
  • future scheduled synchronization is stopped;
  • pending synchronization jobs are cancelled or invalidated where possible;
  • new synchronization jobs are prevented from being created;
  • OAuth access is revoked where supported;
  • locally stored access and refresh tokens are deleted;
  • temporary authorization codes and OAuth state values are deleted;
  • the integration is marked as disconnected;
  • the Connected Service can no longer be used for new GrowthMate reports;
  • previously imported data may remain available;
  • existing historical reports and recommendations may remain available; and
  • the user can separately request deletion of retained historical information.

The Application should clearly explain:

> Disconnecting stops GrowthMate from retrieving new information and removes the stored authorization credentials. Historical data already imported into GrowthMate will remain until you separately delete it or delete the Workspace.

Disconnecting an integration does not automatically delete data that GrowthMate previously imported.

3. Disconnecting and deleting imported data

An authorized Workspace owner or administrator may choose to disconnect a Connected Service and delete its imported data.

This operation may delete:

  • stored OAuth Credentials;
  • connected account identifiers;
  • analytics property mappings;
  • Search Console property mappings;
  • Google Ads customer and manager-account mappings;
  • Umami website mappings;
  • imported website analytics;
  • imported search-performance data;
  • imported advertising data;
  • campaign and conversion records;
  • synchronization checkpoints;
  • source-specific synchronization history;
  • raw import or staging records;
  • cached API responses;
  • temporary processing files;
  • source-specific error payloads;
  • source-specific files;
  • reports based exclusively on the deleted source;
  • recommendations based exclusively on the deleted source;
  • implementation briefs based exclusively on the deleted source; and
  • source-specific evidence attached to cross-source findings.

The operation does not automatically delete unrelated Workspace data.

For example, deleting a Google Ads integration should not delete independent Search Console or Umami information.

4. Data derived from more than one source

Some GrowthMate reports and recommendations may combine information from several Connected Services.

When one source is deleted:

4.1 Exclusively source-derived information

A report, recommendation or brief that depends exclusively on the deleted source may be permanently deleted.

Examples include:

  • a Google Ads-only recommendation;
  • a Search Console-only opportunity;
  • a GA4-only performance report;
  • a source-specific synchronization report; or
  • a brief created entirely from one deleted source.

4.2 Partially source-derived information

A report or recommendation that also uses information from another retained source may be:

  • recalculated;
  • regenerated;
  • invalidated;
  • marked as incomplete;
  • assigned a lower confidence level;
  • stripped of deleted-source evidence; or
  • deleted where it can no longer be supported reliably.

GrowthMate will not intentionally continue displaying deleted-source information as active evidence.

4.3 Independent information

Information unrelated to the deleted integration may remain, including:

  • Workspace settings;
  • team memberships;
  • billing records;
  • independent user notes;
  • consent records;
  • security logs;
  • Terms acceptance records; and
  • legally required records.

5. Google integration disconnection and revocation

GrowthMate may connect to Google Analytics, Google Search Console and Google Ads through Google OAuth.

When an authorized user disconnects or deletes a Google integration, GrowthMate will take reasonable steps to:

1. stop future Google API requests; 2. prevent new synchronization jobs; 3. cancel or invalidate queued synchronization jobs; 4. attempt to revoke Google OAuth authorization; 5. treat already invalid or revoked credentials as no longer usable; 6. delete locally stored access tokens; 7. delete locally stored refresh tokens; 8. delete temporary authorization codes and OAuth state; 9. mark the integration as disconnected; 10. stop repeated retries using invalid credentials; and 11. record only a non-sensitive revocation result.

Possible revocation records may indicate:

  • authorization revoked;
  • authorization already revoked;
  • token invalid;
  • Google temporarily unavailable;
  • network failure; or
  • manual review required.

GrowthMate does not retain raw OAuth tokens in deletion logs.

A temporary failure to contact Google does not prevent GrowthMate from deleting locally stored credentials.

Where a credential must temporarily be retained for a secure revocation retry, it will remain encrypted, access restricted and subject to a short retry period.

6. Revocation through the user’s Google Account

A user may revoke GrowthMate’s authorization directly through their Google Account.

When GrowthMate detects that authorization has been revoked or is no longer valid, GrowthMate may:

  • stop the affected synchronization;
  • mark the integration as disconnected or requiring reconnection;
  • prevent repeated failed API calls;
  • delete unusable local OAuth Credentials;
  • cancel future synchronization;
  • notify the Workspace owner;
  • provide a reconnection option; and
  • provide an option to delete historical imported data.

Revoking authorization through Google stops GrowthMate from obtaining new data.

It does not automatically delete information already imported into GrowthMate.

Users who also want stored information deleted must use GrowthMate’s data-deletion controls or contact GrowthMate.

7. Umami and other integration disconnection

Where a Connected Service does not use Google OAuth, GrowthMate will use the provider’s available disconnection or credential-revocation process.

Depending on the integration, GrowthMate may:

  • delete API keys;
  • delete access tokens;
  • delete connection credentials;
  • remove account mappings;
  • disable scheduled synchronization;
  • invalidate queued jobs; and
  • delete imported data when requested.

A third-party provider may retain information independently under its own terms and privacy policy.

GrowthMate cannot delete information that remains under the independent control of another provider unless GrowthMate has the technical and legal ability to request that deletion.

8. Deleting an individual user account

A user may request deletion of their personal GrowthMate account.

Personal account deletion may include:

  • personal profile information;
  • personal authentication credentials;
  • active login sessions;
  • personal API tokens;
  • personal notification settings;
  • personal communication preferences;
  • personal account metadata;
  • individual product-analytics identity where supported;
  • personal Workspace memberships; and
  • information that GrowthMate is not required to retain.

Individual account deletion does not automatically delete an organization-controlled Workspace where other authorized users remain.

Information created within an organization’s Workspace may remain under the control of that organization, including:

  • reports;
  • recommendations;
  • action records;
  • implementation briefs;
  • business data;
  • shared notes;
  • integration data; and
  • billing information.

Where appropriate, historical references to a deleted user may be anonymized rather than removed if deletion would damage:

  • security records;
  • financial records;
  • action-history integrity;
  • fraud-prevention records; or
  • organization-controlled audit history.

9. Sole Workspace owners

A user who is the sole owner of a Workspace cannot delete their personal account without first resolving ownership of that Workspace.

The user must choose one of the following:

1. Transfer Workspace ownership to another eligible user. 2. Delete the entire Workspace. 3. Cancel the personal account-deletion request.

GrowthMate will not intentionally leave a Workspace without an authorized owner.

If ownership transfer is selected, the receiving user may be required to accept ownership before the original owner’s account deletion is completed.

10. Deleting an entire Workspace

Only an authorized Workspace owner may request deletion of an entire Workspace.

Workspace deletion may include:

  • the Workspace profile;
  • Workspace settings;
  • Workspace memberships;
  • invitations;
  • share links;
  • Workspace API keys;
  • Connected Services;
  • OAuth Credentials;
  • integration mappings;
  • imported analytics information;
  • Search Console information;
  • Google Ads information;
  • Umami information;
  • synchronization history;
  • reports;
  • recommendations;
  • implementation briefs;
  • action records;
  • comments and notes;
  • uploaded files;
  • report-delivery settings;
  • notification history where appropriate;
  • customer-generated content;
  • internal configuration; and
  • other active Customer Data associated with that Workspace.

Before Workspace deletion, GrowthMate may require:

  • recent authentication;
  • confirmation of Workspace ownership;
  • a typed confirmation phrase;
  • review of affected users;
  • review of connected integrations;
  • confirmation of subscription consequences; and
  • confirmation that deletion cannot be reversed after completion.

Deleting a Workspace does not necessarily delete restricted billing, tax, legal, fraud-prevention or security records that GrowthMate is required to retain.

11. Subscription consequences

Deleting a personal account does not automatically cancel an organization’s subscription where other Workspace users remain.

Deleting an entire paid Workspace may result in:

  • cancellation of future subscription renewal;
  • loss of paid features;
  • termination of connected integrations;
  • deletion of active Workspace data; and
  • retention of required invoices and transaction records.

Subscription cancellation and refunds remain subject to the GrowthMate Refund and Cancellation Policy.

Deleting the Application, closing a browser or disconnecting one integration does not by itself cancel an active subscription.

12. Authorization requirements

GrowthMate applies different permissions to different deletion operations.

12.1 Disconnecting an integration

Normally available to:

  • Workspace owners; and
  • administrators with integration-management permission.

12.2 Deleting integration data

Normally available to:

  • Workspace owners; and
  • administrators with explicit data-management permission.

12.3 Deleting an individual account

Available to the authenticated user for their own account, subject to sole-owner restrictions.

12.4 Deleting a Workspace

Available only to an authorized Workspace owner.

GrowthMate verifies authorization on the server.

The presence of a button or access to a URL does not establish permission to perform a deletion.

GrowthMate may require recent authentication or additional identity verification before performing a high-impact deletion.

13. Confirmation and protection against accidental deletion

GrowthMate may require one or more of the following before destructive deletion:

  • password re-entry;
  • authentication-provider confirmation;
  • multi-factor authentication;
  • email confirmation;
  • a time-limited confirmation link;
  • a typed confirmation phrase;
  • the exact Workspace name;
  • acknowledgement of affected data categories; and
  • confirmation of subscription consequences.

GrowthMate does not intentionally preselect destructive deletion options.

The Application should distinguish clearly between:

  • Disconnect only;
  • Disconnect and delete imported data;
  • Delete my personal account; and
  • Delete the entire Workspace.

14. Background jobs and synchronization

Deletion is not complete if background systems can recreate the deleted information.

When a deletion request is confirmed, GrowthMate takes reasonable steps to:

  • disable the relevant integration or Workspace;
  • stop new jobs from being scheduled;
  • cancel pending jobs;
  • invalidate stale jobs;
  • prevent running jobs from writing new data;
  • stop scheduled synchronization;
  • stop API retries;
  • remove synchronization checkpoints; and
  • verify that no active job recreated deleted information.

A job started before deletion may be rejected if the integration or Workspace is no longer active.

GrowthMate may use deletion locks, status checks, generation identifiers or similar technical controls to prevent stale processing.

15. Deletion processing stages

A deletion request may pass through stages such as:

  • request received;
  • awaiting confirmation;
  • confirmed;
  • queued;
  • revoking external authorization;
  • cancelling jobs;
  • deleting active data;
  • cleaning external services;
  • verifying deletion;
  • completed;
  • partially completed;
  • failed; or
  • manual review required.

GrowthMate may display deletion status in the Application or communicate it by email.

A deletion request will not be represented as complete while GrowthMate knows that material active Customer Data remains available, except where the information must legally be retained.

16. Deletion periods

GrowthMate applies the following deletion targets.

| Action or data category | Target period | | ---------------------------------------------------- | --------------------------------------------------------- | | Stop new API access | Immediately after confirmed disconnection | | Stop scheduled synchronization | Immediately | | Prevent new jobs | Immediately | | Cancel or invalidate queued jobs | As soon as processing begins | | Revoke OAuth authorization | Immediately where technically available | | Delete access and refresh tokens | Immediately and ordinarily no later than 24 hours | | Delete temporary OAuth state and authorization codes | Immediately | | Delete active imported integration data | Ordinarily within 30 days after a verified request | | Delete active personal-account data | Ordinarily within 30 days after a verified request | | Delete active Workspace data | Ordinarily within 30 days after a verified request | | Send completion confirmation | After active-system deletion is verified | | Expire deleted information from backups | Through normal backup rotation, ordinarily within 90 days |

GrowthMate aims to complete most active-system deletion requests much sooner than the maximum period.

A longer period may apply where necessary because of:

  • identity or authority verification;
  • a legal hold;
  • an active dispute;
  • fraud investigation;
  • security incident;
  • technical corruption;
  • third-party service failure;
  • a complex Workspace relationship; or
  • a legal obligation.

Where appropriate, GrowthMate will explain the delay.

17. Backup copies

GrowthMate maintains restricted backups for disaster recovery, security and business continuity.

When information is deleted from Active Systems:

  • the deleted information may temporarily remain in encrypted backups;
  • backup copies are not used during ordinary product operations;
  • access to backups is restricted;
  • backup copies expire through the applicable rotation schedule;
  • deleted information will not intentionally be restored to active use;
  • deleted information is ordinarily removed through backup rotation within 90 days; and
  • GrowthMate may retain a deletion ledger so that deletions can be reapplied after a disaster recovery event.

GrowthMate does not normally alter each historical backup to remove individual records because doing so may damage backup integrity or make recovery unreliable.

18. Restoration and deletion reconciliation

If GrowthMate restores a database from a backup, GrowthMate will take reasonable steps to prevent previously deleted information from returning to normal use.

The recovery process may include:

1. restoring the database; 2. restoring or obtaining the latest deletion ledger; 3. identifying deletion requests completed after the backup date; 4. reapplying those deletions; 5. deleting restored OAuth Credentials associated with deleted records; 6. ensuring deleted integrations remain disabled; 7. ensuring deleted Workspaces remain unavailable; 8. preventing synchronization until reconciliation is complete; and 9. verifying that removed information has not returned to active use.

A deletion ledger is intended to contain only the minimum information needed to reapply a deletion and will not contain copies of the deleted Customer Data.

19. Legal and compliance retention

GrowthMate may retain limited information where required for:

  • tax compliance;
  • accounting;
  • invoicing;
  • payment disputes;
  • fraud prevention;
  • security investigations;
  • consent evidence;
  • Terms acceptance;
  • legal claims;
  • court or governmental orders;
  • regulatory compliance;
  • grievance handling; or
  • deletion audit evidence.

Retained information will be:

  • limited to what is reasonably necessary;
  • separated or logically restricted where appropriate;
  • unavailable in ordinary product interfaces;
  • accessible only to authorized personnel;
  • not used for advertising;
  • not used to recreate deleted Customer Data;
  • not used for unrelated product analytics; and
  • deleted when the applicable retention requirement ends.

Possible retained categories include:

  • invoices;
  • transaction identifiers;
  • subscription cancellation records;
  • tax records;
  • consent history;
  • Terms acceptance history;
  • security logs;
  • fraud records;
  • legal correspondence;
  • deletion request status; and
  • non-sensitive deletion audit records.

20. Deletion audit records

GrowthMate may retain a minimal audit record to demonstrate that a deletion request was received and completed.

A deletion audit record may contain:

  • deletion request identifier;
  • request type;
  • irreversible or opaque target reference;
  • requester reference where legally permitted;
  • request date;
  • confirmation date;
  • completion date;
  • categories deleted;
  • OAuth revocation result;
  • completion status;
  • policy version;
  • legal-retention categories;
  • backup-expiry date; and
  • controlled failure category.

A deletion audit record will not intentionally contain:

  • OAuth tokens;
  • passwords;
  • payment-card information;
  • raw Google data;
  • raw Umami data;
  • deleted reports;
  • recommendation contents;
  • implementation-brief contents;
  • advertising search terms;
  • private user notes; or
  • copies of deleted database records.

21. Product analytics and identity deletion

GrowthMate uses product-analytics systems such as PostHog and Google Analytics.

Following account deletion, GrowthMate may:

  • stop identifying the user in future product events;
  • reset the local analytics identity;
  • remove or anonymize user properties;
  • request deletion of identifiable analytics profiles where supported and appropriate;
  • retain aggregated or de-identified statistics;
  • retain minimal consent or suppression records; and
  • retain non-identifying business analytics where permitted.

GrowthMate does not intentionally include complete connected Customer Data in product-analytics events.

Deleting a GrowthMate account may not delete aggregated statistics that no longer reasonably identify a person or Customer.

22. Marketing and advertising records

Following withdrawal of marketing consent or account deletion, GrowthMate may:

  • stop sending promotional messages;
  • remove the user from active GrowthMate remarketing audiences where applicable;
  • remove the user from future Customer Match or custom-audience uploads where applicable;
  • update email and WhatsApp marketing preferences;
  • retain a minimal suppression record; and
  • retain consent-withdrawal evidence where required.

GrowthMate’s advertising audiences are separate from Customer-connected Google Analytics, Search Console, Google Ads and Umami data.

Deleting Connected Data does not require GrowthMate to delete independent first-party billing or marketing information where GrowthMate has a lawful reason to retain it, although applicable opt-out choices will be respected.

23. Razorpay and payment records

GrowthMate uses Razorpay for payment processing.

GrowthMate can delete or restrict its own billing records subject to applicable law, but it cannot necessarily delete information independently retained by Razorpay for:

  • payment processing;
  • fraud prevention;
  • financial regulation;
  • payment disputes;
  • taxes; or
  • other legal obligations.

Users may need to contact Razorpay directly concerning information controlled independently by Razorpay.

Deleting a GrowthMate account does not erase legally required invoice and transaction records.

24. OpenRouter and AI processing

GrowthMate may use OpenRouter to route limited information to artificial-intelligence model providers.

When active GrowthMate data is deleted:

  • GrowthMate will stop submitting that data in future AI requests;
  • generated reports or briefs stored by GrowthMate will be deleted where covered by the request;
  • GrowthMate will apply its configured OpenRouter and model-provider data controls;
  • GrowthMate will not intentionally use deleted Customer Data for future AI processing;
  • GrowthMate will not retain deleted AI prompts or outputs in Active Systems except where subject to a lawful retention exception; and
  • downstream provider retention, where any exists, remains subject to the applicable provider configuration and terms.

GrowthMate aims to use data-minimized requests and provider settings that restrict logging or model training where available.

25. Shared reports and links

Deleting a Workspace or relevant report may invalidate:

  • report share links;
  • implementation-brief links;
  • invitation links;
  • action-assignment links;
  • public report tokens; and
  • other shared access credentials.

Recipients may have independently copied, downloaded, exported or stored information before deletion.

GrowthMate cannot delete copies independently retained by an authorized recipient outside GrowthMate.

Users should share reports only with appropriate recipients.

26. Customer-controlled data

Where GrowthMate processes data on behalf of an organization, the organization may control certain deletion decisions.

An individual Workspace member may not have authority to delete:

  • organization-owned reports;
  • organization-connected integrations;
  • billing records;
  • shared action history;
  • other members’ information; or
  • the entire Workspace.

An individual should contact the relevant Workspace owner concerning organization-controlled data.

GrowthMate may refer a deletion request to the responsible Customer where GrowthMate acts only as its Data Processor or service provider.

27. How to request deletion

Users may use the in-application controls available through:

text id="r8d0pi" app.growthmate.net → Settings → Data Sources

for integration disconnection and source-data deletion.

Personal account deletion may be available through:

text id="ln3guw" app.growthmate.net → Settings → Account → Delete my account

Workspace deletion may be available through:

text id="0bkcy4" app.growthmate.net → Settings → Workspace → Delete Workspace

Where an in-application option is unavailable, send a deletion request to:

[email protected]

A request should include:

  • the account email;
  • the Workspace name or identifier;
  • the relevant integration;
  • whether the request concerns disconnection or deletion;
  • the requested data categories; and
  • sufficient information to verify identity and authority.

Do not send:

  • passwords;
  • OAuth tokens;
  • API keys;
  • card numbers;
  • CVV codes; or
  • other sensitive credentials.

28. Identity and authority verification

GrowthMate may verify:

  • identity;
  • account access;
  • Workspace membership;
  • Workspace ownership;
  • administrative authority;
  • the affected integration; and
  • the scope of the deletion request.

Verification may involve:

  • logging in;
  • recent re-authentication;
  • email confirmation;
  • multi-factor authentication;
  • organization confirmation;
  • payment or billing verification; or
  • additional information reasonably necessary to prevent unauthorized deletion.

GrowthMate will not request excessive information solely to discourage a valid request.

29. Deletion confirmation

GrowthMate may send:

29.1 Request confirmation

A request confirmation may include:

  • request type;
  • request date;
  • affected Workspace or integration;
  • categories requested for deletion;
  • cancellation method where available;
  • security instructions; and
  • a non-sensitive request identifier.

29.2 Completion confirmation

A completion confirmation may include:

  • active-system completion date;
  • categories deleted;
  • OAuth revocation outcome;
  • categories retained for law or security;
  • backup-expiry explanation;
  • support contact; and
  • a non-sensitive request identifier.

The confirmation will not contain copies of deleted Customer Data.

30. Failed or partially completed requests

A deletion request may require manual review where:

  • Workspace ownership is unclear;
  • an active legal hold exists;
  • a payment dispute exists;
  • a security investigation is active;
  • a cross-tenant relationship appears inconsistent;
  • a third-party provider is temporarily unavailable;
  • a storage or database operation fails;
  • an encryption credential is unavailable; or
  • deletion could affect another Customer.

GrowthMate distinguishes between:

  • completed;
  • partially completed;
  • retryable failure;
  • permanent failure; and
  • manual review required.

GrowthMate will not intentionally mark a request completed while material active Customer Data remains, except where retention is legally required.

31. Cancellation of a deletion request

Where GrowthMate offers a short cancellation period for personal-account or Workspace deletion, the deadline will be shown to the user.

During a cancellation period:

  • normal access may be suspended;
  • integrations may already be disconnected;
  • new data collection may be stopped;
  • OAuth Credentials may already be deleted; and
  • cancellation may not restore third-party authorization.

Immediate integration-data deletion requests may not be reversible.

After permanent deletion begins, GrowthMate may not be able to cancel the request.

32. Data that may exist outside GrowthMate

Deleting data from GrowthMate does not necessarily delete data independently held by:

  • Google;
  • Meta;
  • WhatsApp;
  • Razorpay;
  • OpenRouter;
  • an AI Model Provider;
  • Brevo;
  • PostHog;
  • MilesWeb;
  • an organization using GrowthMate;
  • an authorized report recipient; or
  • another Connected Service.

These organizations may retain information under their own privacy policies, contracts and legal obligations.

Users may need to contact the relevant provider directly.

33. Security of deletion operations

GrowthMate applies reasonable safeguards to deletion operations, including:

  • server-side authorization;
  • recent re-authentication;
  • role verification;
  • Workspace ownership checks;
  • rate limiting;
  • confirmation tokens;
  • limited token validity;
  • audit logging;
  • tenant-boundary checks;
  • transaction controls;
  • background-job invalidation;
  • idempotent processing;
  • restricted staff access; and
  • sanitized error records.

GrowthMate will not process destructive deletion through an unauthenticated public request without appropriate verification.

34. No use of deleted Google data for advertising

Connected Google API data is not used to advertise GrowthMate.

After deletion, GrowthMate will not intentionally use deleted Google API data for:

  • Google Customer Match;
  • Google Ads remarketing;
  • Meta custom audiences;
  • personalized advertising;
  • unrelated user profiling;
  • data resale;
  • data-broker services; or
  • generalized AI model training.

GrowthMate’s own advertising audiences are based only on eligible first-party information collected directly by GrowthMate and processed according to the Privacy Policy and Cookie Policy.

35. Children’s information and sensitive data

GrowthMate is intended for business users aged 18 or older.

GrowthMate does not knowingly use children’s information for Customer Match, custom audiences or personalized advertising.

Where prohibited sensitive information is discovered during deletion processing, GrowthMate may prioritize removal and take additional security measures.

36. Changes to this policy

GrowthMate may update this Data Deletion Policy and Instructions to reflect:

  • product changes;
  • new integrations;
  • legal requirements;
  • Google or Meta policy changes;
  • new service providers;
  • backup architecture changes;
  • security improvements; or
  • changes to deletion workflows.

Material changes may be communicated through:

  • the Website;
  • the Application;
  • email; or
  • another appropriate method.

The current version will display its effective date and last-updated date.

37. Contact information

Questions or deletion requests may be sent to:

QOPTERVZN INFOCOM PRIVATE LIMITED

Plot No. 19, At – Khokarla Balaji Nagar, Behind Bhaiyaji Nagar Bhupali Duplex Bhandara, Maharashtra India – 441904

Privacy email: [email protected]

Grievance Officer: Alok Diwate Director [email protected]

Website: https://growthmate.net

Application: https://app.growthmate.net