BaserowPDF is a small tool, run by EBLYN, that turns a Baserow row into a branded PDF. This page explains what we collect, why, and what we deliberately never touch.

What we collect

• Account. Email address, and — if you sign in with Google — your name and profile photo, all provided to us by Firebase Authentication after you sign in. We never see or store a password.
• Your Baserow connection. The API base URL, table id and table name you connect, and your Baserow API token. The token is encrypted at rest with libsodium before it touches our database and is never sent back to your browser once saved.
• Your template. Brand name, accent color, footer text, which fields to show and in what order, and an uploaded logo file, if you add one.
• Usage records. That a PDF was generated, when, how long it took, and whether it succeeded — not the document itself and not the row data inside it.
• Basic analytics. Google Analytics (GA4) records page views and general usage in aggregate, the same as most websites.
• Anything you send us directly. A bug report or a newsletter sign-up (both optional, both in the site footer) is stored with your email in EBLYN's shared internal system, used only to answer you or send occasional product updates.

What we read from Baserow, and what we don't keep

To build a preview or a PDF, BaserowPDF fetches the relevant rows and field definitions from your table live, at the moment you ask for it, using your read-only token. That data is used to render the document and then discarded — it is not written to our database.

Generated PDFs are never stored. Every file streams straight to your browser over the same request that created it. We keep the fact that a generation happened, not the file.

How we use it

To run the service you're using: authenticate you, connect to your table, render your template, and enforce the published fair-use limits (120 PDFs/hour, 50 rows/batch) so the free service stays usable for everyone. Aggregate analytics inform what we build next. We do not sell your data, and we do not use your Baserow row data for anything other than rendering the document you asked for.

Who else sees it

• Firebase (Google) — authentication only. See Google's privacy policy.
• Google Analytics (GA4) — aggregate usage analytics.
• Baserow — we call the Baserow API on your behalf, using the token you provided, to your own account. Baserow's handling of your data is governed by Baserow's own privacy policy.
• EBLYN's internal tools — bug reports and newsletter sign-ups only, kept within the same company that runs BaserowPDF, never sold or shared onward.
• OVH — our hosting provider, storing the encrypted database and application files.

Cookies & local storage

One session cookie keeps you signed in — strictly functional, not used for tracking. A small theme value in your browser's local storage remembers your light/dark preference. Google Analytics may set its own cookies, subject to your browser's settings.

Retention & deletion

Delete your account from the Account page and your connection, template, logo and generation history are removed immediately and permanently, by cascade — there's no 30-day grace period holding onto it. Deleting your BaserowPDF account does not delete your Firebase or Baserow accounts, which are separate.

Security

Your Baserow token is encrypted at rest with sodium_crypto_secretbox, never logged, and never echoed back to the browser after you paste it. All traffic between you, BaserowPDF and Baserow runs over HTTPS/TLS.

Your rights

You can review your connection and template settings at any time in the app, and delete everything from the Account page. For anything else — a data export request, a question about this policy — email us.

Children

BaserowPDF is not directed at children under 16, and we do not knowingly collect data from them.

Changes

If this policy changes in a way that matters, we'll update the date above and, where reasonable, tell existing users directly.

Contact

Questions about this policy or your data: contact@baserowpdf.com.