Privacy Policy

Last updated on October 25, 2026

eKard is an online service for digital business cards, which we call Kards, and for taking bookings. This policy explains what we collect, why, who helps us handle it, how long we keep it, and what you can do about it. It covers ekard.app, our Android app, every Kard and booking page we serve, including those on their owners' own web addresses, and the emails we send. It goes with our Terms and Conditions.

In Short

We don't sell personal data and we don't show ads. No advertising or analytics company tracks you on our pages.
A Kard is public: anyone with its link can see what its owner put on it.
When you share your details on someone's Kard, or book with a business, they get those details and decide what to do with them. We store and deliver them on their behalf.
Most of what we hold stays until it's deleted. To have your whole account deleted, ask at Delete your account or in the app. To see, correct or delete anything else, write to hello@ekard.app.

Who We Are

In this policy, "we" and "us" mean the team that runs eKard. "You" means anyone whose information we handle: people who have an account, including a business's front desk and staff; people who visit a Kard; people who book with a business that uses eKard; and people someone adds to their contacts.

We decide how the information in your own account is used, as this policy describes. When a business, or anyone with an account, collects details through eKard (the contacts on their Kards, their clients and their bookings), they decide what to do with them, and we store and process them for them.

To reach us about anything in this policy, write to hello@ekard.app.

What We Collect

If you have an account

Your account. Your name and email address. If you sign up with an email address, your password, which we keep only as a one-way hash that can't be turned back into the password. If you sign in with Google: your Google account's ID, name, email address and profile picture, updated each time you sign in. If you ask us to delete your account: when you asked and confirmed, and your reason, if you give one. How you came to sign up: the first page of ours you opened, the website that sent you (its domain alone, such as instagram.com, never the page), any campaign tags in the link, the Kard whose page or exchange brought you, and whether you signed up in our app.
Where you are, roughly. The country and time zone of your internet connection, as Cloudflare reports them, saved the first time you open your Kards to set sensible defaults, such as your calendar's time zone.
Your Kards. What you put on them: your name, tagline and description, photo, phone and WhatsApp numbers, email, website, social profiles, a payment address such as a UPI ID, links, documents, events and designs. A Kard is public: anyone with its link can see it. Search engines are asked not to list it unless you switch that on.
Your contacts. People who share their details on your Kards or book from them, and the people you add yourself: typed in, or read off their paper business card in our app (see AI Features).
Your calendar, if you take bookings: your services and prices, your hours, the people on your team (names, titles, contact details, working hours and time off), your clients and their bookings, the notes you keep, and the advances and payments you record (amount, method and tip).
Your organization, if you run one: its name, logo and Kards, its members and their roles, and the email addresses of people you invite.
Payments. Your plan, what you paid and when, and Razorpay's references for your orders, payments and subscription, including the type of payment method (card, UPI or net banking, for example). You enter card or bank details in Razorpay's checkout; we never see them.
What you connect. Your calendar, if you connect one (see Calendar Data from Google and Microsoft). The apps you send new contacts to, if you set one up (see Contacts You Send to Google Contacts and Other Apps). For phone notifications: the address your browser's push service gives us, a description of the browser and device, and which notifications you chose. The API keys you create for an AI assistant or another tool, and the web addresses you set up to receive your bookings (webhooks).
Our Android app. Each phone you sign in on: the name the app gives it, its Android and app versions, and when it last used the app. The keys it signs in with are kept only as one-way hashes. If you turn the app's notifications on: the phone's Firebase installation ID, which Google uses to reach it, and which notifications you chose.
Price lists you import. The photo, PDF, link or text you give the AI import (see AI Features).
Messages to us. What you write when you email us or message us on WhatsApp.

If you visit a Kard

