Kromigo

Privacy Policy

Last updated: September 30, 2026

This policy explains what Kromigo, a service provided by A Singh Who Codes (“we”, “us”), collects when you text, or call, a restaurant that uses our SMS ordering service. It covers why we collect it, and what we do and don't do with it.

What we collect

  • Your phone number. We receive it when you text a restaurant's number. It's how the restaurant replies to you.
  • Your name, only if you provide it, so the restaurant knows whose order it is.
  • Your messages: the content of your conversation with the ordering assistant, and its replies.
  • Your orders: items, options, totals, and your answers to the restaurant's checkout questions, such as pickup or delivery and payment method.
  • Missed calls. If the restaurant has call recovery switched on, we record your number and the time and outcome of a call their line didn't answer. See If you call and can't get through.
  • Service records: message counts, timestamps, delivery status and the cost of each message, so we can run and bill the service.

We do not ask for or store your payment card details. Payment for food happens directly with the restaurant at pickup or delivery.

How we use it

To operate the ordering service: understanding what you want to order, pricing it correctly, delivering the order to the restaurant, and texting you order updates such as confirmation, an estimated ready time, and when your food is ready. We also keep records of message volume and cost so we can run the service reliably and bill the restaurant. We do not use your messages or order history to advertise to you, and we do not sell them.

Your information is kept separate per restaurant

This is a deliberate design decision, not just a policy. Your customer record, meaning your phone number, your name and your order history, is scoped to the individual restaurant you ordered from. A restaurant using Kromigo can only ever see its own customers and its own orders. If you order from two different restaurants that both use our service, they are two independent records, and neither restaurant can see the other's.

There is exactly one exception, and it is a single yes-or-no fact. So that the assistant can answer honestly if you ask whether it recognises you, it is told whether your number has used Kromigo before at some other restaurant. It is never told which restaurant, never given a name from there, and never given an order from there, and it asks you for your name fresh, exactly as it would a first-time customer. Beyond that one bit, we do not build a cross-restaurant profile of you.

If you call and can't get through

Some restaurants forward calls their own line couldn't answer to their Kromigo number. When that happens we don't answer the call. We end it, so it can fall through to their voicemail, and we text you once to say you can order or ask questions by text instead. That message includes STOP instructions.

This is the only message we send that you didn't start, so to be explicit about it: we receive and store your phone number and the time and outcome of that call, we send at most one recovery text per caller in a 30-minute window, and we never send one to a number that has opted out of that restaurant's messages. There is no recording and no transcription, because the call is never answered, so there is nothing to record.

Who we share it with

We do not sell your personal information. We share it only with the parties needed to deliver the service:

  • The restaurant you're ordering from. They receive your order, name, phone number, and conversation. If new-order emails are switched on for them, we also email them your order: your name, what you ordered, your pickup or delivery details and the total, but not your phone number. That email is delivered by our email provider, SMTP2GO.
  • Our messaging carrier (Telnyx), to actually send and receive the text messages and to handle the forwarded calls described above.
  • Our AI provider. The content of your messages is sent to a third-party AI service to generate the assistant's replies. This is how the assistant understands your order. See The AI assistant below.
  • Our error-monitoring provider (Sentry). When something goes wrong, the diagnostic report can include your phone number and, occasionally, the text of a reply we stopped from being sent. It is used only to fix faults.
  • When legally required, if compelled by law.

The AI assistant

Your messages are processed by Fireworks AI, which runs the model that powers the assistant. To generate each reply, we send it your message along with the restaurant's menu and hours.

We send these requests with retention switched off. Fireworks documents that, in this mode, prompt and generation data exist only in volatile memory for the duration of the request and are not written to persistent storage, and that they do not use it to train or improve their models without explicit opt-in. Two honest caveats: they do log service metadata such as the number of tokens in a request, and where prompt caching is active some prompt data can remain in volatile memory for several minutes.

We do not send your phone number to the AI provider. The assistant is told your first name, once you give it, and what you've said, but never your number. Your order is linked to it on our side, not by the model. We don't send payment details either, because we never collect them.

How your messages are stored

The content of your messages is encrypted at rest in our database. That covers both our record of the texts themselves and the assistant's memory of your conversation. They can't be read by inspecting the database directly; that includes by us, without the application's encryption key. Your phone number and order details are stored unencrypted, because the restaurant needs to be able to look your order up.

Opting out

Reply STOP to any message to stop receiving texts from that restaurant, including missed-call texts. STOPALL (or STOP ALL), UNSUBSCRIBE, CANCEL, END and QUIT do the same thing. You'll get one confirmation and then nothing further. We keep a record that you opted out; that record is precisely what lets us honour it and not text you again.

Opting out is per restaurant, so sending STOP to one restaurant does not opt you out of another. Reply START or UNSTOP to opt back in, and HELP at any time for the restaurant's contact details.

Retention

We keep conversation and order records for as long as needed to operate the service and for the restaurant's own business records. If you'd like your information deleted, contact the restaurant you ordered from, or email us and we'll work with them to action it, subject to any records they're required to keep. An opt-out record is the one thing we keep regardless, because deleting it would mean losing the instruction not to text you.

Restaurant accounts

If you use the Kromigo portal to operate a restaurant, we store your name, email address, and login credentials, and use cookies to keep you signed in. These cookies are strictly necessary for the portal to function. We don't run advertising or analytics trackers on this site.

Subscription billing is handled by Stripe, and card details are entered on Stripe's own pages: they never pass through, and are never stored by, Kromigo. We hold the resulting customer and subscription identifiers, your plan, and your order counts, which is what an invoice is calculated from. Account email, meaning payment failures, trial reminders, password resets and, if they're switched on for your restaurant, new-order notifications, is delivered by SMTP2GO.

Changes

We'll update this policy as the service evolves. Material changes will be reflected in the “last updated” date above.

Contact

Questions about your information, or want it deleted? Contact the restaurant you ordered from directly, or email us at info@asinghwhocodes.com. See also our Terms of Service.