Privacy policy
Version 1.1.0In effect from Oct 24, 2026
This policy explains what personal data Bitecard processes, why, for how long, who receives it, and what rights you have. Bitecard is a weekly-menu service for restaurants: a restaurant builds its weekly and standing menu and its restaurant page in an admin app, and publishes them on a public page. The service is available to businesses only and is not directed at children.
1. The controller
The controller is:
- Name: Berényi Levente egyéni vállalkozó (sole trader)
- Registered seat: 1016 Budapest, Bérc utca 12. fszt. 3., Hungary
- Sole trader registration number: 57183503
- Tax number: 58997976-2-41
- EU VAT number: HU58997976
Referred to below as "we" or the "Provider".
2. Contact
Send questions and requests about your data to:
- Email: support@bitecard.app
- Postal address: 1016 Budapest, Bérc utca 12. fszt. 3., Hungary
We do not run a telephone helpline; we answer by email.
We have not appointed a data protection officer, because our activity does not involve regular and systematic monitoring of data subjects on a large scale, and we process no special categories of data. You can write to us directly about any data protection matter at the address above.
3. What data we process
a) Account owners and staff
- email address (used to sign in);
- first and last name, phone number (the phone number is optional);
- chosen language, email notification settings;
- onboarding steps completed;
- notifications belonging to your account (for example a plan change, or a staff member joining).
b) Subscription and billing
- the billing name, address, tax number and email you enter on Stripe's checkout page, which Stripe passes to us;
- the subscription's plan, period and status;
- the version of the General Terms and Conditions you accepted and when you accepted it;
- the details of issued invoices (amount, VAT, invoice number, language).
You enter your card details only on Stripe's own page; they never reach us.
c) Restaurant data
- the restaurant's name, address, contact email and phone, website, Facebook and Instagram pages, opening hours, introduction texts;
- the uploaded logo, cover image, dish photos and gallery images;
- the menus and dishes.
This is mostly business data, but it may be personal data for a sole trader, or where a person appears in a photo. The data a restaurant enters is visible to anyone on its public menu page.
d) Invitations
- the invited staff member's email address, entered by the restaurant's owner, and who sent the invitation.
e) The try page (/try)
- the restaurant name and menu draft entered while trying the service;
- a cookie that brings you back to the draft you started;
- your IP address, for at most 25 hours, to protect against overload and abuse.
f) Visitors to the website and the public menu pages
- the hosting provider's logs: IP address, browser, page requested, and the server's error messages, in which email addresses are masked;
- on the public menu page, a keyed, irreversible hash of the IP address and the page, for at most 25 hours, to protect against overload;
- the number of menu-page views, with a random identifier, no IP address and no profile;
- error reports (browser, operating system, where the error occurred), from which names, email addresses, phone numbers, tokens, cookies and submitted form data are removed before sending. If you have consented to analytics, an error report also carries the analytics session identifier, so the error can be linked to the session recording.
g) Product analytics, only with consent
- in the admin app: a pseudonymous user identifier, language, role, restaurant and plan, the pages visited, and a recording of the session in which all text and every input field are masked;
- on the marketing pages: the pages visited. No session recording runs there.
h) Contacting us
- whatever you include in your message to us.
i) Reporting content
- if you report a public menu page (the "Report this page" link or the abuse@bitecard.app address): your name, your email address, the content of the report, our decision and the statement of reasons sent to the restaurant.
j) Business statistics
- subscriptions started, changed, cancelled and with missed payments, try-page drafts claimed and menus published, attributed to the restaurant and the plan but with a random identifier, not linked to a user, an IP address or a profile.
4. Purposes and lawful bases
| Purpose | Data | Lawful basis |
|---|---|---|
| Providing the account and the service, signing in with a one-time link sent by email | 3. a), c) | performance of a contract (GDPR Art. 6(1)(b)) |
| Inviting staff to the restaurant's account | 3. d) | the legitimate interest of the restaurant and the Provider in letting the restaurant involve its staff (Art. 6(1)(f)) |
| Displaying the public menu page | 3. c) | performance of a contract (Art. 6(1)(b)) |
| Collecting subscription fees, payment notices | 3. b) | performance of a contract (Art. 6(1)(b)) |
| Proving which version of the ÁSZF the Customer accepted and when | 3. b) | legitimate interest in proving the terms of the contract (Art. 6(1)(f)) |
| Issuing and keeping invoices | 3. b) | legal obligation (Art. 6(1)(c); Act CXXVII of 2007 on VAT and Act C of 2000 on Accounting) |
| Transactional email: sign-in link, invitation, billing and plan-change notices, warning before account deletion | 3. a), d) | performance of a contract (Art. 6(1)(b)) |
| Keeping a try-page draft | 3. e) | legitimate interest in letting the visitor continue the draft they started (Art. 6(1)(f)) |
| Security of the service, protection against overload and abuse, hosting logs, debugging | 3. e), f) | legitimate interest in running the service securely and continuously (Art. 6(1)(f)) |
| Anonymous counting of menu-page views, so the restaurant can see whether guests use it | 3. f) | legitimate interest (Art. 6(1)(f)) |
| Business statistics on how many subscriptions start, change and end, and how many menus are published | 3. j) | legitimate interest in following how the service performs as a business (Art. 6(1)(f)) |
| Product analytics and session recording | 3. g) | consent (Art. 6(1)(a)), which may be withdrawn at any time |
| Correspondence, customer support | 3. h) | performance of a contract, or legitimate interest in answering the request (Art. 6(1)(b) and (f)) |
| Handling content reports, the decision and the statement of reasons | 3. i) | legal obligation (Art. 6(1)(c); Articles 16 and 17 of Regulation (EU) 2022/2065) |
| Establishing, exercising and defending legal claims | the data needed | legitimate interest (Art. 6(1)(f)) |
Where we rely on legitimate interest, we will explain on request how we weighed your interests against ours. We do not sell personal data, and we do no tracking for advertising.
5. Who receives the data
We pass data to the providers without which Bitecard could not run. They process it on our instructions, under contract:
| Provider | Role | Data received |
|---|---|---|
| Vercel | running the application (Frankfurt, fra1), logs, storing uploaded images (Vercel Blob, Frankfurt) | all data passing through the application; logs; uploaded images |
| Prisma | running the database (Prisma Postgres, Frankfurt) | account, restaurant, menu, subscription, invoice and notification data |
| Stripe | subscription fees and card payment | billing name, address, tax number, email, card details, subscription status |
| Számlázz.hu | issuing electronic invoices and reporting them to the tax authority (NAV) | buyer name, address, tax number, email, invoice amounts |
| Resend | delivering transactional email | the recipient's email address and the message content |
| PostHog | product analytics with consent, anonymous counting of menu-page views, business statistics | the data in 3. f), g) and j) |
| Sentry | error monitoring | the cleaned error reports in 3. f) |
The Számlázz.hu service is provided by KBOSS.hu Kft., which also forwards invoices to the Hungarian National Tax and Customs Administration (NAV) as the law requires. We disclose data to an authority or court only where the law obliges us to. Data a restaurant puts on its public menu page is available to anyone.
At the Provider, only the Provider himself, Berényi Levente, has access to the data.
6. Transfers outside the European Economic Area
The application, the database, the image store, analytics and error monitoring run in the European Union (Germany). Several of our providers are US companies, however, so data may reach countries outside the EEA. Provider by provider:
- Vercel: processes logs and backups in the United States. Vercel Inc. is certified under the EU-US Data Privacy Framework, and the transfer is also covered by the Standard Contractual Clauses adopted by the European Commission (hereinafter: SCCs; Decision 2021/914, Modules 2 and 3) in Vercel's data processing agreement.
- Prisma: the database runs in Frankfurt. Prisma Data, Inc. is certified under the EU-US Data Privacy Framework. It transfers to its own sub-processors under the SCCs.
- Stripe: the contracting party is Stripe Payments Europe, Limited (Ireland). Stripe, Inc. and its affiliates also process the data in the United States, under the EU-US Data Privacy Framework, with the SCCs as a fallback.
- Resend: sends email from Ireland but processes data mainly in the United States. The transfer relies on the SCCs (Decision 2021/914, Module 2) and the EU-US Data Privacy Framework.
- PostHog: stores the data in the EU (Frankfurt). Any access by the US company PostHog Inc. relies on the SCCs (Decision 2021/914, Module 2).
- Sentry: stores the data in the EU (Germany). Any access by the US company Functional Software, Inc. relies on the EU-US Data Privacy Framework, with the SCCs as a fallback.
- Számlázz.hu: the data stays in the EU (Hungary and Frankfurt); there is no transfer outside the EEA.
7. How long we keep data
| Data | Retention |
|---|---|
| Account, restaurant and menu data | while a subscription runs. After the last subscription ends, the data stays available to download; after 30 days we send a warning email, and after 60 days, but never less than 30 days after the warning, we delete the account, the restaurants, the menus and the uploaded images. The same applies to an account that no longer has access to any restaurant (for example a removed staff member): the 30 days run from the latest of the last subscription's end, the account's creation and the last accepted invitation |
| If you delete your account | deleted immediately, together with the restaurants, menus and uploaded images, except billing data. The account cannot be deleted while an invoice is still being issued. The data disappears from backups within 7 days |
| Invoices and billing data | 8 years (Section 169 of the Accounting Act) |
| Record of accepting the ÁSZF (version, time) | as long as the subscription record is kept |
| Try-page draft that was not claimed | 30 days from the last change |
| Overload-protection entries | deleted at the next daily clean-up after their one-hour window, so at most 25 hours |
| Notifications | 90 days after being read; unread ones until the account is deleted |
| Expired or revoked invitations | 30 days |
| Accepted invitations | until the restaurant or the account is deleted |
| Analytics events and business statistics | 1 year |
| Session recordings | 30 days |
| Error reports | 30 days |
| Hosting logs | up to 30 days |
| Correspondence | until the matter is closed, then up to 5 years (the general limitation period of the Civil Code) |
| Content reports, decisions and statements of reasons | 5 years |
8. Your rights
- Access and portability: you can download your data yourself in a machine-readable format (JSON) with the "Download my data" button under Settings → Privacy: your account, restaurants, menus, image addresses, subscription, invoices and notifications. If your subscription has already ended, you can do the same from the page shown after you sign in. On request, we will also tell you what data we process about you.
- Rectification: you can correct your name, phone number and language yourself under Settings → Profile, and your billing details under Settings → Subscription; we correct anything else on request.
- Erasure: you can delete your account yourself under Settings → Danger zone. This also deletes your restaurant, menus and uploaded images, except billing data, which the law requires us to keep.
- Restriction: you can ask us only to store your data and not otherwise use it if you contest its accuracy (while we check it), if the processing is unlawful but you ask for restriction instead of erasure, if we no longer need the data but you need it for a legal claim, or if you have objected and we are still checking whether our interests prevail.
- Objection: you can object to processing based on legitimate interest; we then stop, unless compelling legitimate grounds justify continuing.
- Withdrawing consent: you can withdraw your analytics consent as easily as you gave it: when signed in, under Settings → Privacy; when signed out, with the "Cookie settings" link in the website footer. Withdrawal does not make earlier processing unlawful.
Send your request to the contact in section 2. Acting on it is free of charge, unless the request is manifestly unfounded or excessive. We answer within one month at most, and verify your identity where that is needed.
9. Complaints and remedies
If you feel we have infringed your rights, please write to us first. You may also lodge a complaint with the supervisory authority:
Nemzeti Adatvédelmi és Információszabadság Hatóság (NAIH), the Hungarian National Authority for Data Protection and Freedom of Information 1055 Budapest, Falk Miksa utca 9–11.; postal address: 1363 Budapest, Pf. 9. Email: ugyfelszolgalat@naih.hu · Phone: +36 1 391 1400 · https://www.naih.hu
You may also go to court. You may bring the action, at your choice, before the regional court for your place of residence or stay.
10. Is providing the data required
Without an email address no account can be created and you cannot sign in. Without the billing details, the tax number (where Stripe supports one for the Customer's country) and acceptance of the ÁSZF, no subscription can be concluded and the invoice the law requires cannot be issued. The phone number, photos and the restaurant's other details are optional; if you leave them out, they simply do not appear. Consent to analytics is voluntary, and refusing it has no consequence.
11. Automated decision-making
We do not carry out automated decision-making, including profiling. Content reports are also decided by a person.
12. When we process data on a restaurant's behalf
When a restaurant enters other people's data into Bitecard, for example by uploading a photo in which a person appears, or publishing a staff member's contact details, the restaurant decides the purpose of that processing. The restaurant is then the controller, and we process the data on its behalf, under the data processing agreement (https://bitecard.app/en/landing/dpa). Please send requests about such data to the restaurant first. If you send them to us, we will pass them on.
We process staff invitations and staff accounts as controller, as described in 3. a) and d) and in section 4.
We collect no data on a restaurant's behalf about its guests who view the public menu page. We process the technical data described in 3. f) as a controller in our own right.
13. Cookies
Cookies and stored items needed for the service to work (sign-in, language, selected restaurant, try-page draft, the consent answer) are set without consent. We place analytics cookies in your browser, on the website and in the admin app alike, only after you consent. The public menu pages use no analytics cookies. The full list of cookies, their purposes and lifetimes is in the cookie notice: https://bitecard.app/en/landing/cookies.
14. How we protect the data
- Data travels over encrypted (HTTPS) connections.
- The application, the database, the image store, analytics and error monitoring run in an EU region, in Germany.
- There are no passwords: sign-in is by a one-time link sent by email.
- Every read and write is limited to the restaurant's own account, and the server checks that the user has access.
- Personal data and secret identifiers are removed from error reports before sending, and email addresses are masked in the server's logs.
- All text and every input field are masked in session recordings.
- Only the Provider himself, Berényi Levente, has access to production data.
- The database is backed up daily, and backups are kept for 7 days.
If a personal data breach affects your data, and the law requires it, we notify the NAIH within 72 hours, and you too if the breach is likely to result in a high risk.
15. Changes to this policy
We may change this policy. The version number and the effective date are always shown at the top of the page, and we send earlier versions on request. We will tell you by email, before it takes effect, about any change that materially affects you.