Punchya

Punchya

Privacy Policy

Effective November 7, 2026 · Last updated November 7, 2026

1. Who we are

Punchya is published by Bacon Cheese Frosting LLC ("BCF", "we", "us"), a Wyoming limited liability company.

1309 Coffeen Ave, Ste 1200, Sheridan, WY 82801, United States
[email protected] · +1 (307) 316-2342

This policy explains what Punchya collects, what it doesn't, who can see what, where the data goes, and how to get rid of it. It covers the Punchya iPhone app, its widgets and notifications, and the invitation page at punchya.com.

2. The short version

A punch has no words in it. It's a tap that says "it happened", and you and the other person have already agreed what it means. So there is no message for us to read, store, scan or lose, because none is ever written.

What we do need is the minimum to get a punch from one phone to another:

We also learn how Punchya is used in aggregate: what kinds of phones and languages people use, roughly where (city, not street), and how punches flow. We look at groups of people, never at individuals.

We don't sell your data, we don't share it for advertising, and we don't track you across other apps or websites. Punchya has no advertising and no advertising identifier. There's no App Tracking Transparency prompt because there's nothing to ask.

The rest of this policy is the detail.

3. What we collect

a. Your account

There's no email address, no password and no profile photo.

b. Punches

Each punch, and each punch back, is stored as a record of:

That's all a punch is. There's no text, no location, no photo and no audio in it.

c. Your contacts

If you let Punchya see your contacts, it checks which of them already use Punchya:

  1. On your phone, each phone number is put through a one-way function (a salted SHA-256 hash) that turns it into a long code.
  2. Only those codes are sent to us. Your contacts' names, and the rest of your address book, stay on your phone.
  3. We compare the codes with the codes of people on Punchya, and tell your phone which ones matched. Then we forget the list: the codes you sent aren't stored.

A hash is not encryption. Phone numbers are short enough that someone with our app and enough computing power could work backwards from a hash to the number. We treat hashes as personal data and protect them that way, and we never show anyone another person's hash.

The exception is someone you invite (§3e). When you invite a contact, their hash and the name you have saved for them are stored on your Punch List, so the invitation can show on your list while you wait for them.

d. Groups

If you make a group, we store its name, who's in it, who made it, and whether it's shared. People in a shared group see its name and the initials of the other members. They see a member's full name only if that person is already on their own Punch List.

e. Invitations

When you invite someone, your phone sends the invitation, as an ordinary text from your Messages app and your number. We don't send texts to anyone and we never see your invitee's number.

We store a pending punch for them: who it's from, their number's hash, and when it expires. If they join within seven days, that punch is waiting for them. If they don't, it's deleted.

The link in the invitation is the same for everyone (punchya.com/invite). It carries nothing about you or them.

f. Names, and reporting a name

Names are checked when you save them, so the worst can't be used. A name that's refused isn't kept.

If you report a name, we receive the name, whether it's a person's or a group's, a code that identifies the account that chose it, and the time. We don't record who sent a report, and a report contains nothing anybody has sent. We delete a report once we've dealt with it. If we change a name to initials, we keep a record that we did (the old name and the date) so we can handle someone who does it again. That record is deleted with the account.

g. Your phone and notifications

h. Usage and device information

To see how Punchya is used and whether it works for the people using it, we collect:

We use this only to report on groups of people, for example "people whose phones are set to Spanish punch back more often" or "the cities where Punchya is growing". It never includes your name or phone number, and it isn't used to identify, profile or advertise to you. We don't use the advertising identifier, and Google Signals and ad personalization are turned off.

i. Crash reports and server logs

j. Microphone and speech recognition

Punchya asks for your microphone and speech recognition for one thing: naming a group out loud instead of typing it.

It listens only after you tap the microphone on the "Name this group" screen, and stops when you tap again or pause. Your words are turned into text on your iPhone, using Apple's on-device speech recognition. The sound isn't recorded or saved, and your voice is never sent to us, to Apple or to anyone else. If your iPhone can't recognize speech on the device, Punchya doesn't send your voice anywhere to be recognized. It opens the keyboard instead.

The only thing that leaves your phone is the name you save, exactly as if you'd typed it.

k. What stays on your phone