Each visit. When a Kard opens, or one of its links is tapped, we record the time, which Kard and link, the web address your browser says you came from, any campaign tags in the link (a printed QR code adds one), which browser, operating system and kind of device you use, the IP address the visit came from, and the approximate location Cloudflare gives for your connection: country, continent, city and rough coordinates. Saving a Kard's contact card and opening its booking page are counted too, and so are taps on its buttons (Call, WhatsApp, Directions, a way to pay, a profile): which button, never the number, the address or anything you type. We set no cookie to count visits, and we don't link them to your name or account.
What the Kard's owner sees. Totals: views, link and button taps, where visits came from, countries, cities and devices. Never a list of who visited, and never an IP address.
Details you share. If you share your details on a Kard: your name, and whatever else you fill in (email, phone number, a message, and any questions the owner added). They go into the owner's contacts and, if the owner has switched it on, to the owner by email. The owner may also send them to an app they use, such as Google Contacts (see Contacts You Send to Google Contacts and Other Apps). If you give an email address, we send you a copy of the owner's card, at most once a day for each Kard. With your details goes one word for how you reached the Kard (its QR code, a search, a link in a chat, an email), read from your visit: never the address you came from, or anything else about the visit.
If you're signed in. When you share your own Kard back, the owner of the Kard you're visiting gets your Kard's name, phone number, email and link, and any note you add. When you save a Kard, it's kept in your account.

If someone adds you to their contacts

What they enter. Someone with an account can add you in our Android app, by typing your details or scanning your paper business card, or through our API. We keep what they save: your name, phone numbers, email addresses, job title, company, website and address, as they entered them or the card showed them, and their own notes. The photo of your card stays on their phone (see AI Features).
What happens next. They decide what to do with your details, as with any contact. If they choose, we email you their Kard.

If you book with a business

What you give. Your name; your phone number, email address or both, as the business asks; your address, for a visit at your place; your answers to the business's questions; a note; and the email addresses of up to five guests, who get the confirmation too. If you're signed in to eKard, we fill in your name, email and phone for you.
What comes with it. Your time zone, as your browser reports it, and where you booked from: which Kard, a booking link, or the business's own website. An online booking also adds you to the contacts of the Kard you booked from.
Waitlists and suggested times. Your details, and the days and times that suit you.
What the business records. Your bookings and visits, its own notes about you (an allergy, for example), missed and cancelled visits, the payments it records (amount, method and tip), whether you confirmed, and whether it has stopped you booking online. A business can also add you itself: at its front desk, from a phone call, or from a list it imports.
Paying the business. You pay the business directly: an advance it asks for (by UPI, for example) and whatever you pay on the day. We never handle that money or see how you paid. The business records what it received, and whether an advance was refunded or kept.
Messages. We email you your confirmation, reminders before your visit, any change or cancellation, word when a time you're waiting for opens up, and, if the business asks for reviews, a request for one after your visit. Where a booking page offers it and you tick the box, we also send your confirmation and reminders on WhatsApp, until you reply STOP. The business's team can also message you themselves, from their own phones (on WhatsApp, for example).
Your booking's link. Your confirmation carries a private link to see, move or cancel the booking. Anyone who has it can use it, so keep it to yourself.

Everyone

Technical data. Every request to eKard passes through Cloudflare, which sees your IP address, and reaches our servers, which log the page, the time, your IP address and your browser. We also use IP addresses for a short time to stop abuse, such as too many attempts to sign in or book.
Error reports. When something goes wrong, a report goes to Sentry with the page, your browser, the technical details of the error and, if you're signed in, your account's number (never your name or email address), so we can tell how many people a problem hit. Sentry also measures how quickly our servers answer.

Calendar Data from Google and Microsoft

If you take bookings with eKard, you can connect your own Google Calendar or Microsoft 365 / Outlook calendar (Calendar sync). eKard reads and writes nothing there until you connect it and allow access on Google's or Microsoft's own screen, and it uses what it gets for two things only: keeping your busy times off your booking page, and keeping your bookings in your calendar.

