Privacy Policy

Who we are

Dacia Reserve LLC is a Romanian deli and smokehouse at 422 S Dixie Hwy, Hollywood, FL 33020. This policy covers www.daciareserve.food, the Dacia Reserve app for iPhone and Android, the accounts, orders, and rewards behind them, our phone line and text messages, and what happens at our register when your account is attached to a sale.

We are the business that decides what happens to your information. Write to hello@daciareserve.food with anything about this policy.

What we collect from you

The waitlist form: your name, phone number, email address, an optional note about the deli you miss, and which consent boxes you checked.

An account: your first and last name, and your phone number, your email address, or both. One phone number belongs to one account. If you sign up with an email address and a password, our authentication provider stores the password as a hash; we never see it. Optionally the month and day of your birthday but never the year, your language, and whether you want marketing email or marketing texts. We record the moment you opt in to texts.

An order: the name, phone number, and email address for the pickup, what you ordered, the tip, and a note to the counter if you write one.

A catering inquiry: your name, email address, phone number, the date, the number of guests, the kind of event, and what you write.

An email to us: whatever you put in it.

Signing in by phone: your number. We text you a one-time code through Twilio.

At the register without an account: if you give the counter your number, Square keeps it with your purchase. If you say yes to texts, we keep the number and the time you said yes, send your sign-in link, and may send one review request. Marketing texts come after you reply YES. If you told our cashier yes to our texts before October 5, 2026, you are opted in to marketing texts too, and you can reply STOP at any time.

When we miss your call: your number, the time and any voicemail. Twilio records and transcribes it and the recording comes to our team by email so we can call you back.

When you text us: your messages and our replies, kept as a conversation our team reads.

A job application: your name, phone, email, availability, languages, experience, how you heard of the job, and our notes.

The holiday list: your name, phone and email, the holidays and dishes you want, how many will be at the table, whether you have been to our shop, when you'd pick up, where the list came from (an ad, a friend's link, our website or a printed code), and whether you want marketing email or texts. It is saved on your account, we email you a copy when you save it, and it is also a free giveaway entry. If a friend saves a list through your link, we note that it came through you. Lists saved before October 6, 2026 may also hold a ZIP code, a birthday month and how you heard about us.

A rating on our review page: the score, any note and any contact you leave. From a link we texted you, we know which visit it was. A low score goes to the owners' phones so they can make it right.

A giveaway entry: your Instagram or Facebook name and comment, or your holiday list entry.

Where you came from: if a card, text or post brought you, its tag is saved on your account.

When you sign in: we look for the record the register already has for your number, copy the name the counter typed if your account has none, and credit your earlier counter purchases.

What we collect automatically

Our host, Vercel, keeps standard server logs of requests: IP address, time, page, and browser. Supabase and Square keep their own logs of what our servers ask them.

We measure the site with Google Analytics 4 and Vercel Analytics. Vercel Analytics counts page views without a cookie or an identifier. Google Analytics sets its own cookies, described below, and we ask it to record a short list of moments and nothing personal: which pages are read, when the menu is opened, when an order is started and when it is paid, when the catering form is sent, when the address or phone number is tapped, when an account is created, when a holiday list is saved or changed, and the steps of our review page. We deny it the advertising permissions, we never send it your name, email, phone number, or order note, and in the European Economic Area, the United Kingdom, and Switzerland, and whenever your browser sends a Global Privacy Control signal, it runs without cookies and without any identifier, so it cannot tell one visit from another.

We run the Meta Pixel and its Conversions API on the website. Meta receives page views and these events: the menu opened, a dish added to the cart, an order started, an order paid (the total and the order code), a catering request sent, the address or phone tapped, an account created, and a first holiday list saved (which holidays it is for). When you are signed in, the Pixel also gives Meta your email, your phone and our internal id for your account, each turned into a hash in your browser. When you add to the cart, start an order, pay, or save your first holiday list, our server also sends Meta its own copy of that event, with the Meta cookies described below, your IP address, your browser type and, when you are signed in, the same hashes; for a paid order it carries hashes of the email and phone given for the order, and for a holiday list those given on the list. Meta never receives your name, your note to the counter or your card. Orders placed in the app or at the register are never sent to Meta. Staff accounts are left out. It never runs in the European Economic Area, the United Kingdom, or Switzerland, for a browser sending a Global Privacy Control signal, or once you have used the Do Not Sell or Share link in the footer. You can also manage this in your Facebook or Instagram ad settings and at optout.aboutads.info.

