Your data stays yours.
Period.
Qwikerr was built with a Zero Data Knowledge architecture. We facilitate the sync between your platforms and your CRM — but we never see, store, or touch your data.
How we protect your data
Every design decision in Qwikerr was made with privacy and security as the primary constraint — not an afterthought.
Zero Data Retention
We do not have a database that stores your CRM records, leads, contacts, or any chat message content. Data flows directly from your browser to your CRM endpoint via their API. If Qwikerr disappeared tomorrow, your CRM would be untouched.
Official OAuth 2.0
We use each CRM's official API and OAuth 2.0 authorization flow. You grant permission directly to the CRM — not to us. Qwikerr receives a short-lived, scoped access token. We never see or store your CRM password or master API key.
TLS 1.3 Encryption
Every API call made by the extension is encrypted using TLS 1.3 — the current industry standard. Data in transit between your browser and your CRM is protected from interception.
GDPR & CCPA by Design
Because Qwikerr retains no personal data, there is no data subject access request or erasure request to fulfill on our side. Uninstalling the extension stops all access and severs any association — no off-boarding process needed.
Minimal Extension Permissions
Qwikerr requests only the Chrome permissions it needs: sidePanel, storage (for OAuth token), and activeTab. It does not request browsing history, screen capture, or all-site read access.
No Message Content Access
Qwikerr reads only structured contact metadata visible on the page — name, phone number, email — to identify a CRM match. The content of your chats, emails, and messages is never accessed, read, or processed.
Security FAQ
Does Qwikerr read my WhatsApp messages?
No. Qwikerr reads only the contact's name and phone number from the chat header so it can look up the matching CRM record. The content of your conversations is never read, stored, or transmitted.
Where is my CRM data stored?
In your CRM — not on Qwikerr's servers. We have no back-end database that stores your CRM records, leads, or contacts. Data flows directly from your browser to your CRM's API.
How does Qwikerr connect to my CRM?
Via OAuth 2.0 — the same authorization protocol used by Google, Salesforce, and all major platforms. You grant permission directly to your CRM. Qwikerr receives only a short-lived, limited-scope access token. We never see your CRM password.
What Chrome permissions does the extension request?
Qwikerr requests sidePanel (to show the sidebar), storage (to save your OAuth token locally), and activeTab (to read the current page's contact info). It does not request browsing history, screenshot access, or all-sites permissions.
Is Qwikerr GDPR compliant?
Yes. Because Qwikerr retains no personal data, there is no Qwikerr-side data subject or erasure request to fulfill under GDPR or CCPA. Uninstalling the extension revokes all access and severs any association.
Ready to sync securely?
Join teams worldwide who trust Qwikerr with their CRM workflows — with zero data on our side.
Add to Chrome — It's Free Talk to our team →