What we read. Whether you're busy or free in the calendars you tick, so nobody can book a time you're busy; visitors to your booking page see only which times are free. With Google, we ask for free and busy times only, never your events. With Microsoft, whose permission covers whole events, we read only each event's start and end, its "show as" status, and whether it's all-day or cancelled, never its title, details, place or guests. We also read the list of calendars you own (their names, which one is your main calendar, and whether each can add Google Meet or Microsoft Teams links), so you can choose which to check and where bookings go, and your account's email address, to show which account is connected.
What we write. Only once you've allowed it: each booking becomes an event in the calendar you pick, with what's booked, when and where (for a visit at the client's home, their address), the client's first name and last initial, and a link to the booking in eKard. When the booking moves or is cancelled, we change or delete that event. For a video meeting without a link of its own, we ask Google or Microsoft to add a Google Meet or Microsoft Teams link to the event, and put that link in the booking's emails. The client's phone number, email and notes never go into your calendar, unless you switch on "Add clients to the event as guests", which adds their name and email to the event so that Google or Microsoft sends them an invitation. With Google, we can add events only to calendars you own.
How we protect the access. Google and Microsoft give eKard access tokens, never your password. We keep them encrypted in our database (AES-256-GCM, with the keys kept apart from the database), send them only to Google or Microsoft, over HTTPS, and keep them out of our logs and error reports.
How long we keep it. Busy times are used for two minutes, then read again; nothing else about your events is kept. The tokens stay until you disconnect. When you disconnect, we delete them at once and keep only the connected account's email address, its calendars' names and ids, your choices, and which bookings we added as events, so that connecting the same account again carries on updating those events. To have those deleted too, write to hello@ekard.app; to delete your whole eKard account, use Delete your account.
Disconnecting and removing access. "Disconnect", under Calendar sync in eKard, stops all reading and writing at once. For Google, it also tells Google to revoke eKard's access. Microsoft gives apps no way to do that, so remove eKard yourself in your Microsoft account: account.live.com/consent/Manage for a personal account, or myapps.microsoft.com for a work or school account. You can also remove eKard from your Google Account at any time, at myaccount.google.com/connections. Events already added stay in your calendar until you delete them there.
Never sold, never for ads or AI. We don't sell calendar data, use it for advertising, or use it to train AI models, ours or anyone else's. We don't share it with anyone, except the service providers described below that run eKard for us (our servers, and error reports that can name a calendar Google or Microsoft couldn't check), and where the law requires. Nobody at eKard reads it, unless you ask us to help with a problem, for security, or where the law requires.

eKard's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Contacts You Send to Google Contacts and Other Apps

You can have each new contact on your Kards sent to an app you use: your Google Contacts, your HubSpot, or an app or web address you choose. Nothing is sent until you, or your team's admins, set it up, and you can stop it at any time.

Google Contacts

You can connect Google Contacts in a Kard's Settings, under "Send new contacts to other apps", or in Connected apps. eKard reads and writes nothing there until you allow access on Google's own screen, and it uses what it gets for one thing only: keeping the people you meet in your own Google Contacts.

