Back to home

Tablemail Privacy Policy | Restaurant Email Marketing

Learn how Tablemail handles restaurant email marketing registrations, optional pricing answers, visit measurement and your choices to access or remove data.

Last updated: 2026-10-23

Who we are and what is available

Tablemail operates at emailmarketingforrestaurants.pro. This policy covers our free early access registration, optional research questions and site administration. Contact the site operator at yzshi123@gmail.com about privacy or your registration.

The restaurant email marketing product is still being developed. This site does not currently accept your restaurant's customer spreadsheets, send your marketing campaigns, process payments or start subscriptions. Any future service will have its own updated disclosures before it collects additional information.

Information you provide

We save your email address, consent time, submission time and language when you register. Restaurant name, your role, the size of an existing permission-based mailing list, your main goal and your answer to a possible $29 monthly price are optional. The pricing answer is research, not a purchase. We do not ask for card details, customer contact lists or sensitive personal information.

A site account, if you use one, also stores its email, profile information, password hash and sign-in sessions. Registration for early access does not require an account. Only authorized administrators can access the waitlist dashboard and export registrations.

Browser storage and visit measurement

We use first-party browser storage to remember language, theme and referral information. Campaign and referring-domain cookies can last up to 30 days. Referral attribution uses the referring domain and UTM source, medium and campaign; it does not require a full referring URL. Your browser also stores campaign attribution for the current session.

Our basic visit counter creates a random browser identifier in local storage. The database saves a keyed hash of that identifier, a page-view identifier, language, source and time. Waitlist tables do not link this browser identifier to your submitted email. We skip this measurement when your browser sends Do Not Track. Clearing local storage or using another browser changes the identifier, so visitor figures are estimates. Language, theme and attribution storage may still be used when Do Not Track is enabled.

We do not enable advertising pixels. Cloudflare may automatically insert its Web Analytics performance beacon to measure page loading and basic visit information; it is separate from our first-party counter. As our hosting and database provider, Cloudflare may also process IP addresses, request details and security logs. Account sign-in uses authentication cookies; the waitlist itself does not need a sign-in cookie.

Why we process this information

We use your registration and consent to assess interest, understand restaurant priorities, arrange early access and contact you about this product or related research. We use estimated traffic and referral information to understand which outreach brings relevant visitors. Security and account records help operate the site and prevent abuse. Where applicable, we rely on your consent for registration communications and on legitimate interests in operating and securing the site, subject to local law.

We do not sell registration data or use it to send unrelated advertising. We do not verify email ownership through the registration form, so a recorded entry is not proof that the person owns that address.

Storage, recipients and retention

Production data is stored in Cloudflare D1 and processed by Cloudflare Workers. Authorized operators can read and export the waitlist for this research. Exported copies must be handled with the same access restrictions. Providers may process information outside your country; applicable safeguards depend on the provider and relevant law. We use HTTPS, restricted administrator access and hashed withdrawal credentials, but cannot promise that any service is completely secure.

We keep active registrations while evaluating and preparing Tablemail and review their continued need. If the project ends or information is no longer needed, we remove personal contact details rather than reuse them for unrelated purposes. We may retain limited records when required for security, legal obligations or respecting a previous withdrawal. Provider logs and backups follow provider retention arrangements; deletion from the live waitlist does not instantly erase every backup.

Withdraw, access or correct your information

Save the private withdrawal link displayed after registration. Anyone with that link can withdraw the entry, so keep it private. Repeating the registration does not replace the original link, and we do not automatically email a new link. Withdrawal clears the live entry's email, restaurant details, optional answers and attribution and removes it from active reports. A keyed email hash, withdrawal state and limited technical timestamps remain to prevent unverified re-enrollment.

If you lose the link, want a correction or have an access, deletion or objection request, email yzshi123@gmail.com from the address concerned. We may request reasonable evidence of ownership before acting. Rights, response periods and complaint options depend on your jurisdiction; where available, you may contact your local data protection authority. You can also clear site storage or enable Do Not Track to limit visit measurement.

Children and policy changes

This research is intended for adults working with restaurants. Please do not submit children's information. We will update this page when our data practices change and seek additional consent when required. The date above identifies the latest revision. See our Terms of Service for the scope of the current service.