Privacy policy

1. Overview

Delitero is self-serve online ordering software for businesses in the United States. This policy covers everyone who touches the service: businesses that use Delitero and the people who work for them (owners, managers, staff, and delivery drivers), customers who order from a business's ordering page or embedded widget, and visitors to delitero.com.

The short version: we store what is needed to take, pay for, and fulfill an order, and nothing else. Card numbers go to Stripe and never reach us. There are no advertising trackers and no analytics cookies on any page we serve. We do not sell personal data, we do not use it to train models, and we never market to a business's customers.

2. What we store about a customer

A customer orders without an account. For each order we store the contact details given at checkout: name and phone number, and an email address if one is entered, which is used to send the receipt. For a delivery order we also store the delivery address (street, unit, city, state, ZIP) and any delivery note.

The order itself: items, options, per-item notes, the order note, prices, fees, tax, tip, any promo code, the fulfillment mode and the chosen time, timestamps, and the order's full status history. After payment, Stripe reports the outcome to us and we store the card brand, the last four digits, and Stripe's payment and charge identifiers. We never receive or store a full card number.

Order texts are consented and off by default. The checkbox at checkout is unchecked when the page loads. If a customer ticks it, we store that consent, the moment it was given, and the phone number it was given for, and we send one text when the order reaches the stage that text is for. Leaving the box unticked sends nothing and stores no consent.

Order chat, where a business has it switched on, stores the messages in the thread and any photo a customer attaches. A message removed by its sender leaves a marker in place of its content. Threads about a specific order are visible to that business and, while the delivery is out, to the driver carrying it; a driver never sees order totals or refund amounts.

A post-delivery tip, if a customer chooses to add one, is a separate payment through Stripe. We store its amount, any tax on it, and Stripe's identifiers for it, on the order it belongs to.

If someone reports a chat thread for abuse, we keep a point-in-time copy of that thread and its images as evidence for 90 days, separately from the live thread, so a report can still be reviewed after the thread itself is gone.

3. What we store about a business and its people

Account: the account holder's name and email address, and the password stored only as a salted hash, never in plain text. Team members carry a name, email address, and role.

Business profile: name, phone, email, address, time zone, opening hours, pickup and delivery settings, the phone number chosen for order escalation, promotions, receipt branding, and the ordering-page and banner images uploaded.

Menu: categories, items, descriptions, prices, availability, container sizes, and the photos uploaded.

Compliance attestations: where a state requires a business to confirm it holds its licences or a valid health permit before an address can be saved, we store the fact and the moment of that confirmation. We do not store licence documents, permit numbers, or scans, and we never ask for them.

Payments: the Stripe connected account identifier and whether charges are enabled on it. Never bank details, never card data.

Devices: the name of each paired Orders-screen device, its pairing state, and any push token it registers.

Orders: the full order history described in the section above, with its event log.

4. What we store about a delivery driver

A business creates its own driver accounts; there is no driver self-signup. For each driver we store a name, email address, phone number, a salted password hash, whether they are currently on shift, and any push token their app registers.

Consent records: where a state requires a written notice or an acknowledgment before a driver works, we store that the driver acknowledged it and when. That includes the location-tracking notice and, where a state requires it, a food-safety acknowledgment.

Location: the driver app sends location only while a delivery is actually out, never before it and never after it, and never in the background. At most one point every ten seconds is stored. The current point is visible to the business whose delivery it is; it is never visible to the customer and never public. The last point recorded is retained on the completed delivery record, so a business can see where a delivery finished. Nothing else about the route is kept.

5. What our infrastructure records automatically

Like any web service, our infrastructure processes IP addresses and basic request metadata (URLs, timestamps, user agent) to serve requests, enforce rate limits, prevent abuse, and debug problems. These server logs are operational, not marketing data. We run no analytics scripts, no advertising pixels, and no third-party trackers on the ordering pages, the admin portal, the demo, or the marketing site.

6. The waitlist

If you leave your email address on the waitlist page, we store that address, the time you submitted it, and the page on our site whose button sent you there. We use it for one thing: telling you when signups open. We send that one email, and then we delete the address. The form sets no cookie. Your IP address is processed to rate limit the form and is not stored with your address. To be removed before then, email support@delitero.com.

7. How we use it

Everything above is used to run the ordering service. Concretely: showing a business's menu and taking orders; passing each order to the Orders screen and, for a delivery, to the driver carrying it; processing payment through Stripe and recording the result; calculating the sales tax that applies at the address the order goes to; sending transactional email (order receipts to customers who gave an email address, and account email to business users such as verification, password reset, and team invites); sending the order text a customer consented to; alerting a business when a paid order sits unaccepted, first on the Orders screen, then by text, then by a voice call to the number the business configured; carrying order chat between the parties to an order; showing a business its own order history and sales figures; and securing the service through rate limiting, abuse prevention, and debugging.

We send no marketing email. There is no newsletter, and a customer email address is never used for promotion.

We do not use personal data for advertising, for profiling, or to train models, and we do not combine data across businesses.

8. Payments and Stripe

Card details never touch Delitero's servers. The payment form on the ordering page is Stripe's Payment Element: the card number, expiry, and security code go from the customer's browser directly to Stripe. Each payment is a direct charge on the business's own Stripe account.

After payment, Stripe tells us the outcome and the card's brand and last four digits, which we store so the business and the customer can recognize the payment on receipts and order screens.

Stripe processes payment data under its own terms and privacy policy (stripe.com/privacy). Refunds are issued by the business and processed by Stripe back to the original payment method.