What we send, and when. Each new contact on the Kards you switch on, usually within a minute of their arriving: people who share their details or their own Kard with you, book a time or suggest one, and the people you, or an app with your API key, add. You can switch on the Kards you hold and, while you run a team, the team's Kards. Each person becomes a contact in your Google Contacts with their name, email addresses, phone numbers, company and job title, a link to their own Kard if they shared it, their website, and a note: their message, their answers to your questions, any notes with their details, how they came and how they found your Kard, the event, which Kard, the date, your own note, and a link to them in eKard. It carries a label named "eKard", which we make the first time, and, out of sight, eKard's own id for the contact, so that a retry never adds them twice. "Add the ones you already have" sends a Kard's earlier contacts the same way, when you ask.
What we read, and why. To avoid adding someone twice, we search your Google Contacts for each new person's email addresses, then their phone numbers. Google answers with the contacts that match, with their names, email addresses, phone numbers, company and job title, websites, notes and labels; we use these only to tell whether one is the same person and, for a contact you entered yourself, which of its fields are empty. "Add the ones you already have" reads the email addresses and phone numbers of all your contacts once, for the same check. We also read your Google account's email address, to show which account is connected; the names of your labels, to find one named "eKard"; how many contacts that label holds, for "Check connection"; and, if Google's answer to an add was lost, which of the label's contacts carries our id, to find the one we added. We keep none of it, apart from Google's id for each contact we added or matched.
Someone already in your contacts. They keep everything they have: we add the label, link them to the contact in eKard, and change nothing else. Only if you entered the contact yourself (typed in, or read off their paper card) do we also fill the fields that are empty there, never one that has something in it. Nothing a visitor typed on your Kard, or an app or AI agent added with your API key, is ever written into a contact you already have, because we can't check that the email or phone number they gave is theirs. Their details stay in eKard.
What we never do. We never delete a contact or a label in your Google Contacts, change a field that has something in it, or send a contact's later changes: each person is sent once, and one you delete there isn't added again. Deleting a contact in eKard leaves it in Google Contacts.
How we protect the access. Google gives eKard access tokens, never your password. We keep them encrypted in our database (AES-256-GCM, with the keys kept apart from the database), send them only to Google, over HTTPS, and keep them out of our logs and error reports.
Stopping it, and what stays. Switching a Kard off stops its new contacts going there. "Disconnect", in Connected apps (in your account menu), stops it for every Kard at once: it tells Google to revoke eKard's access and deletes the tokens. You can also remove eKard from your Google Account at any time, at myaccount.google.com/connections. The contacts already added stay in your Google Contacts, with their label, until you delete them there. After you disconnect, we keep the account's email address and Google's id for it, the label's id, Google's id for each contact we added or matched, which Kards sent there, and each Kard's last 50 deliveries, so that connecting the same account again carries on without adding anyone twice. To have those deleted too, write to hello@ekard.app; deleting your eKard account revokes the access and deletes them all.
Never sold, never for ads or AI. We don't sell anything we get from your Google Contacts, use it for advertising, or use it to train AI models, ours or anyone else's. We don't share it with anyone, except the service providers described below that run eKard for us (our servers, and error reports that can quote what Google said about a contact it refused), and where the law requires. Nobody at eKard reads it, unless you ask us to help with a problem, for security, or where the law requires.

eKard's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

HubSpot

You can connect your own HubSpot in a Kard's Settings or in Connected apps, and a team's admins can connect the team's HubSpot in the team's Settings, under Apps. You allow it on HubSpot's own screen, to read and write contacts, and eKard uses that access for one thing only: keeping the people you meet in that HubSpot account.

