Privacy Policy

Last updated: September 8, 2026

This policy explains what Labelara ("we", "us") collects when you use the Labelara website and application at https://labelara.com (the "Service"), why we collect it, who else processes it, how long we keep it, and what your choices are. The short version: we collect the minimum needed to run a label-making service, your recipes are confidential business information, and we never sell personal data.

1. Who we are and how to reach us

The Service is operated by Labelara. For anything in this policy — a question, a data request, a complaint — email support@labelara.com. We answer within two business days.

2. What we collect

Account data. Your email address. It is your account identifier, receives sign-in codes and service messages such as receipts, and is the only piece of profile information we hold. We do not ask for a name, a password, or a phone number.
Google sign-in data. If you choose "Continue with Google", Google sends us your email address, a flag saying the address is verified, and a numeric Google account identifier. Section 3 describes this in detail.
Your content. Recipes, ingredient lists and quantities, custom ingredient nutrition values, and label settings you choose to save. Until you sign in and save, a draft lives only in your browser's local storage and never reaches our servers.
Billing data. Payments are handled by Paddle, our merchant of record (section 6). We never see or store card numbers. We receive your subscription status, plan, and transaction identifiers so we can unlock paid features and show you what you are paying for.
Usage data. Page views and product events such as "a calculation was performed" or "a PDF was exported", with identifiers and counters only — never the contents of a recipe. Session replays in which all on-screen text and every form field are masked before leaving your browser.
Technical data. IP address, browser type, and the time and outcome of each request, in server logs we keep for security, abuse prevention and rate limiting.

3. Sign in with Google

You can sign in with a one-time code we email you, or with your Google account. When you use Google, we ask Google only for the OpenID Connect "openid" and "email" scopes. We do not request, and cannot access, your Gmail, Contacts, Calendar, Drive, Photos, YouTube, or anything else in your Google account, and we never post or act on your behalf.

What we receive from Google, and what we do with it:

Your email address and its verified status. We use the address to find your existing Labelara account or create a new one, exactly as we would after an emailed code. Only addresses Google reports as verified are accepted. The address is stored as your account email.
Your Google account identifier (the "sub" claim). We store it next to your account so that you keep reaching the same account even if you later change the email address on your Google account.
Nothing else. We do not store Google access or refresh tokens after the sign-in completes, we do not read your Google profile picture or name, and we do not share anything received from Google with advertisers or data brokers. Google sign-in data is only shared with the service providers in section 6 to the extent they host our database.

You can revoke Labelara's connection to your Google account at any time from myaccount.google.com/permissions. Revoking does not delete your Labelara account; to delete it, see section 8. Labelara's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

4. Why we use your data

To create your account, sign you in, and keep you signed in.
To calculate, render, store and let you re-download the labels you build — the Service itself.
To take payment through Paddle and unlock the features you paid for.
To send service messages: sign-in codes, receipts, and notices about changes that affect your account. We do not send marketing email.
To understand which parts of the Service are used and where people get stuck, using the aggregated usage data described above.
To keep the Service secure: detecting abuse, limiting request rates, and investigating incidents.
To meet legal obligations such as tax records.

Where the law requires a legal basis (for example in the EU or UK), we rely on performance of our contract with you for the first four purposes, our legitimate interest in running and improving a secure service for the next two, and legal obligation for the last.

5. Recipes are confidential

Your recipes are your trade secrets. We do not read them except when needed to operate the Service or when you explicitly ask for support on a specific recipe. We do not use them to train machine-learning models, build datasets, or benchmark other customers, and we exclude their contents from logs and analytics.

6. Who else processes your data

Paddle operates checkout and payments as our merchant of record and is an independent data controller of the data you provide at checkout (name, email, payment method, transaction data, and location used for tax). It processes that data under its own privacy policy. For US customers the contracting entity is Paddle.com Inc. (New York, USA); the group parent is Paddle.com Market Limited (London, UK).

Service providers that process data on our behalf and on our instructions:

Google — identity provider when you choose Google sign-in (section 3);
Resend — delivery of transactional email such as sign-in codes and receipts;
PostHog — website analytics, product usage events (identifiers and counters only) and masked session replays;
our hosting providers — servers, database and backups, located in the United States.

We may also disclose data when the law requires it, to protect the rights and safety of users or the Service, or as part of a merger or acquisition, in which case this policy continues to apply to it. We do not sell personal information and do not share it for cross-context behavioral advertising.

7. Cookies and local storage

Essential cookies. A session cookie keeps you signed in for up to 7 days, and expires after 30 minutes without activity. During sign-in, a short-lived cookie ties the emailed code or the Google round trip to the browser that started it. Both are HttpOnly and never used for tracking.
Analytics cookie. A first-party PostHog cookie tells a returning visit from a new one. We do not use advertising cookies or cross-site tracking.
Local storage. Your guest draft, label settings and unit preference are kept in your own browser so you do not lose work when you sign in or come back later. Clearing site data removes them.

8. Retention and deletion

Account data, saved recipes and the Google account identifier are kept while your account exists.
To delete your account, email support@labelara.com from the address on the account. We delete your recipes and personal data within 30 days, except records we must keep for tax and accounting purposes, which Paddle and we retain as the law requires.
Server logs are kept for 30 days. Backups are kept for 30 days.
Usage data is kept for up to 12 months in identifiable form, then only in aggregate.
Draft data in your browser's local storage stays on your device until you clear it; we cannot delete it for you.

9. Your rights

Depending on where you live — including under the CCPA/CPRA for California residents and the GDPR/UK GDPR for people in the EU and UK — you may have the right to access the personal data we hold about you, to correct it, to receive a copy in a portable format, to delete it, to object to or restrict certain processing, and to complain to a supervisory authority. Email support@labelara.com. We will verify that the request comes from the account's address and answer within the legally required time frame, normally within 30 days. We do not discriminate against anyone for exercising these rights, and we do not sell personal information, so there is nothing to opt out of.

10. Children

The Service is for businesses and adults. It is not directed to children under 16, and we do not knowingly collect their data. If you believe a child has created an account, email support@labelara.com and we will delete it.

11. Security

All traffic is encrypted in transit with TLS. Sign-in codes and session tokens are stored only as one-way hashes. Access to production systems is limited to the people who operate the Service. No system is perfectly secure; if you believe you have found a vulnerability or that your account was accessed without permission, email support@labelara.com.

12. Where your data is processed

Our servers, database and backups are hosted in the United States, and the providers in section 6 process data in the United States and in the other countries where they operate. The team that runs Labelara works from outside the United States and accesses production data from there only as described in section 11. Wherever you use the Service from, your data is transferred to and processed in those countries under this policy, and we contract with each provider on terms that require them to protect it.

13. Changes to this policy

We may update this policy as the Service changes. The date at the top shows the current version. For material changes we will post a notice on the site or email the address on your account before the change takes effect.