Punchya keeps an Activity log on your phone for troubleshooting (Settings › Diagnostics). It isn't sent to us. Display preferences that aren't listed in §3a also stay on your phone.

l. What we never collect

We don't collect your precise location. Punchya never asks for location access, and it never receives your location from your phone, even if you use Punchya alongside other apps or automations. We also don't collect your contacts' names (except someone you invite, §3c), your email address, photos, calendar, health or financial data, browsing history, or the words of anything, because a punch has none. We don't use the advertising identifier (IDFA), and Punchya contains no advertising and no advertising SDKs.

4. What other people can see

This is where Punchya differs most from apps you may know, so it's worth being exact.

5. Who processes it

We use a small number of services to run Punchya. Each acts on our behalf, under its own data-processing terms:

ServiceWhat it does for Punchya
Google (Firebase and Google Cloud)Sign-in and the sign-in text message, the database, our server code, notifications delivery, App Check, settings, usage analytics, crash reports, server logs
AppleDelivering notifications (Apple Push Notification service), App Attest, on-device speech recognition
CloudflareHosting punchya.com and the invitation page

The invitation itself is sent by your phone through your own carrier, as any text you send.

6. How we use it

To run Punchya: sign you in, find the people you know, deliver punches and show them on both phones, run groups and invitations, protect the service from abuse, and fix what's broken. We use punch records and usage information (§3h) in aggregate to understand how Punchya is used: which ways of punching people prefer, how often and how quickly punches are answered, how use grows or fades over time, and how all of that differs by device, language and region. These are reports about groups, never about a person.

We don't use any of it to build a profile of you, to make automated decisions about you, or to advertise to you. We don't sell it, and we don't share it for advertising or cross-context behavioral advertising.

7. Your choices

8. Retention and deletion

Deleting your account (Settings › your name › Delete account) removes, straight away:

What stays, and why. A punch you sent is part of the other person's history too. So it isn't deleted: it's anonymised. The sender is replaced with the same placeholder used for every deleted account, so nothing on it can be connected to you. A punch someone sent you stays in their history the same way.

Otherwise:

Deleting the app doesn't delete your account. Use Delete account first.

9. Children

Punchya is not directed at children, and you must be at least 13 to use it. We don't knowingly collect information from anyone under 13. If you believe a child has given us information, write to [email protected] and we'll delete it.

10. California residents

If you live in California, the CCPA/CPRA gives you rights to know what personal information we collect, to have it deleted, and to correct it. The categories we collect are described in §3; there are no others. We don't sell personal information and we don't share it for cross-context behavioral advertising, and we haven't done so in the preceding twelve months. We don't collect sensitive personal information as that term is defined, including precise geolocation, and we don't offer financial incentives for personal information. To exercise these rights, use Delete account in the app, or write to [email protected].

We won't discriminate against you for exercising any of these rights.

11. Residents of other U.S. states

A number of other states, including Virginia, Colorado, Connecticut, Utah, Texas, Oregon and others, have consumer privacy laws granting rights comparable to those in §10, such as access, deletion and correction. If you live in one of them, we extend the same commitments to you, on the same terms as §10. Write to [email protected].

We don't sell personal data, and we don't process it for targeted advertising or profiling.

12. Canada

Punchya is available in Canada. If you live there, you have the right to access the personal information we hold about you and to ask us to correct it, under PIPEDA and provincial law. Write to [email protected]. Your information is stored and processed in the United States (§14), where it may be accessible to U.S. authorities under U.S. law.

13. Security

Data is encrypted in transit and at rest. Every request to our servers must come from a signed-in user and a genuine copy of the app (§3g). Each person can read only their own records; everything else goes through server code that checks who's asking. Punches carry no words, so even a breach couldn't reveal what anyone said to anyone. No system is completely secure, and we don't claim ours is.

14. Where data is processed

Punchya is available in the United States and Canada. Our database and server code run in Google Cloud's us-central1 region, in the United States.

15. Changes

If we change this policy in a way that matters, we'll post the new version at this address with a new effective date and, if the change expands what we collect, say so in the app.

16. Contact

Bacon Cheese Frosting LLC
1309 Coffeen Ave, Ste 1200, Sheridan, WY 82801, United States
[email protected] · +1 (307) 316-2342