What we send, and when. Each new contact on the Kards sending to it, usually within a minute: the same people as for Google Contacts. Each person becomes a HubSpot contact with their first and last name, email address, phone number, company, job title and website (their own Kard if they shared it, otherwise their website), and a note on its timeline: their message, their answers to your questions, any notes with their details, how they came and how they found your Kard, the event, which Kard, the date, your own note, and a link to them in eKard. "Send the ones you already have" sends a Kard's earlier contacts the same way, when you ask.
What we read, and why. To avoid adding someone twice, we look up the new person's email address in your HubSpot or, if they gave none, their phone number. HubSpot answers with the matching contact's name, email address, phone and mobile numbers, company, job title and website; we use these only to tell whether it's the same person and, for a contact you entered yourself, which are empty. If HubSpot's answer to an add was lost, we look for what we may have added (a contact made since with the details we sent, or a note on it with its link to eKard), so nothing is added twice. When you connect, HubSpot tells us the account's id, name and web address, and what you allowed: we keep these, to show which account is connected. It also tells us the email address of the person who connected it, which we don't keep. "Check connection" reads the account's id and name again. We keep none of the contacts' details, only HubSpot's id for each contact we added or matched, and for its note.
Someone already in your HubSpot. They keep everything they have: we link them, add the note, and change nothing else. Only if you entered the contact yourself (typed in, or read off their paper card) do we also fill the fields that are empty there. What a visitor typed on your Kard, or an app or AI agent added with your API key, goes in the note alone, never into the contact's fields, because we can't check that the email or phone number they gave is theirs. We never set a lifecycle stage, lead status or contact owner: those stay yours.
What we never do. We never delete anything in your HubSpot, change a field that has something in it, or send a contact's later changes. Deleting a contact in eKard leaves it in HubSpot.
A team's HubSpot. The team's admins choose which of its Kards send to it, and the people who hold those Kards see that they do. If the admin who connected it leaves the team, is made a member or deletes their account, it pauses: new contacts stay in eKard, unsent, and the team's other admins are emailed to keep sending to that HubSpot account or to connect another.
How we protect the access. HubSpot gives eKard access tokens, never your password. We keep them encrypted in our database (AES-256-GCM, with the keys kept apart from the database), send them only to HubSpot, over HTTPS, and keep them out of our logs and error reports.
Stopping it, and what stays. Switching a Kard off stops its new contacts going there. "Disconnect", in Connected apps (a team's, in the team's Settings under Apps), stops it for every Kard at once: it asks HubSpot to revoke eKard's access and deletes the tokens, and if HubSpot doesn't confirm, we say so. HubSpot keeps eKard in your account's list of apps until you remove it there, in Settings › Integrations › Connected Apps. The contacts and notes already added stay in HubSpot until you delete them there. After you disconnect, we keep the account's id, name and web address, HubSpot's ids for the contacts we added or matched and the notes we added, which Kards sent there, and each Kard's last 50 deliveries, so that connecting the same account again carries on without adding anyone twice. To have those deleted too, write to hello@ekard.app. Deleting your eKard account does the same for your own HubSpot and deletes them all; a team's HubSpot stays the team's, paused for its other admins.
Never sold, never for ads or AI. We don't sell anything we get from your HubSpot, use it for advertising, or use it to train AI models, ours or anyone else's. We don't share it with anyone, except the service providers described below that run eKard for us (our servers, and error reports that can quote what HubSpot said about a contact it refused), and where the law requires.

Webhooks and Zapier

A web address you give a Kard. If you or your team's admins give a Kard a web address for its new contacts (a webhook: a Zapier or Make hook, or your own server), each new contact on that Kard goes there as it arrives, with their details, message and answers, your note, how they came and which Kard, until you remove the address.
An app you give your API key. If an app you've given your API key, such as Zapier, asks to hear about new contacts, each new contact on the Kards it asks about (the ones you hold and, while you run a team, the team's) goes to the address it gives, until it stops asking or you replace the key.

Google Maps on Kards

A business can link its Kard to its listing on Google Maps. The Kard then shows the business's Google rating and, when a visitor asks for them, up to five of its Google reviews, from Google's Places API.

What we keep. Only the listing's ID on Google Maps, on the Kard. We never store the business's name, rating or reviews, or anything else Google sends: each comes from Google when someone looks, goes straight to their screen, and isn't kept by us, by Cloudflare or in your browser's cache.
What Google gets from us. Our server asks Google for the listing by its ID, in the language the Kard is shown in. It sends nothing about the visitor: not your IP address, your device or anything you typed. When a business owner searches for their business, Google gets the words they type. When a business owner looks at their linked listing, Google sends the listing's address, hours, phone and website so the owner can compare them with their Kard; we show them once and keep none of them.
What your browser fetches from Google. Reviewers' profile photos load from Google's servers straight into your browser, so Google sees your IP address and browser, as with any picture on the web; your browser is asked not to tell Google which page they're on. The links to Google Maps (all the reviews, a reviewer's profile, Write a review) open Google, where Google's privacy policy applies.
If you wrote one of the reviews. Your review is public on Google Maps. A Kard shows it as Google gives it, with your name, photo and a link to your Google profile, in Google's order, and the business can't hide it. To change or delete it, do it on Google Maps: the Kard shows the change the next time someone looks.
Counts. To stay within our budget for Google Maps, we count how many times we ask Google, and what it costs, for each Kard and day, for each account's Kards in a month, and for a business owner's own searches and looks in a day: only the numbers, never which visitor looked or what Google said. We keep each Kard's daily counts for 13 months, and the others until their day or month ends. To stop one network asking for ratings too often, we also count its asks by part of its IP address, for each Kard and for all Kards together, for a day at most.
Address suggestions. When you type a street address on a Kard, our server sends Google Maps the words you've typed so far, the country you chose (else your account's, else the country your connection comes from), your browser's or app's language and a random number that groups one search, and shows you Google's suggestions. Nothing else: not your name, email, account or IP address. When you pick one, Google sends us that address in its parts. We keep the address as you save it, and the place's ID on Google Maps so Directions open the exact place. We don't keep Google's other suggestions or the place's map coordinates. We count your suggestions and picks in a day, and each search's, only the numbers, until the day ends.

