ExpoCards privacy
Last updated: 30 September 2026
ExpoCards turns a photograph of a business card into a contact you can review, correct and export. This page explains what the app does with that data.
What is stored, and where
- Contacts and card photos are stored on your device, in the app's own storage. They are not uploaded to us for storage, and we keep no copy of them that we can read: if you use Teams (below), our server keeps an encrypted copy of your team's list, without the key to open it.
- Your settings — app name, logo, accent colour and event tag — are stored on your device in the same way.
- There is no sign-in and nothing to register: we never ask for your name, email or a password. There is no advertising and no tracking.
- We keep one kind of count on our website: when you open expocards.app/get from a link carrying a tag, such as ?ref=li-page-en, we add one to that tag's count for the month, so we know which of our links people follow. If you then tap the App Store button there, we add one to a second count for that tag, and the link you tap carries the tag to the App Store, so that Apple can tell us how many downloads each of our links brought. Nothing else is recorded: no IP address, cookie or anything that identifies you or your device. Opened without a tag, the page counts nothing. (The hosting provider's standard request logs, described below, apply to that page as to every request.)
What leaves your device
- When you scan a card, the photo is sent over an encrypted connection to our scanning service, which passes it to Anthropic's Claude API to read the text. The details it reads are returned to your device. Our service does not store the photo or the details: once the response has been sent, it no longer has them.
- With the photo goes the language chosen under "Translate cards into" in Settings: a language code such as "en", nothing about you. In the same reading, Anthropic's Claude then also writes the card's name, company and job title in that language, and they come back to your device with the other details. Set it to Off and no language is sent.
- A QR code in the photo is read by the app on your phone, before anything is sent. When the code holds the contact details (a vCard, for example), the photo is not sent at all unless you tap "Read the printed card too". "Scan a QR code" sends nothing either, unless you then ask for the photo to be read.
- Anthropic processes the image to produce the response. Under its published data-retention policy Anthropic deletes inputs and outputs within 30 days — or later if its safety systems flag a request, or the law requires it — and by default does not use them to train its models. See Anthropic's privacy policy for details of their handling.
- The app generates a random id at first launch. It is sent with each scan, and when the app starts or you open Settings, so the app can show how many scans you have left. Our server keeps a count of scans against that id, and the month of its first scan (which decides its free scans: 10 that month, then 5 a month), so the monthly allowance and anything added to it can be honoured. The id is not derived from your device or your identity, and is erased from the device by "Erase all data".
- Like any internet service, our server and its hosting provider see the IP address a request comes from, and the provider keeps standard request logs for a limited time. We use the address to limit abuse, and the country it is in to choose the currency of our prices. The counters we keep against abuse are stored under a scrambled form of the address (a one-way hash of its network), never the address itself: a count per network for a couple of minutes, and, while a launch gift of scans is running, a count per network for up to two days; the AI helpers (below) keep a count per network for up to two days as well; Teams (below) keeps a count per network of new teams and of invites that did not work, for up to two hours. We do not use it to locate you beyond the country, and we do not share it.
- Nothing else is sent to us (apart from Teams, below, if you use it), except what an AI helper sends when you tap it (below). Viewing, editing, searching and exporting your contacts all happen entirely on the device and work with no connection.
- If you have device backups switched on — iCloud on an iPhone, Google backup on Android — the app's data may be included in your own backup. That is between you and Apple or Google; we never see it.
Who processes data for us
Vercel hosts the scanning service. Upstash stores the scan counters, the encrypted copies of team lists and the link counts. Anthropic reads the card photo, and writes the summaries and reads the company websites you ask about (below). Apple handles payments in the iPhone app; Stripe handles any payment made in the web version or in the Android app from our website. None of them receives your contact list in a form it can read, and none of them is given anything for advertising or profiling.
Where the data is processed
- Vercel runs our server (the scanning service, the Teams relay and the AI helpers). Vercel is a US company, and its main processing facilities are in the United States. Vercel is certified under the EU–US Data Privacy Framework and its UK Extension, and its data processing terms also include the EU standard contractual clauses and the UK's addendum to them.
- Anthropic reads card photos and writes what the AI helpers show. It stores data in the United States, and may process a request on its servers in other countries. The transfer is covered by the EU standard contractual clauses, with the UK Addendum, in Anthropic's data processing terms.
- Upstash keeps the scan counts, purchase records and link counts, and the encrypted copies of team lists, in the United States (N. Virginia, AWS us-east-1). Upstash is certified under the EU–US Data Privacy Framework and its UK Extension.
- The service you pay through (Apple, for the App Store) handles your payment details under its own privacy policy.
AI summaries and About their company
Three optional helpers work on contacts you have already saved. None of them runs by itself: each sends something only when you tap it, and only with a connection.
- Summarise notes sends that contact's name, job title, company, city, country and event tag, with the notes you typed, to our service, which passes them to Anthropic's Claude AI to write a short summary and a suggested next step. Today's leads does the same for the contacts you saved today (each one's notes cut to 500 characters) to write one recap. Card photos, email addresses and phone numbers are never sent.
- About their company sends only the company's name and its website address to our service and on to Anthropic. The address is the website on the card or, if there is none, the part after the @ of a work email address (for example "example.com": never the email address itself, never a free-mail domain such as gmail.com, and never a social network). Anthropic then fetches one page of that company's own website, and Claude writes three or four lines on what the company does, its size if the page states it, and where it is based. There is no web search, and nothing about the person is sent or looked up: not their name, job title, email address or phone number, your notes or the card photo. The website sees a request from Anthropic, not from you. The app asks you once before the first time. What comes back is shown with the page it came from, and it can be out of date.
- What is kept. The summary, the recap and what About their company wrote are saved on your device, with the contact (the day's recap with the app's settings). The summary is included in exports; all of them are included in backups; none of them is shared with a team. Our service keeps none of it: once it has answered, it no longer has what you sent or what came back. Anthropic handles it as it handles card photos (above). Our server logs record only how many tokens a request used and how many pages it read, never names, companies, websites, notes or results.
- Counting. To keep these helpers within their daily limits, our server keeps, for two days, how many summaries and company look-ups the app's random id and each network (from the IP address) used that day. They use scans from the same allowance as scanning cards, as the app shows on each button.
- Other people's data. A company's name and website are business details, but a sole trader's business can be a person: use what About their company tells you only to follow up the contact who gave you their card (see "Other people's data" below).
Resúmenes con IA y «About their company» (en español)
Tres ayudas opcionales trabajan sobre contactos que ya has guardado. Ninguna se pone en marcha sola: cada una envía algo solo cuando la tocas, y solo con conexión.
- Summarise notes (resumir notas) envía el nombre, el cargo, la empresa, la ciudad, el país y la etiqueta del evento de ese contacto, con las notas que escribiste, a nuestro servicio, que los pasa a Claude, la IA de Anthropic, para escribir un resumen breve y un siguiente paso. Today's leads (los contactos de hoy) hace lo mismo con los contactos que guardaste hoy (las notas de cada uno, recortadas a 500 caracteres) para escribir un único resumen del día. Nunca se envían fotos de tarjetas, direcciones de correo ni números de teléfono.
- About their company (sobre su empresa) envía solo el nombre de la empresa y la dirección de su sitio web a nuestro servicio y de ahí a Anthropic. La dirección es el sitio web de la tarjeta o, si no hay, lo que va detrás de la @ de un correo de trabajo (por ejemplo «example.com»: nunca la dirección de correo en sí, nunca un dominio de correo gratuito como gmail.com y nunca una red social). Anthropic descarga entonces una página del propio sitio web de la empresa, y Claude escribe tres o cuatro líneas sobre a qué se dedica, su tamaño si la página lo indica y dónde está. No se hace ninguna búsqueda web y no se envía ni se busca nada sobre la persona: ni su nombre, ni su cargo, ni su correo, ni su teléfono, ni tus notas, ni la foto de la tarjeta. El sitio web recibe la petición de Anthropic, no la tuya. La app te pregunta una vez antes de la primera. Lo que vuelve se muestra con la página de la que sale, y puede estar desactualizado.
- Qué se guarda. El resumen, el resumen del día y lo que escribió «About their company» se guardan en tu dispositivo, con el contacto (el del día, con los ajustes de la app). El resumen se incluye en las exportaciones; todos se incluyen en las copias de seguridad; ninguno se comparte con un equipo. Nuestro servicio no guarda nada: en cuanto responde, ya no tiene lo que enviaste ni lo que volvió. Anthropic lo trata igual que las fotos de tarjetas (más arriba, en inglés). Los registros de nuestro servidor anotan solo cuántos tokens usó cada petición y cuántas páginas leyó, nunca nombres, empresas, sitios web, notas ni resultados.
- Recuento. Para mantener estas ayudas dentro de sus límites diarios, nuestro servidor guarda durante dos días cuántos resúmenes y consultas de empresa usó ese día el identificador aleatorio de la app y cada red (a partir de la dirección IP). Usan escaneos del mismo cupo que el escaneo de tarjetas, como la app indica en cada botón.
- Datos de otras personas. El nombre y el sitio web de una empresa son datos de negocio, pero el negocio de un autónomo puede ser una persona: usa lo que te diga «About their company» solo para hacer seguimiento del contacto que te dio su tarjeta (ver «Other people's data», más abajo).
Teams
Teams (Settings → Team) lets the phones on a stand share one contact list. Nothing is shared unless you start or join a team.
- What is shared. Every contact on the team's list: the details read from the card, your notes, the event tag and “Assign to”, and the name each member types for themselves. Card photos are not shared; they stay on the phone that took them. When you start or join a team you choose whether the contacts already on your phone join the list.
- Encrypted, and we don't have the key. Before anything leaves your phone it is encrypted with a key that only the team's phones hold. Our service, hosted by Vercel, keeps that encrypted copy with Upstash so that a phone can catch up after being offline. We don't have the key, so we can't read the contacts, notes or names in it. What our service does see: random ids for the team and for each phone, when changes are sent and how large they are, and the IP address a request comes from. The id used for counting scans is never sent with team data, with one exception: from when ExpoCards Unlimited is on sale, the phone that starts a team sends its anonymous account id, and our service keeps it with the team, so that it can check that the person who started the team has ExpoCards Unlimited running. It is deleted automatically at most 90 days after the team was last used.
- Who can read the list. Every phone in the team, and anyone who joins with a live invite: a code or link that works for 24 hours (from when ExpoCards Unlimited is on sale, for up to 14 days if the member who makes it chooses) and for up to 10 people. Any member can remove a phone; a removed phone keeps what it already has.
- How long it is kept. Until the team is deleted, or until 90 days after the team was last used, when it is deleted automatically. A contact deleted in a team disappears from every phone's list, but its encrypted entry stays in the copy until the team is deleted or expires.
- Where. Upstash stores the copy, still encrypted end to end, in the United States (N. Virginia, AWS us-east-1), and our server, run by Vercel, passes it on. How each transfer is protected is in "Where the data is processed" above.
- Leaving and deleting. Settings → Team → Leave team takes your phone out; when the last phone leaves, the team is deleted. Any member can choose “Delete team for everyone”, which erases our copy at once. “Erase all data” also takes the phone out of its team. In every case each phone keeps the contacts it already has.
Equipos (en español)
Con Equipos (Settings → Team), los teléfonos de un stand comparten una sola lista de contactos. No se comparte nada hasta que creas un equipo o te unes a uno.
- Qué se comparte. Cada contacto de la lista del equipo: los datos leídos de la tarjeta, tus notas, la etiqueta del evento y «Assign to» (asignar a), y el nombre que cada miembro escribe para sí. Las fotos de las tarjetas no se comparten: se quedan en el teléfono que las hizo. Al crear un equipo o unirte a uno eliges si los contactos que ya tienes en el teléfono pasan a la lista.
- Cifrado, y no tenemos la clave. Antes de salir de tu teléfono, todo se cifra con una clave que solo tienen los teléfonos del equipo. Nuestro servicio, alojado en Vercel, guarda esa copia cifrada en Upstash para que un teléfono pueda ponerse al día después de estar sin conexión. No tenemos la clave, así que no podemos leer los contactos, las notas ni los nombres que contiene. Lo que sí ve nuestro servicio: identificadores aleatorios del equipo y de cada teléfono, cuándo se envían los cambios y su tamaño, y la dirección IP de cada petición. El identificador con el que se cuentan los escaneos nunca se envía con los datos del equipo, con una excepción: desde que ExpoCards Unlimited está a la venta, el teléfono que crea un equipo envía su identificador anónimo de cuenta, y nuestro servicio lo guarda con el equipo para comprobar que quien lo creó tiene ExpoCards Unlimited activo. Se borra automáticamente como máximo 90 días después del último uso del equipo.
- Quién puede leer la lista. Cada teléfono del equipo, y cualquiera que se una con una invitación vigente: un código o enlace que vale 24 horas (desde que ExpoCards Unlimited está a la venta, hasta 14 días si así lo elige el miembro que lo crea) y para un máximo de 10 personas. Cualquier miembro puede quitar un teléfono; el teléfono quitado conserva lo que ya tiene.
- Cuánto tiempo se guarda. Hasta que se elimina el equipo, o hasta 90 días después de su último uso, cuando se elimina automáticamente. Un contacto eliminado en un equipo desaparece de la lista de todos los teléfonos, pero su entrada cifrada sigue en la copia hasta que se elimina el equipo o caduca.
- Dónde. Upstash guarda la copia, que sigue cifrada de extremo a extremo, en Estados Unidos (Virginia del Norte, AWS us-east-1), y nuestro servidor, que funciona en Vercel, la transmite. Upstash y Vercel están certificados en el Marco de Privacidad de Datos UE-EE. UU. y su Extensión para el Reino Unido, y las condiciones de Vercel incluyen además las cláusulas contractuales tipo de la UE (más detalle en «Where the data is processed», más arriba, en inglés).
- Salir y eliminar. Settings → Team → Leave team saca tu teléfono del equipo; cuando sale el último teléfono, el equipo se elimina. Cualquier miembro puede elegir «Delete team for everyone» (eliminar el equipo para todos), que borra nuestra copia en ese momento. «Erase all data» también saca el teléfono de su equipo. En todos los casos, cada teléfono conserva los contactos que ya tiene.
- Quién es responsable. Un equipo se crea para una organización, que decide para qué sirve su lista: de esa lista la organización es la responsable del tratamiento, y nosotros guardamos la copia cifrada por cuenta suya, como encargado, con las condiciones de tratamiento de datos de nuestras condiciones de uso (apartado 5a). Como no podemos leer la copia, las solicitudes de las personas de las tarjetas las atiende la organización, desde sus teléfonos.
Your own database (web app only)
If — and only if — you open Settings → Advanced, enter your own Supabase project URL and key and switch sync on, your contacts are also copied to that Supabase project. That project is yours: we have no access to it, and the app never contacts it while sync is switched off. A phone in a team cannot use it at the same time.
Payments
The web version and the Android app sell nothing at present: purchases are made in the iPhone app, through Apple. The rest of this paragraph is for when that changes. If you buy scans or an event pass in the web version, or in the Android app from our website, the payment is processed by Stripe on Stripe's own pages. In the iPhone app, Apple processes the payment through your Apple Account. Your card details never pass through this app or its servers. To work out VAT, Stripe asks for your billing address, and a business can add its VAT number; Stripe keeps both in our Stripe account, with the receipt it emails you, for our tax records. So is the country your connection came from, as tax rules require evidence of where each buyer is. Our own servers record only what you bought, when, the payment provider's reference for it, and the app's anonymous account id it belongs to, so your purchase can be honoured. Stripe and Apple also receive that random id with each purchase (Stripe as a note on the payment, Apple as the purchase's account token), so the purchase reaches the right install; the id itself says nothing about who you are.
ExpoCards Unlimited bought in the iPhone app also runs on your other devices with the same Apple Account, and after a reinstall: up to five installs of the app. Its purchase record then lists those installs' random ids (at most five), and we note for 400 days that they belong together, so that a team started on one can follow you to another.
Why we use it
UK and EU data protection law asks us to say why we use each kind of data, and on what basis.
- To provide what you asked for: reading the cards you photograph, counting your free and added scans, adding a purchase to the right install (and an App Store purchase to your other devices), running a team you start or join, and the AI helpers you tap. The basis is our contract with you: without it we could not provide the service.
- To prevent abuse and keep the service working for everyone: the per-minute and per-network counters, the hosting provider's request logs, and the purchase record that stops one purchase being added twice. The basis is our legitimate interest in a service that is fair, safe and not misused. You can object to this at any time (see "Your rights").
- To keep the tax records the law requires for payments taken on our behalf. The basis is a legal obligation.
How long we keep it
- Card photos, and what is read from them: not kept by our service at all. Anthropic deletes them within 30 days, as described above.
- This month's scan count: about 45 days. The month of the first scan: 400 days from that scan.
- Scans added to the id, bought or given: until you ask us to delete them, because they never expire. A note of scans given as a launch gift: 400 days; the marker that stops the gift being given twice: until you ask us to delete it.
- A running pass, such as ExpoCards Unlimited: until 30 days after it ends.
- Purchase records: at least six years, as UK tax law requires. The record of an App Store purchase has no end date, because it is what stops one purchase being added twice; on request we remove the app ids from it. The note that installs belong to one Apple Account: 400 days after the last purchase that linked them.
- Stripe's records of a web or Android payment (billing address, any VAT number, the country): kept in our Stripe account as our tax records, six years for UK VAT and ten years where EU VAT applies to a sale to an EU consumer. Our server's own notes of a checkout: 7 to 30 days.
- Counters kept against abuse: 2 minutes for the per-minute ones, up to 2 days per network, 2 hours for Teams' per-network count. The AI helpers' daily counts: 2 days.
- A team's encrypted copy: until the team is deleted, or 90 days after it was last used.
- Link counts from our website: 400 days. They hold nothing about you.
- The hosting provider's request logs: for a limited time, under Vercel's own policy.
- Emails you send us: as long as we need them to answer you and follow up.
Exporting and deleting
- You can export your contacts at any time as a vCard, CSV or Excel file, or download a full JSON backup, and take that data elsewhere.
- Deleting a contact removes it, and its photo, from the device. "Erase all data" in Settings removes everything the app holds on the device, including the random id.
- The scan count our server holds against that id stays behind, for as long as "How long we keep it" says: scans added to an id are kept so they can be honoured. To have the server-side record deleted, copy the id first (Settings, About, tap to copy) and email it to us.
- Removing the app deletes its local storage along with it.
- If your phone is in a team, deleting a contact removes it from every phone's list in the team; “Erase all data” first takes the phone out of the team. The team's encrypted copy is erased when the team is deleted (Settings → Team → Delete team for everyone), or 90 days after its last use.
Your rights
- Under UK and EU data protection law you can ask us for a copy of the data we hold about you, and ask us to correct it, delete it, limit how we use it, or give it to you in a form you can take elsewhere. You can object at any time to what we do on the basis of our legitimate interests.
- We never ask who you are, so our server knows you only by the app's random id: copy it from Settings → About (tap to copy) and include it when you write. "Erase all data" removes that id from the phone, so copy it before you erase. We answer within one month at the latest. Write to help@expocards.app
- If you are unhappy with how we handle your data, you can complain to the Information Commissioner's Office in the UK (ico.org.uk), or to the data protection authority where you live in the EU. We would be glad to hear from you first.
Other people's data
The details on a business card belong to the person who gave it to you. You are responsible for handling them lawfully — including under the GDPR or any other rules that apply to you — and for honouring any request from that person to see or delete what you hold.
A team is set up for an organisation, which decides what its list is for: for that list the organisation is the controller, and we store the encrypted copy on its behalf, as its processor, under the data-processing terms in our terms of use (section 5a, Teams). Because we cannot read the copy, requests from the people on the cards are answered by the organisation, from its phones.
Children
ExpoCards is a business tool and is not directed at children.
Who we are, and contact
This app is published by Adam Michel Monir Hakim Ayad, an individual developer based in the United Kingdom, who is the data controller for what is described here. Questions about this policy, or requests about your data: help@expocards.app. We aim to reply within two working days.