When something breaks, the page reports the error to Sentry so we can fix it: the error itself, the page, the browser, and a scrubbed technical trace. Before it leaves your browser we strip emails, phone numbers, card tokens, and anything that looks like a secret. Sentry also keeps a Session Replay for one visit in ten and for every visit where an error happens: a recording of how the page moved, with every piece of text and every input masked and all images and video blocked, so it shows clicks and layout, not what you typed or read. The card fields are Square's own and are never in it.

The app reports crashes and errors to Sentry so we can fix them: the error, the screen it happened on, the app version, the phone model and system version, and a technical trace. No account, name, email address, or phone number is attached, and web addresses lose their query string before they leave the phone.

If you allow notifications, the app sends us a push token, the address Apple or Google gives your phone for notifications, together with the platform and the device name the phone reports. We store it against your account to tell you about your orders and, for a staff account, to announce new orders, texts, and missed calls at the shop. Offers are sent only if you turn on the Offers switch, which starts off, and never more than one a week. Signing out removes the token.

The camera is used only in staff mode, to read a member's code at the counter. Nothing it sees is saved.

Card payments in the app, Apple Pay included, go through Square's In-App Payments SDK. Square collects what it needs to process and protect the payment, such as a device identifier, the payment details, how the payment screen was used, and crash data, under Square's own privacy notice. The full card number never reaches us.

The app carries no advertising or analytics library of its own; the payment and sign-in kits report their own usage to Square and Google. It does not track you across other companies' apps or websites.

Signing in with Google or Apple

Continue with Google: Google tells us your name and your email address and gives us an identifier for your Google account. That is all we ask for. We do not request your contacts, calendar, or photos, and we never display or use your Google profile picture.

Sign in with Apple: Apple gives us an identifier, an email address, and your name the first time. If you choose Hide My Email, the address is Apple's private relay address, and that relay address is the only one we ever see. Mail we send there is forwarded by Apple to your real inbox, which stays hidden from us.

Apple's servers also send ours notices about your Apple account, and we act on four of them. If you revoke Sign in with Apple for Dacia Reserve, we end your sessions. If you delete your Apple account, we delete your Dacia Reserve account. If Apple stops forwarding relay mail, we switch off marketing email so we stop writing into a dead address. If forwarding starts again, we note it. Each of those is written to our internal log.

We never receive your Google or Apple password.

What we get from Square

When you pay, Square confirms the payment and gives us its order and payment identifiers, the amounts, the tax, the tip, and later any refund. At the counter our staff can see the card brand and last four digits for an order; we never receive the full card number, the expiry, or the security code, and we never store them.

When you buy in store with your number attached at the register, Square tells us about the sale, including what was on the ticket, so the ledger can mark your points and any reward you used.

Why we use it

To take your order, fill it, and tell you when it is ready.

To run your account: sign you in, show your order history, keep your ledger.

To answer you when you write to us.

To send marketing, only if you asked for it.

To run the business: accounting, tax, fraud prevention, and understanding how a week went.

To meet obligations the law puts on us.

Payments

Square is our payment processor. The card fields on our checkout page are Square's own, hosted by Square inside our page, so your card details travel to Square and never touch our servers or our database. Apple Pay, Google Pay, and Cash App Pay work the same way. Square is PCI DSS compliant, and we are the merchant level for a business that never handles card data.

Square uses what it collects under its own privacy notice, as our processor and as a payment company in its own right.

Square's payment form also loads Square's own scripts on the checkout page and reports to Square's own error and usage services. That is Square's code doing Square's monitoring, not ours.

Your Square customer profile

If you have an account, we create a customer profile for you inside Square holding your name, your email address, your phone number, and a reference to your account. It exists so the register can find you: the counter looks you up by phone number, attaches the sale, and your points are marked.

That profile lives with Square, not only with us. When you delete your Dacia Reserve account we delete our side of it, but the profile held by Square is not removed automatically. Write to hello@daciareserve.food and we will remove it.

The Reserve Ledger

For members we keep a running ledger: every credit and debit, the reason for it (an online order, an in store sale, the founding bonus, a refund, a correction by our staff), the order it came from, and the rewards you have claimed. Points belong to the account and go when the account goes.

Guest orders

You can order without an account. The name, phone number, and email address given for that pickup are kept with the order.

If you later create an account and confirm the same email address, those earlier orders attach themselves to your account and their points join your ledger.

The tracking link in your order email is signed. Anyone holding the link can see that order's status and its items, so treat it like a receipt. We store only a fingerprint of the link and never the link itself, and the link does not expire.

Email and text messages