How We Use It

To run eKard: to show Kards, pass on the details people share, take and change bookings and remind people of them, keep connected calendars up to date, and send the emails and notifications that go with all of this.
To keep it safe: to sign you in, check email addresses, stop abuse and spam, and find and fix errors.
To show Kard owners and businesses how they're doing, in totals: views, link taps, contacts and bookings.
To run paid plans: to take payments and keep track of what each account has paid for.
To help you when you write to us.
To keep you informed. Some emails always come, such as password resets and booking confirmations. The others (new contacts, a monthly summary, milestones, tips in your first days, and updates about your Kards) can be switched off at Email preferences or from any of those emails.
To understand how eKard is used, from totals such as how many people sign up each day, and where they came from.
To meet legal obligations, and to protect the people who use eKard, and eKard itself.

Where the law asks for a reason (a "legal basis"), ours are: providing the service you asked for; our legitimate interest in keeping it safe, working and improving; your consent, for the connections and messages you switch on, which you can take back at any time; and our legal obligations.

We don't sell personal data, we don't use it for advertising, and we don't train AI models on it.

AI Features

Price-list import. A business can turn a printed or typed price list into draft services. We send photos and scanned pages to Moonshot AI (its Kimi model; Moonshot AI stores data in Singapore), and typed or pasted text, or the text of a PDF, to DeepSeek (which stores data in China). They read the list and send back draft services, which the business checks; nothing is added until it confirms. We delete the upload within 24 hours, or as soon as the business confirms or discards the import. Our record of AI requests keeps the text that was read (never the photos) and the list that came back.

Under their own terms, Moonshot AI and DeepSeek may keep what they receive and use it to improve their AI models, so please leave other people's personal details out of a price list you import.

Reading a paper business card. In our Android app, you can add a contact by scanning their paper business card. The phone reads the card's text itself, with Google's text recognition, and the photo stays on the phone. We send that text to Anthropic (its Claude model; Anthropic stores data in the United States), which sorts it into fields, such as the name, phone numbers and email addresses, for you to check before you save. On our website, on a paid plan, you can instead upload photos of the business cards you've been given (Contacts, then Scan cards): we send each photo to Anthropic, which reads every card in it into fields the same way, and we delete the photo as soon as it's read. Apart from the contacts you save, we keep nothing of the cards, the photos or Anthropic's replies, only what each request cost, how long it took and how many cards it read. Under its commercial terms, Anthropic doesn't train its models on what we send it.

Design help. Our team can ask Kimi to rework a Kard's design. Kimi receives the design's code and the instruction, never the Kard's contacts or bookings.

Who Else Handles It

These companies do work for us, and handle data under their own terms and privacy policies:

DigitalOcean runs our servers and database in India, and one mail server in the United States.
Cloudflare carries all traffic to eKard, protecting it and speeding it up; stores the files you upload (photos, documents and QR codes) and our encrypted backups of the database; and tells us the approximate location of each connection.
Amazon Web Services sends our emails (Amazon SES).
Google lets you sign in with Google, connects Google Calendar if you choose, and hosts our own email (Google Workspace), so the messages you send us are stored there. Google Maps gives Kards their businesses' Google ratings and reviews, and suggests addresses as you type them (see Google Maps on Kards). In our Android app, Google delivers the notifications (Firebase Cloud Messaging), including what they say, such as a client's name and the time of their booking; and its scanners in Google Play services read QR codes and paper business cards on your phone.
Microsoft connects Outlook and Microsoft 365 calendars, if you choose.
Razorpay takes payments for paid plans. It gets a reference to your account when you sign up, your name and email for its checkout, and the payment details you enter there.
Sentry receives error reports and speed measurements, in the United States.
Moonshot AI and DeepSeek read price lists for the AI import (see AI Features).
Anthropic reads the text of paper business cards scanned in our Android app (see AI Features).
Google, Mozilla, Apple and Microsoft deliver phone notifications in your browser, through the push service of the browser you use. Browser notifications are encrypted, so these services can't read them.
jsDelivr serves the phone-number field on signed-in pages, so it sees your IP address when they load.
Meta carries booking messages on WhatsApp, where a booking page offers them.