9. Cookies and device storage

We use almost none, and none for tracking.

Admin portal: one session cookie that keeps you signed in. It is httpOnly (not readable by page scripts) and expires after 7 days. Signing out or changing your password invalidates sessions. A second, non-secret cookie remembers which of your locations you last had open.

Ordering pages and widget: no cookies. After you place an order, your browser's sessionStorage holds a summary of it so your confirmation and status page can show your items on the same device. It never leaves your browser and is cleared when the tab session ends. The order status link itself contains a long unguessable order ID; treat the link like a receipt and do not share it if you do not want someone to see the order.

Marketing site: no cookies, no analytics, no trackers.

Because there are no advertising or analytics cookies anywhere, there is no cookie banner and nothing to opt out of.

10. Your customers stay your customers

If you run a business on Delitero, the people who order from you are your customers. Their names, contact details, addresses, and order history belong to your business. Our role is to process that data to run your ordering.

We never sell it, never rent it, never use it to market anything to them, and never share it with another business on Delitero. We do not operate a consumer app, a marketplace, or a directory, so there is nowhere for us to send your customers even if we wanted to. If you leave Delitero, your customer data leaves with you, and your customers' relationship with you is unaffected.

11. Service providers

We use outside providers only where a function genuinely requires one, and each processes data only to provide that function to us. This is the complete current list, named by what it does:

Cloudflare: hosting and compute, the databases, and file storage for menu and chat images, plus delivery of the transactional email we send. Serving is US-based for this US-only product, and storage is encrypted at rest. It processes the service data described above.

Stripe: payments, on each business's own Stripe account. It processes the card and payment data described in the payments section.

Twilio: the text messages and voice calls the service places, which are the order-escalation alerts to a business and the consented order text to a customer. It processes the destination phone number and the message content.

Google Firebase: push notifications to the Delitero apps on Android devices. It processes the device push token and the notification content.

Apple: push notifications to the Delitero apps on iPhone and iPad. It processes the device push token and the notification content.

When we add a provider, we update this list before it starts processing anything.

12. When we share information

We do not sell personal data. We do not share it with advertisers, data brokers, or "partners". Data leaves Delitero only in these cases: to the providers listed above, to run the service; between the parties to an order (the business sees the customer's order details, and the driver assigned to a delivery sees the delivery name, phone, address, and items, never prices or payment details); if the law requires it (we comply with valid legal process, and where lawful and practical we will tell the affected business); and if the business changes hands (if Delitero is acquired or merges, data transfers to the successor bound by this policy's commitments, and businesses will be notified).

13. How long we keep things

Some of this the system enforces by itself. The rest is stated plainly as what we do, without pretending a timer exists where none does.

Enforced automatically: a checkout that is never paid is cancelled 2 hours after it was started. A completed order leaves the live order system 24 hours after it is written to the order history. An order chat is archived 4 hours after it is resolved, resolves itself after 24 hours with no messages, and is archived no later than 7 days after it opened; archived threads are no longer readable in the product. A copy of a chat thread preserved because someone reported it is kept for 90 days and then deleted.

Kept until you ask us to remove it: order history and its event log, so a business has a permanent sales record; business account, menu, team, and device data, for as long as the account is open; the last recorded point of a completed delivery, on that delivery's record.

Operational server logs are short-lived and used only as described above.

There is no self-serve account deletion yet, and we would rather write that here than imply a button that does not exist. If you want your account and its data deleted, or if you are a customer who wants your order data deleted, email support@delitero.com. We will honor the request, except where the business needs the record for tax, accounting, or legal reasons. For a customer request about a specific order we will pass it to the business you bought from, since that is the business holding the relationship.

14. Security

All traffic is encrypted in transit (TLS). Data is encrypted at rest by our infrastructure provider. Passwords are stored as salted hashes, never in plain text. Admin sessions use httpOnly cookies; API access is role-gated per team member, and role changes and removals take effect immediately. Changing or resetting a password revokes all other sessions for the account. Paired Orders-screen devices authenticate with their own revocable tokens, so no owner credentials sit on a counter. Card data never reaches our systems.

No system is perfectly secure. If we learn of a breach affecting your data, we will notify you and the authorities as required by law.

15. Your choices and rights

A business can view and correct its account data in the admin portal at any time. Customers can contact the business they ordered from, or us, about their order data.

Depending on where you live, state privacy laws (such as the California Consumer Privacy Act) may give you rights to access, correct, delete, or port personal data, and to opt out of its sale or sharing. We do not sell or share personal data in the sense those laws regulate, and we will honor access, correction, and deletion requests as described above regardless of whether a statute currently obliges us to.

To exercise any of this, email support@delitero.com. We verify a request by email confirmation only; we never ask you for identity documents. We will respond within 45 days.

16. Children

The service is not directed at children. You must be 18 or older to open a business account. Ordering pages are general-audience commerce pages, and we do not knowingly collect personal information from children under 13. If you believe a child under 13 has submitted personal information to us, email support@delitero.com and we will delete it.

17. United States only

Delitero serves businesses in the United States, and the service is hosted and operated for the US. Do not use the service from jurisdictions where its data practices would not be lawful.

18. Changes and contact

When this policy changes we will post the updated version with a new effective date. For material changes we will email business account owners before the change takes effect. Keeping your account after the effective date means the updated policy applies.

Privacy questions and requests: support@delitero.com.

Delitero, Inc., a Delaware corporation. Registered agent: Legalinc Corporate Services Inc., 131 Continental Dr, Suite 305, Newark, DE 19713.