Order email comes from orders@daciareserve.food. Account email, such as confirming your address or resetting your password, comes from no-reply@daciareserve.food. Both are delivered by Resend on our behalf. These are service messages: while you have an account or an open order, they are how the service works.

Texts come from our shop number and are delivered by Twilio. We send three kinds. Account texts you asked for: your sign-in link and codes, word that an order was received and is ready, our replies when you text us, and one text back when we miss your call. One request to review a visit, sent a couple of hours after you buy, once per number. And marketing texts, only if you opted in: by ticking the SMS box or by replying YES to our text. If you told our cashier yes to our texts before October 5, 2026, you are opted in to marketing texts too, and you can reply STOP at any time.

Marketing email and marketing texts are separate, optional, and each has its own consent. Message frequency varies, up to 4 messages a month, and message and data rates may apply. Unsubscribe in any email, reply STOP to any text, reply HELP for help, or write to hello@daciareserve.food. Consent is not a condition of purchase.

Text messaging originator opt-in data and consent are never shared with any third party. Mobile information is shared only with the providers that deliver our messages.

Cookies and your device

We set five cookies of our own. sb-dacia-auth-token holds your signed-in session and is set by our authentication provider; it may be split across a few cookies whose names start the same way. dacia-lang remembers the language you picked and lasts a year. dacia-src remembers, for seven days, which card, text or post brought you to the site, and is saved on your account as where you came from if you create one. dacia-consent carries, for thirty minutes, the choices you made on the founding page about texts and email while you sign in with your phone, Google or Apple, and is deleted once they are saved to your account. dacia-setup remembers for a year that you closed the setup card on your account page. We also keep a few small flags in your browser's storage, such as whether you used the Do Not Sell or Share link and whether a sign-up or a purchase was already counted; they never leave your device.

Google Analytics sets two more, _ga and one whose name starts with _ga_, which tell Google a returning browser from a new one for up to two years. They are analytics cookies, not advertising cookies, and nothing here follows you to other sites. We show no cookie banner: in the United States none is required for these, and where consent is required first they are not set at all.

The Meta Pixel, when it runs, uses two cookies of its own: _fbp, and _fbc, which is set only when you arrive by tapping a Meta ad and remembers that tap. Both last up to 90 days and are advertising cookies rather than analytics ones. A Global Privacy Control signal keeps the Pixel from ever loading, and so does the Do Not Sell or Share link in the footer. You can also manage this in your Facebook or Instagram ad settings and at optout.aboutads.info.

Your cart lives in your browser's local storage under dacia.web.cart.v1 and stays on your device until you check out. In the app, your cart, the name and phone you use for pickup, your last twelve orders, and your session are stored on your phone by the app itself.

Square's payment form may set its own cookies and storage on the checkout page, under Square's notice.

Who we share it with

We do not sell your personal information and never have. Apart from the Meta Pixel described above, we do not share it for anyone else's advertising.

We use these providers, each only for what is listed. Supabase: the database and sign-in that hold your account. Vercel: hosting and server logs. Square: payments, the catalog, the register, and your customer profile. Cash App: if you pay with Cash App Pay. Resend: sending our email. Twilio: our texts, the one-time sign-in codes, and the shop's phone line, including voicemail and its transcript. Apple: only if you sign in with it. Google: sign-in if you use it, the Google Analytics measurement described above, the map on the visit page, which loads from Google only when you tap it, and the Google Sheet that receives sign-ups from our SMS sign-up page. Sentry: error reports and the masked replays described above, and the app's crash reports. Expo: delivering the app's push notifications through Apple's and Google's push services, and checking for app updates. OpenRouter, and the company whose model it uses for a draft, such as Anthropic, Google or DeepSeek: the internal drafting assistants described below. We tell OpenRouter to use only model companies that do not train their models on what we send. Some of them keep it for a short time, for example 30 days at Anthropic, before deleting it. Instagram and Facebook: giveaway entries made there. Meta: the Pixel and its Conversions API described above.

We also share when the law requires it, when we have to protect someone's safety or our rights, and if the business is ever sold or merged, in which case your information moves with it and this policy follows until it is replaced.

Google Analytics data goes to Google for measurement only; we deny it the advertising permissions, so it is not used to build an advertising profile of you. When the Meta Pixel runs, some browsing data reaches Meta for advertising, which California law calls "sharing"; the Do Not Sell or Share link in the footer stops it.

Drafting assistants in our staff portal

Our staff portal has internal assistants that draft copy, and they send text to a language model through OpenRouter.

What they are given is business data: the menu, prices, hours, the weekend specials, our brand rules, and counts and totals that contain no individual records.

