Your receipt, your table.

The Halvsies owner can review receipts and problem reports to troubleshoot the service. Access to the owner dashboard is restricted. Basic operational events, such as receipt creation, changes, and processing failures, help us understand what went wrong. These activity logs do not contain receipt text, photos, participant names, phone numbers, or sign-in credentials. Receipt inspection and administrative changes are logged too.

Halvsies is an early version for splitting receipts with friends. The sample receipt uses made-up people and does not send payments.

For shared splits, the creator signs in and guests can either sign in or enter a display name. Accounts keep receipts you create or join, your choices, and the display names at those tables. Creating an account from the guest account prompt keeps that same guest identity and its receipts. Vercel hosts the site, and Supabase stores account information, receipts, memberships, and choices. Earlier versions also stored payment reports. People who join a split can see its receipt details, participants, and choices. Only share an invitation with people you want at that table. Before joining, an active invitation also shows the available names the creator added, so guests can choose their existing place. Choosing a listed name keeps any items already assigned to it.

Google handles Google sign-in. Where phone sign-in is available, Supabase and Twilio Verify process your phone number and verification code to sign you in. Your account phone number and sign-in credentials are not included in the receipt shared with other participants. Halvsies uses phone numbers for authentication, not marketing texts.

You can choose a display name and add an optional profile photo. People at splits you have joined can see your chosen name and photo. Profile photos are resized, cropped to a square, stripped of embedded metadata, and stored privately in Supabase; they are not sent to the receipt-reading AI. You can replace or remove your photo in Account settings. Replaced and removed photos are deleted from our storage, with scheduled retries if deletion fails. Your profile is separate from your sign-in phone number and email.

When you upload a receipt, we store the photo privately in Supabase and send a resized copy to Meta’s Muse Spark 1.3 Standard model through Vercel AI Gateway to read its items and amounts. We remove embedded photo metadata from that copy. The creator reviews and edits the result before sharing a split.

When receipt texting is available, Twilio receives the photo and message you send to Halvsies. We keep a private intake record with your sending number, a reference to the photo, and an optional party count; we do not save the rest of your caption. Only a signed-in account with that confirmed phone number can import it. The private review link expires after 24 hours. At expiry, automatic cleanup removes the intake’s phone and photo references and requests deletion of its Twilio media, with retries if a service is unavailable. A message identifier remains for seven days to prevent duplicate processing. After import, the privately stored receipt photo follows the seven-day photo policy below. Twilio may retain other message records under its own service policies. Texted photos are not scanned by the AI model until you open the link and confirm access. Each text accepts one receipt photo. In the private review, you can add more photos, supported receipt links, or manual receipts and combine up to five receipts into one shared split. Each photo keeps its own storage expiry, and people who join the split can view the included receipt details and available photos.

We use receipt-texting phone numbers and messaging consent information to deliver the replies you request and protect access to your receipts. Message frequency depends on your requests. Message and data rates may apply. We do not sell or share mobile numbers or messaging opt-in information with third parties for marketing or promotional purposes. We share this information with service providers such as Supabase and Twilio only as needed to operate authentication, deliver requested messages, and protect the service. Reply STOP to stop receipt texts or HELP for help when texting is available.

If you paste a supported Toast receipt link, Halvsies requests that receipt page from Toast and reads its visible items, add-ons, and amounts directly, without sending it to an AI model. The link and original page are not saved with your split. Reviewed entries are saved just like a manually entered receipt. We keep a bounded set of recent import times for your account to limit repeated requests.

Receipt photos are available to the creator and people who join the resulting split. Access expires seven days after upload, when automatic deletion is scheduled. Deletion retries if a storage service is temporarily unavailable. Removing a photo earlier also deletes our stored copies. Reviewed receipt details remain part of the split. Meta and Vercel process the photo under their own service policies; this photo expiry applies to Halvsies storage.

Halvsies shows your share and a link to the creator’s payment profile. Payments happen in your chosen payment app; Halvsies does not transfer money, confirm payment, or read your Venmo account. Your amount can change when the table’s choices change.

If you choose to report a problem, we privately store your message, problem category, screen name, and session identity so we can investigate. Reports from a split can include its reference after we verify you have joined it. We do not automatically attach receipt photos or private invitation links. Guests can send reports without creating an account.