We also share data:

With the people you choose: the owner of a Kard you share details on; the business you book with, and its team; the guests you add to a booking.
With tools a business or account holder connects. If a business sets up a webhook, details of its bookings, including each client's name and contact details, go to the address it chose. A Kard's new contacts go to the apps its owner or their team sets up, as Contacts You Send to Google Contacts and Other Apps describes. If you give an AI assistant or another tool your API key, it can read and change your account's data through our API.
When the law requires it, or to protect someone's safety or rights.
If eKard changes hands, in a merger or sale, with the new owner, who must keep to this policy.

Cookies

We use a few cookies to make eKard work. None is for advertising or follows you to other sites, and counting Kard visits uses none.

Signing in. One cookie keeps you signed in while your browser is open; it also protects forms from forgery and remembers a few things between pages, such as where to go back to after you sign in. Another keeps you signed in on that browser until you sign out.
Booking. After you book, a cookie remembers your booking for 30 minutes, so that a refresh or a second tap shows it instead of booking twice. When the booking page sits inside a business's own website, this cookie comes from us, not from that site.
Picking up where you left off. Short-lived cookies remember a Kard you were saving while you signed in (5 minutes) and a team invitation you were accepting (1 day).
Preferences. Cookies remember which calendar you open first, that you've answered the question about phone notifications, and which of your devices this browser is, for notifications. That last one goes when you sign out; the others stay until you clear them.
Your browser's own storage. After you share your details on a Kard, your browser notes it, so the Kard stops offering the form. The note stays on your device.
Our Android app's storage. The app keeps your sign-in on your phone, sealed with Android's Keystore, and copies of what it shows you, so it works without a signal. Signing out of the app deletes them.

Pages from other companies follow their own cookie policies: Razorpay's checkout on our pricing page, and Google's and Microsoft's pages when you sign in or connect a calendar. Cloudflare may also set a cookie to tell people from bots. You can block or delete cookies in your browser's settings, but without the sign-in cookies you can't sign in.

How Long We Keep It

Your account, and everything in it: until you delete it (see Your Rights and Choices). We keep a record of the request, with your email address, when you asked and confirmed, and your reason, after the account is gone.
A Kard: until you delete it. That deletes its page, documents, and visit and link-tap records at once. The contacts it collected are no longer shown anywhere, but stay in our database until you ask us to delete them.
Contacts: until the Kard's owner deletes them.
Visit records: for as long as the Kard exists.
A business's clients, bookings and waitlists: for as long as the business keeps them in its calendar.
Price lists you import: the upload is deleted within 24 hours (see AI Features).
Business cards read in the app: nothing of the card's text or the reply, apart from the contact you save (see AI Features).
Calendar connections: see Calendar Data from Google and Microsoft.
Contacts sent to other apps: see Contacts You Send to Google Contacts and Other Apps.
A Kard's Google rating and reviews: never kept. The listing's ID on Google Maps stays on the Kard until its owner removes it or Google no longer finds the listing (see Google Maps on Kards).
A Kard's address place ID: until its address changes or Google no longer finds the place (see Google Maps on Kards).
Phone notifications: until you turn them off, sign out of that browser or the app, or the browser or phone stops accepting them.
The app's sign-ins: the list of phones signed in to your account, ended or not, until your account is deleted.
The website's sign-ins: each browser signed in to your account, named by its browser and system (such as "Chrome on Windows", never the browser's own description), with when it signed in and was last used, while it's signed in and for 6 months after it ends, or until your account is deleted. Signing out of a browser ends its sign-in here, so a copy of its cookie no longer works.
Backups: we back up the database every 6 hours, encrypted, and keep the last 2 days of backups, one a day for the last 14 days and one a month for the last 12 months. So something deleted from eKard stays in older backups for up to 12 months, until they're deleted in turn.
Server logs: overwritten automatically as they fill up, usually within days. Error reports: kept by Sentry for up to 90 days.
If you unsubscribe from emails: we keep your address on our unsubscribe list, so that we keep honoring your choice.
Messages you send us: in our mailbox, for as long as we need them to help you.