Two exceptions, said plainly. When our team drafts a reply to a catering inquiry, the model is given the inquiry's first name, the date, the guest count, the event type, and the message you wrote, word for word. Your email address and phone number are never included. And when we draft a reply to a public review, the review's text is pasted in.

We never send account lists, email addresses, phone numbers, order histories, or point balances to a model, and a person reads and edits every draft before anything is sent.

How long we keep it

Orders and the ledger we keep. They are our books, and tax and accounting rules expect us to hold them.

Raw notifications from Square, about payments and about customer records, are deleted after thirty days.

Raw model text from the drafting assistants is cleared after thirty days.

Our internal audit log records who did what in the staff portal. It is append only and it survives an account deletion.

Waitlist and catering records stay until you ask us to remove them.

We keep the record of who agreed to texts and who said STOP, including the yes given at the counter, for five years after the last text we send that number. It is our proof of consent. Our note that we already asked a number for a review is kept the same way, so nobody is asked twice. If you delete your account, the yes on it goes with it, and we keep only your number, on the list of numbers we must not text.

The text inbox and the texts we send are kept for two years.

Missed calls, voicemails and their transcripts are kept for twelve months.

Job applications are kept for twelve months after the hiring decision.

The holiday list is kept until January 31 after the season it was for.

Notes and scores from our review page are kept for two years.

The browser details kept for Meta on a website order (the Meta cookies, the IP address and the browser type) are cleared after 72 hours.

An unfinished holiday list, one you started and pressed the button to get a code for, or opened in another browser, is kept for thirty days so you can finish it, and we may send one reminder to the email you gave. Then it is deleted.

Deleting your account

You can delete your account yourself: on the site under Account, then Security, and in the app under the Account tab. It happens right away and cannot be undone.

What goes: your sign-in, your profile with its name, phone, birthday, language, and consents, your points ledger, and your reward claims. Deleting also stops every text and marketing email from us: your phone number goes on our list of numbers we do not text, and your email address is unsubscribed from our newsletter.

What stays: your past orders, kept as our books with the name, phone, and email that were on them, no longer linked to an account, and the audit entries that record what happened.

What we remove by hand when you ask: the customer profile Square holds for the register. Write to hello@daciareserve.food.

Security

Traffic runs over HTTPS. Passwords are hashed by our authentication provider and we never see them. Rows in our database are protected one account at a time, so an account can read only its own, and the staff portal is limited to the roles that need it. Card data never enters our systems. Order tracking links are signed and stored only as a fingerprint. Square's notifications are signature checked before we act on them.

No system is perfect. If something goes wrong we will tell the people affected, and the authorities where the law asks us to.

Your choices and rights

See or correct what we hold: sign in and open Account, or write to us.

Turn marketing on or off: Account, then Preferences, the unsubscribe link in any email, or STOP to any text.

Ask for a copy of your information, or ask us to delete it: hello@daciareserve.food. We answer within thirty days, we do not charge for it, and we may need to confirm who you are first.

We do not treat anyone differently for exercising any of this.

California residents

If you live in California, you have the right to know what we collect and why, to get a copy, to correct it, to delete it, to limit the use of sensitive personal information, which we do not collect, and not to be discriminated against for asking.

We do not sell personal information. Google Analytics data goes to Google for measurement only, with the advertising permissions denied, which we do not believe is selling or sharing as California law uses those words. Sharing browsing data with Meta for advertising, through the Meta Pixel, does count as "sharing" under California law, and the Do Not Sell or Share link in the footer stops it, honored also through a Global Privacy Control signal from your browser. Write to hello@daciareserve.food and say what you want. You may use an authorized agent.

Romania, the EU, and the UK

Our site is in Romanian too, and people read it from Romania. If you are in the EU or the UK, you have the rights the GDPR gives you: access, correction, deletion, restriction, portability, objection, and a complaint to your data protection authority.

Our lawful bases are the contract between us when we take your order and run your account, your consent for marketing, and our legitimate interest in running and securing a small business. Your information is stored in the United States. You can withdraw consent at any time, and doing so does not undo what came before.

Children

Dacia Reserve is not directed at children. We do not knowingly collect information from anyone under 13, and accounts are for 18 and over. If you believe a child has given us information, write to hello@daciareserve.food and we will delete it.

Changes to this policy

When this policy changes, the date at the top changes with it. When a change matters, we will say so on the site and, for account holders, by email.

If the English and Romanian versions differ, the English one governs.

Contact

Dacia Reserve LLC · 422 S Dixie Hwy, Hollywood, FL 33020 · hello@daciareserve.food. Write in English or Romanian.