Legal
Privacy Policy
Version 2.1 · Effective September 19, 2026
1. Who we are
BiteLeague is operated by Capernaum LLC, a limited liability company organized under the laws of the State of Georgia, United States. In this policy, "we," "us," and "our" refer to Capernaum LLC. "You" refers to anyone who uses the BiteLeague mobile application or website.
This policy explains what information we collect, why we collect it, who we share it with, and what control you have over it.
2. What we collect
BiteLeague waitlist
If you join the BiteLeague waitlist, we collect your email address. We use it to send you occasional updates about BiteLeague before and after launch and to notify you when the BiteLeague app becomes available. Joining the waitlist does not create a BiteLeague account. You can unsubscribe from these emails at any time.
Account information
When you create an account, we collect your email address and a display name you choose. We do not ask for or store your real name. A display name can be anything you like and does not need to identify you. You may optionally add a phone number, a profile photo, and your home state.
If you sign in using Google or Apple, we keep only your email address; we never receive your password. Those providers also send us your real name and profile photo, and we discard both rather than storing them. Your account starts with a generated avatar, and a photo is stored only if you choose to upload one.
Content you submit
When you claim a dish, you upload a photo of the dish and a photo of your receipt. You may also submit dish names and descriptions, vote on dishes, save restaurants to a list, and indicate whether a visit was your first to a restaurant. This content is associated with your account.
Receipt information
To verify dish claims, we process your receipt photo using an automated text-recognition service. From that process we store the merchant name, date, total amount, and individual line items, along with the full text extracted from the receipt.
Because we store the complete extracted text, any information printed on your receipt may be retained — including the last digits of a payment card, where a merchant prints them. We do not collect, request, or store full payment card numbers, and we do not process payments. To limit what is retained, you may obscure any portion of a receipt before photographing it, so long as the merchant name, date, and claimed item remain legible.
Location
With your permission, we use your device's location to find restaurants near you and to determine your city during setup. Your coordinates are used to perform that search and are not stored in our database. We request location only while you are actively using the app; we never access your location in the background. You can decline or revoke this permission in your device settings, and the app will continue to work — you will need to search by name or area instead.
Camera and photo library
When you add a dish photo, a receipt, a restaurant banner, an event photo, a support screenshot, or an owner verification document, you choose whether to take a new photo or pick an existing one. We ask for permission only for the option you choose: the camera if you choose to take a photo, your photo library if you choose to pick one. Choosing one does not grant the other.
We do not browse, scan, or index your photo library. We receive only the specific images you select or capture, and a photo taken in the app is used for the submission you were making. Once submitted, camera photos and library photos are treated identically — the same storage, the same retention described in section 6, and the same visibility described in section 7.
You can decline or revoke either permission in your device settings. Declining the camera still lets you upload from your library, and declining both means you can use everything in BiteLeague except the parts that require a photo.
Restaurant owner verification
If you apply to manage a restaurant listing, we collect your contact name, role, email address, and phone number, along with documents you upload to prove your association with the business. These typically include two utility bills, a business license, and optionally one additional document such as a lease, EIN letter, or bank statement. These documents are stored privately and are accessible only to our administrators for the purpose of reviewing your application.
Support requests
When you contact support through the app, we collect your email address, subject, and message, along with technical details that help us diagnose the problem: app version, build number, platform, and device information. You may optionally attach a screenshot.
What we do not collect
We want to be specific about this, because most apps cannot say it. BiteLeague contains no third-party advertising networks, no analytics SDKs, no crash-reporting services, and no attribution or tracking software. We do not track you across other apps or websites. We do not build advertising profiles. We do not sell your data, and we never have.
3. How we use your information
We use the information described above to operate, secure, and communicate with you about BiteLeague:
- To send BiteLeague waitlist subscribers occasional product updates and a launch announcement
- To create and maintain your account and keep you signed in
- To verify dish claims against receipts and award points
- To show you restaurants and dishes near you
- To let restaurant owners review claims involving their business and, where applicable, appeal a decision
- To review restaurant ownership applications
- To send you notifications within the app about your claims and account
- To respond to your support requests
- To detect and prevent fraudulent claims, abuse, and violations of our Terms of Service
- To comply with legal obligations
We do not use your information for automated decision-making that produces legal effects, and we do not use your information for targeted or behavioral advertising.
4. Who we share it with
We share information only with the service providers required to run the app, and only to the extent each one needs:
- Supabase — hosts our database, authentication, and file storage. Account information, waitlist email addresses, submitted content, and uploaded files are stored on their infrastructure.
- Google Places — provides restaurant listings, hours, and details. When you search nearby, we send approximate coordinates to bias results toward your area. We do not send your name, email, or any account identifier.
- Google Cloud Vision — performs automated text recognition on receipt photos. The receipt image is sent for processing. No account identifier is attached.
- Expo — delivers over-the-air app updates and receives basic device and version information as part of that process.
We may also disclose information if we are required to by law, subpoena, or valid legal process; to investigate suspected fraud or threats to safety; or in connection with a merger, acquisition, or sale of assets, in which case we will notify you before your information becomes subject to a different policy.
We do not sell your personal information, and we do not share it for cross-context behavioral advertising.
5. How long we keep it
- Waitlist email addresses — until the earliest of: you unsubscribe, you create a BiteLeague account using that email address, or 12 months after BiteLeague launches. If you create a BiteLeague account, your email address is removed from the waitlist and is thereafter retained as part of your account information. If you do not create an account, we delete your waitlist email address no later than 12 months after launch.
- Receipt photos and extracted receipt text — 12 months. We keep these long enough to resolve owner appeals and investigate fraudulent claims, then delete them.
- Account information — for as long as your account is active. If you delete your account, we delete this information.
- Dish photos and submitted content — may remain visible after account deletion in aggregate or anonymized form, disassociated from your identity, so that restaurant listings other users rely on remain intact. When your account is deleted, your display name and profile photo are removed from this content and it is credited only as “BiteLeague member”. We never reassign your content to another person or to an invented account.
- Owner verification documents — for as long as the ownership claim is active, and for 12 months after it ends or is denied.
- Support requests — 24 months, so we can reference past issues.
We may retain information longer where required by law or where necessary to resolve an active dispute.
6. Your choices and rights
You can:
- Access and correct your account information in the app at any time
- Delete your account, which removes your account information from our systems
- Unsubscribe from BiteLeague waitlist emails at any time using the unsubscribe option included in those emails or by contacting us
- Revoke location permission in your device settings without losing access to the app
- Request a copy of the information we hold about you
- Ask us to delete specific content you have submitted
To make any of these requests, email support@biteleague.app. We will respond within 30 days. We may need to verify your identity before acting on a request, to protect your account from someone impersonating you.
BiteLeague is offered from the United States and is intended for users in the United States. Depending on where you live, your state may give you additional privacy rights beyond those described here. If you believe you have such rights, contact us and we will honor any that apply to you.
7. How we protect it
Receipt photos, owner verification documents, and support screenshots are stored in private storage that is not publicly accessible. When these files need to be viewed by an authorized reviewer, access is granted through short-lived links that expire after 30 minutes. Database access is restricted by row-level security rules so that users can reach only their own records. All traffic between the app and our servers is encrypted in transit.
Dish photos, restaurant banner images, and event photos are publicly accessible, since they are meant to be seen by other users on restaurant listings. Do not include anything private in a dish photo.
Your display name and profile photo are shown publicly next to content you submit, such as dishes and dish photos, so other users can see who contributed. Your email address, phone number, and receipt images are never shown to other users. If you would rather not be identifiable, choose a display name that is not your real name, and do not use a photograph of yourself.
No system is perfectly secure. If we become aware of a breach affecting your personal information, we will notify you and any required authorities as the law requires.
8. Children's privacy
BiteLeague is not intended for children under 13, and we do not knowingly collect personal information from anyone under 13. If you believe a child under 13 has provided us information, email support@biteleague.app and we will delete it promptly.
9. Changes to this policy
We may update this policy as BiteLeague develops. When we make material changes, we will update the date at the top of this page and notify you in the app before the change takes effect. Continuing to use BiteLeague after a change means you accept the updated policy.
What changed in version 2.1
Effective September 19, 2026:
- Added a Camera and photo library section. The app can now take photos directly instead of only choosing existing ones, so the policy describes both permissions, when each is requested, and what happens if you decline.
No new kind of information is collected. The same dish photos, receipts and documents are stored, used and retained exactly as before — only the way you can provide them has changed — so no re-acceptance is required.
What changed in version 2.0
Effective September 13, 2026:
- We stopped collecting real names. Accounts now use a display name you choose, and the real name supplied by Google or Apple at sign-in is discarded rather than stored.
- We stopped copying the profile photo that Google and Apple send at sign-in. Accounts start with a generated avatar, and we store a photo only if you upload one yourself. Photos previously imported this way have been deleted.
- We now state plainly that your display name and profile photo appear publicly beside content you submit. This was not described in version 1.0.
- We describe what happens to your contributions when you delete your account: they may remain on restaurant listings, credited only as “BiteLeague member”, with your name and photo removed and never reassigned to anyone else.
Because this change affects what is shown publicly about you, we are asking existing users to review and accept version 2.0 when they next open the app. Version 1.0, effective September 12, 2026, remains the policy that applied before this date.
10. Contact us
Questions about this policy or about your information:
Capernaum LLC
Email: support@biteleague.app
Web: biteleague.app