Last updated 27 August 2026
Contact Pack exists to move contact details from one phone to another. It holds the least it can to do that, for the shortest time it can.
Contact Pack never asks for your name, email address or a password, and there is nothing to sign up for. Nothing you do in the app is tied to an identity, because there is no identity to tie it to.
The app reads your address book so you can pick people from it. That reading happens entirely on your device. Your contacts are not uploaded, scanned, indexed or analysed, and no part of your address book leaves your phone unless you build a pack and share it.
Packs you have made are stored on your device. They are not synced to us or anywhere else.
A pack carries whatever the contacts you picked already have on them: names, phone numbers, email addresses, postal addresses, photos, company, job title and department, websites, birthdays and other dates, related people, social profiles and instant messaging handles.
On Pro you choose which of those travel, field by field, and can narrow further by label — every mobile number but no work ones, say. Names are always included; a contact without one cannot be shown or saved. On the free plan a pack carries everything the contact has.
Whatever you choose, it is encrypted before it leaves your phone. The choice is about what reaches the person you sent it to, not about what we can see — we cannot see any of it.
Sharing a pack uploads it to our server, because that is what lets the link work for someone who does not have the app. Before it leaves your phone it is encrypted, and the key never leaves with it.
The key travels in the share link itself, after the #. Browsers do not send that
part of a link to the server, so the key reaches the person you sent it to and never reaches us.
Contact details are decrypted in the recipient's browser or app, not on our server.
This is not a promise not to look. We hold a block of scrambled data and no way to open it. If our server were stolen, breached, or we were asked to hand a pack over, there would be nothing in it to read.
Two things are deliberately not encrypted: the pack's name, and how many people are in it. We need them to title the page and to show a preview when the link is pasted into a chat. So we can see that a pack is called "Soccer Team 2026" and holds four people — and nothing at all about who those people are.
We also store when the pack was created and when it expires. That is the whole record.
Anyone holding the whole link can. Pack addresses are twelve random characters and
the key after the # is another forty-three, so neither can be guessed, and packs are
never listed, searchable or indexed. But the link is the only lock on the door — treat it the way
you would treat the contact details themselves, and send it only to people you mean to have it.
Sending the link without the part after the # is the same as sending nothing:
the pack cannot be opened, by them or by us.
Packs shared on the free plan are deleted two weeks after they were created. On Pro you choose: a day, a week, a month, or no expiry at all — a pack set never to expire is kept until you delete it.
Deleting a pack removes the record from the server and the link stops working immediately. Photos travel inside the encrypted block rather than being stored separately, so they go with it.
A free link is a snapshot. If you edit a pack you have already shared, the link you sent keeps serving what it was made from, and sharing again produces a second link; both records exist until they reach their two weeks, then both are deleted. A Pro link is updated in place instead, so editing the pack changes what that link shows.
Expired and deleted packs are removed permanently. There is no archive.
A pack contains information about people who are not you. Share one only with those who have a reason to have it, and only when the people in it would expect you to. If you are in a pack someone else shared and want it taken down, ask them to delete it — they can do so from the app, and it takes effect at once.
Our server briefly holds the IP address a pack was published from, in memory only, to limit how many packs can be created from one place in an hour. It is never written to disk and never attached to a pack. Error logs record that a request failed, not what was in it.
Subscriptions are handled by Apple through the App Store and by RevenueCat, our billing provider. We never see your payment details. All we receive is whether an active subscription exists.
If this policy changes, the date at the top changes with it.
Email [email protected].