Your Rights and Choices

Wherever you live, you can ask us to:

show you the personal data we hold about you, and give you a copy;
correct it;
delete it;
send it to you in a format other software can read;
stop or limit a use of it, or take back a consent you gave.

You can do much of this yourself: edit or delete your Kards and contacts, download your contacts (and, if you run a calendar, your clients) as a spreadsheet, choose your emails at Email preferences, disconnect a calendar, and turn phone notifications off.

Deleting your account. Ask at Delete your account, or in the app. We email a link to your account's address, and once you confirm, we delete the account within 30 days, with your Kards and the contacts and visit records they collected, your calendar with its clients and bookings, and the phones and browsers signed in to it. Team Kards you hold in an organization stay with it, without your details. We email you when it's done. An organization you run isn't deleted with your account: write to hello@ekard.app about it. Can't sign in? Write to us from your account's email address instead. Copies stay in our encrypted backups for up to 12 months (see How Long We Keep It), and we may keep what the law requires us to keep, such as records of payments.

For anything else, write to hello@ekard.app. We'll answer within 30 days, and may first ask you to show that the account or data is yours. You can also complain to the data protection authority where you live.

If a business or someone else holds your details, because you're in the contacts on their Kard, they added you, or you booked with them, they decide what happens to them. Ask them first. If they can't help, write to us and we'll work it out with them.

Children

eKard isn't meant for children. You need to be 18 or older to create an account, and we don't knowingly collect personal data from children. When a child needs a booking (a lesson or a check-up, say), a parent or guardian should make it. If you think a child has given us personal data, write to hello@ekard.app and we'll delete it.

Where It's Stored

Our servers and database are in India, apart from one mail server in the United States. Our encrypted backups of the database are with Cloudflare. Some of the companies above store or process data elsewhere: Sentry and Anthropic in the United States, Moonshot AI in Singapore, DeepSeek in China, and Cloudflare, Google, Microsoft, Meta, jsDelivr and the push services across their networks around the world. So your data may be handled in a country other than yours, whose data protection laws may differ from your own.

How We Protect It

Your browser's connection to eKard is always encrypted (HTTPS), and browsers are told never to connect without it.
Passwords, and the keys our Android app signs in with, are kept only as one-way hashes. Card and bank details go to Razorpay, never to us.
The keys to connected calendars and WhatsApp accounts, and the secrets that sign webhooks, are encrypted in our database (AES-256-GCM).
Backups of the database are encrypted before they leave our server, and the key that opens them is kept apart from them.
Private links (a booking's own link, calendar feeds, a team member's "My day" page) are long random codes, and search engines are told not to list them. A calendar feed or "My day" link can be replaced at any time.
Inside eKard, people see only what their role allows: a business's front desk and staff see its calendar, not its settings, and no business sees another's data.
Only the people who run eKard can reach the data behind it, and only to run, support or secure the service, or where the law requires.

No system is perfectly secure. If a breach puts your data at risk, we'll tell you, and the authorities where the law requires, as soon as we can.

Changes to This Policy

When we change this policy, we'll post the new version here and update the date at the top. If a change matters, such as a new kind of data or a new company handling it, we'll also email account holders before it takes effect.

Contact Us

For questions, requests or complaints about privacy, write to hello@ekard.app. Our Terms and Conditions cover the rest of how eKard works.