This page explains how users may request deletion of data associated with Snapkey CRM, including data connected through supported social media integrations such as Facebook, Instagram, LinkedIn, Twitter/X, and other third-party services used within the platform.
These Data Deletion Instructions are provided to explain how users can:
- revoke access granted to Snapkey CRM through connected social platforms;
- request deletion of personal data or connected account data stored by Snapkey CRM;
- request deletion of content, media, and related publishing records; and
- understand what information may be deleted and what may be retained for legal or operational reasons.
This page is intended to support transparency, platform compliance, and user privacy rights.
You may revoke Snapkey CRM's access to your connected third-party accounts directly from the settings of the relevant provider.
Revoking access through the third-party platform will prevent Snapkey CRM from taking future actions on your behalf through that integration. However, data previously stored in Snapkey CRM may still remain in our systems until separately deleted — see Section 3 below.
If you want Snapkey CRM to delete your data from our systems, you may submit a data deletion request by contacting ABM Technomatrics Pvt Ltd through our official privacy, support, or deletion request channel.
Your request should include sufficient information to help us identify the relevant records, such as:
- your full name
- your registered email address
- your company or organization name, if applicable
- your Snapkey CRM workspace or tenant name, if known
- the connected platform involved, if any
- the type of deletion requested
Examples of deletion requests include:
- deletion of your user account
- deletion of connected Facebook or Instagram data
- deletion of scheduled or published post records
- deletion of uploaded media
- deletion of a workspace or organization-level data set
- deletion of specific connected account data
Subject to verification, technical feasibility, and applicable law, we may delete or de-identify data associated with your request, including:
- account profile information
- connected social media account records
- stored access token records and integration metadata
- scheduled posts, drafts, and publishing records
- uploaded media and media references
- account connection status records
- analytics records associated with identifiable user or workspace data
- session and workspace-related records where appropriate
Where deletion is completed, the deleted data may no longer be available for access, restoration, analytics, reporting, or platform use.
In certain circumstances, we may retain limited information where necessary for:
- compliance with legal obligations
- tax or financial recordkeeping
- fraud prevention or security monitoring
- enforcing our legal rights
- dispute resolution
- internal audit requirements
- backup integrity and controlled recovery processes
Where data is retained for such reasons, we will limit retention to what is reasonably necessary and permitted by law.
To protect account security and prevent unauthorized deletion, we may require verification before completing a deletion request. Verification may include confirming:
- the email address associated with the account;
- ownership or control of the relevant workspace;
- authority to act on behalf of an organization; or
- control of the connected platform account involved.
If we cannot reasonably verify your identity or authority, we may decline or limit the request for security reasons.
We aim to review and respond to deletion requests within a reasonable period after receipt and verification. The time required to complete deletion may depend on:
- the scope and complexity of the request;
- whether the request involves an individual account or an organization-wide workspace;
- the need for identity or authority verification;
- technical dependencies and backup cycles; and
- legal obligations requiring limited retention.
Once deletion is completed:
- connected account data may be removed from Snapkey CRM;
- stored content, posts, or media may no longer be recoverable;
- analytics related to deleted data may no longer be available;
- workspace access tied to deleted user records may be affected; and
- future publishing or synchronization for removed integrations will no longer function unless reconnected.
Users should ensure that any information they wish to retain has been exported, saved, or otherwise preserved before requesting deletion, where such export is available.
Removing Snapkey CRM from Facebook, Instagram, LinkedIn, Twitter/X, or another connected service revokes future access, but it may not automatically delete data already stored in Snapkey CRM.
If you want previously stored data removed from our systems, you should also submit a direct deletion request to us at
snapkey43@gmail.com.
If you are using Snapkey CRM through a company, agency, or multi-user CRM workspace:
- organization administrators may request deletion of certain workspace-level data;
- individual users may need to contact their administrator for certain deletion actions; and
- we may require proof that the requester has authority to request deletion on behalf of the workspace or organization.
Snapkey CRM may process data obtained from third-party platforms only to provide authorized service functionality such as account connection, scheduling, publishing, analytics, and reporting.
If you want data deletion relating to your third-party social account, we recommend that you:
- revoke Snapkey CRM's access from the relevant platform settings; and
- submit a direct deletion request to Snapkey CRM for stored data within our systems.
Third-party platforms may retain data under their own policies, and you may need to contact them separately to address data held directly by them.
If you would like to request deletion of your data, please contact:
When contacting us, please include enough information to help us identify your records and process your request efficiently.
We may update these Data Deletion Instructions from time to time to reflect changes in our services, platform integrations, legal obligations, or privacy practices. Updated versions will be posted on the relevant public page with a revised effective date.