Privacy Policy

Effective date: May 31, 2026 | Last updated: October 5, 2026

Zeerka Inc (“Zeerka”, “we”, “us”, or “our”) operates the web application at app.zeerka.com and the companion browser extension (“the Service”). This policy explains what personal data we collect, how we use it, and what your rights are.

Questions or requests: see the Contact section for details.

1. Who We Are

Zeerka Inc is the data controller for personal data processed through the Service.

2. What Data We Collect

2.1 Account Data

When you register with an email address, we store:

Your email address
A hashed password (we never store your password in plain text)
Your display name, if you choose to provide one (optional)
Your profile photo, if you upload one. If you signed up with Google, your Google profile photo is copied into your account once, at signup; we store our own copy and never load it from Google afterwards.

When you register or sign in via Google or Microsoft, we receive from those providers only the data needed to create and identify your account (typically: name, email address, and a provider-issued identifier). We do not receive passwords or payment information from these providers.

2.2 Bookmark Data

The content you create in Zeerka is stored in our Azure database:

Tabs, groups, and their names
Links: URL, title, personal notes
Browser sessions: the title, URL, and icon of each tab you save as a session
Notes widget content
Connected calendars: the name you give each calendar and its feed address

Connected calendars — we store the feed address so your calendar can be refreshed, and we keep it encrypted. We do not store your events. When a calendar is refreshed, the feed is requested from your calendar provider and passed straight to your browser, which reads the events and keeps them on your device. On end-to-end encrypted accounts the request is made by the Zeerka browser extension instead, so the feed never passes through our servers at all (see Section 4).

Usage statistics (Most Used Links, Recent Links) — click counts and recently opened links are tracked locally in your browser only. This data is never sent to our servers.

Link health (Premium, Family, and Business plans) — saved links go stale over time: pages get deleted, move to a new address, or end up behind a sign-in. Link health helps you find those links among everything you have saved and fix them. To do that, we keep a small record for each link:

The result of its last check (for example “not found” or “moved”), the HTTP status code, and when the check ran — so we can show you which links need attention and how recently that was confirmed, and so a link checked on one of your devices doesn’t need checking again on another
The new address, if the page has moved — so you can update the link in one step
Whether you excluded the link from the lists — so a link you have decided to keep as it is doesn’t keep being flagged
The date you last opened the link from Zeerka — a link you opened recently is one you have already seen, so it counts as seen for 90 days and link health can focus on the links you haven’t visited in a while. We keep only the most recent date, not a history of your visits. You can turn this off in Settings → Widgets (“Count opened links as seen”); turning it off also deletes the dates already stored.

We never store the content of the pages that are checked.

2.3 Link Icons, Preview Images, and Your Profile Photo

When you save a link, its icon URL is stored as part of the link record. Zeerka may also store a small copy of the icon image in its Azure Blob Storage, so the icon still displays if the site’s own icon later becomes unreachable.

If you choose a preview image for a link, that image is stored in Azure Blob Storage as well. Saving preview images depends on your plan. Your profile photo, if you set one, is stored there too; your browser resizes it before upload, which also removes any camera information the file carried, such as where the photo was taken. No other image data is collected.

2.4 Security Logs (IP Address)

We log your IP address alongside certain write operations (creating, updating, or deleting content; login events) for security auditing and account-integrity purposes. These logs are automatically deleted after 90 days. IP addresses are used solely for security purposes and are not shared with third parties for marketing or advertising.

2.5 Browser Extension

The Zeerka browser extension sends data to Zeerka only when you take an action. It does not track the pages you visit, and it sends nothing in the background on its own. Data goes only to your account at app.zeerka.com:

Saving a page: the page’s URL, title, and icon, plus the preview image you choose, if any
Saving a session: the title, URL, and icon of each tab you save
Importing bookmarks: your browser’s bookmark folders, names, and URLs
Repairing or protecting link icons: when you start this, the extension briefly opens each link’s site in a background tab, reads its icon, and sends the icon to Zeerka
Checking links: when you start a check, the extension loads each link’s page from your browser and, where that isn’t conclusive, briefly opens it in a background tab. It uses your browser’s existing sign-ins, so that a page you have to be signed in to is judged the way you would see it, rather than reported as broken. To tell whether the page still exists, it looks at the page’s status, title, and main heading in your browser. Those are used there and then discarded; they are never sent to our servers. Zeerka stores only the conclusion, such as “not found” or “moved”, and the new address if the page has moved (see Section 2.2)

Some extension features run in your browser without sending anything to Zeerka:

End-to-end encrypted accounts: the extension fetches a page’s details, such as its title, directly from the site, so the URL is never sent to Zeerka unencrypted
Connected calendars on end-to-end encrypted accounts: the extension fetches each calendar feed directly from your calendar provider, so neither the feed address nor your events reach Zeerka; it tells Zeerka only whether the fetch succeeded

The extension also stores the following in your browser only:

Your chosen destination group, until the browser is closed
UI preferences such as the last active pane, theme, and session options
A temporary copy of the tabs you last closed from the sessions panel, so you can reopen them; it is cleared when the browser is closed

2.6 Billing Data

Payments are processed by Paddle. We do not store your payment card details. Paddle’s privacy policy applies to any data you provide during checkout.

2.7 Feedback

When you send a bug report, feature request, or other message from the app (user menu → Send feedback), we store:

Your message and the type you chose
Whether you asked for a reply. We write to you about it only if you did, by email to the address shown in the form.
Your email address, plan, whether you hold that plan or are a member of a family or company plan, whether encryption is on, and your language, as they were when you sent it. We already hold these with your account; we keep them with the report so we can understand it later.
Only if you tick “Include technical details”: the app version, your browser and operating system, screen size and theme, whether Zeerka is installed as an app, and whether the Zeerka browser extension is installed, with its version. The form shows you these values before you send them.

Your bookmarks, notes, names, and other content are never included automatically. Feedback is not end-to-end encrypted, even on encrypted accounts: you are writing it to us, so we can read it. When a report arrives, we receive an internal notification that does not contain your message.

3. How We Use Your Data

Data	Purpose	Legal basis
Account data	Authenticate you and manage your account	Contract
Bookmark data	Provide the core Service	Contract
Link icons and preview images	Display link icons and previews to you	Contract
Profile photo	Show it to you in the app	Contract
Calendar feed addresses	Refresh your connected calendars	Contract
Link health records and last-opened dates	Help you find and fix links that no longer work	Contract
Feedback reports	Read and answer your feedback, fix problems, and improve the Service	Legitimate interests
IP address (security logs)	Detect and prevent abuse, account security	Legitimate interests
Email address	Send account-related emails (password reset, email confirmation)	Contract
Email address (marketing)	Send product news and updates, only if you asked for them	Consent

We do not sell your personal data to third parties. We do not use your bookmark content for advertising.

4. End-to-End Encryption (E2EE)

E2EE is an optional feature on Premium, Family, and Business plans. When enabled:

Link titles, URLs, notes, icons, and preview images; group names; tab names; browser session names and their link data; notes widget content; the name and feed address of each connected calendar; the new address a link check found for a moved page; and your profile photo are encrypted in your browser before being sent to our servers. We store and return ciphertext we cannot read.
Preview images and your profile photo are stored as encrypted files. When you turn encryption on, the copies saved earlier are converted, and each unencrypted original is deleted unless another link still uses the same image.
Copies of site icons saved before you turned on encryption remain in our storage as unencrypted files, under names that are not linked to your account in readable form.
Connected calendars: your calendars are fetched by the Zeerka browser extension, directly from your calendar provider. Neither the feed address nor your events pass through our servers, and the events your browser reads are kept encrypted on your device. Because of this, connecting and refreshing a calendar needs the extension while encryption is on.
Your content is encrypted with a random key created in your browser. We store that key only in locked form, and only your passphrase or your recovery code can unlock it. We never receive your passphrase.
Not encrypted: your email address, account and billing details, your display name, information such as how many items you have and when they were created or changed, and the link health results and dates described in Section 2.2 (such as “not found” and when you last opened a link). Like the dates on your items, these say nothing about which sites your links point to; the addresses themselves stay encrypted. Your display name stays readable because we show it to other people — on the invitations you send and in the sharing lists of people you share a tab with.
Feedback you send us (see Section 2.7) is not encrypted either: you are writing it to us, so we can read it.
Zeerka cannot decrypt your content — not for support purposes, not in response to a data breach, and not in response to a legal request.
Important limitation: E2EE protects against server-side data exposure. It does not protect against a compromised device or a compromised Zeerka application itself. This is an inherent limitation of all browser-based encryption systems.

5. Data Sharing and Third Parties

We share data only with the sub-processors required to operate the Service:

Sub-processor	Purpose	Location
Microsoft Azure	Hosting, database, blob storage (link icons, preview images, profile photos)	EU / US
Paddle	Payment processing and subscription management	UK
Google	Social login (optional)	Global
Microsoft	Social login (optional)	Global
Resend	Transactional email (password reset, email confirmation)	US
Brevo	Marketing email (product updates, only to people who asked for them)	EU

We do not share your data with any other third parties.

6. Data Retention

Data type	Retention period
Active account and bookmark data	Kept for as long as your account is active
Deleted items (Trash)	30 days, then permanently deleted
Deleted accounts	Account and all content permanently deleted 30 days after deletion request
Security logs (IP address)	90 days, then permanently deleted
Feedback reports	Kept for as long as your account is active, and deleted with it. If we reply, the email conversation is kept in our support mailbox, as with any email you send us.

7. Your Rights

You have the right to:

Access the personal data we hold about you
Export your data at any time (user menu → Export)
Correct inaccurate data
Delete your account and all associated data
Withdraw your consent to marketing emails at any time, if you gave it (unsubscribe link in every email or by contacting us)

To exercise any of these rights, contact us (see Section 11).

If you are in the European Economic Area, you also have the right to lodge a complaint with your local data protection authority.

8. Cookies and Local Storage

We use the following browser storage:

Cookie / storage	Purpose
Authentication session cookie	Keeps you signed in while your browser is open
Security token cookies	Protect form submissions and API calls from cross-site request forgery (CSRF)
Local storage	Stores UI state and temporarily caches your data to make the app feel faster

All cookies are set by Zeerka and are strictly necessary to operate the Service. We do not use third-party tracking cookies or advertising cookies.

9. Children’s Privacy

The Service is not directed at children under 13. We do not knowingly collect personal data from children under 13. If you believe a child has provided us with personal data, please contact us (see Section 11) and we will delete it.

10. Changes to This Policy

We will notify you of material changes by email or by displaying a notice in the app before the changes take effect. The “Last updated” date at the top of this page reflects the most recent revision.

11. Contact

Zeerka Inc
1338 Wellington Street West, Unit 10
Ottawa, ON K1Y 3B7
Canada
team@zeerka.com
zeerka.com