Fieldbook

Privacy Policy

Last updated: 1st November 2026

Fieldbook ("we", "us", "our") operates two sites:

This policy tells you which information we collect and how we use it. It also tells you your rights to this information.

Information we collect

  • Account information — your email address and authentication details. Our identity provider (Amazon Cognito) manages them.
  • Logbook content — the contacts (QSOs), logbooks, notes and files that you make or import. This includes callsigns, frequencies, timestamps and locations.
  • Optional QRZ.com credentials — if you connect your own QRZ.com account for callsign lookups, we keep the API access that we need to do these lookups for you. We encrypt your QRZ password at rest. We never keep it in plain text.
  • Optional QRZ Logbook API keys — if you connect your QRZ.com logbook through QRZ Logbook Sync, we keep its API key to upload your contacts for you. We encrypt the key at rest. We never keep it in plain text.
  • Payment information — if you subscribe to Fieldbook Pro, our payment processor, Paddle, does all the billing. We never see or keep your full card details.
  • Technical logs and usage data — basic request and error logs (through AWS), and product analytics and error tracking (through PostHog). We use this data to understand how people use Fieldbook, and to keep it operating securely.
    • When you are signed in, a unique account ID links this data to your account. We do not use personal information that identifies you, such as your email.
    • You can stop this data collection at any time in Settings.

How we use your information

  • To keep your logbooks and sync them across your devices.
  • To do lookups and attach the results to your contacts: callsign details (through QRZ.com), DXCC/CTY entities, and POTA park data.
  • To manage your subscription and billing, through Paddle.
  • To keep the service secure and to prevent misuse.

We do not sell your personal information.

Service providers

We use a small number of trusted providers to operate Fieldbook:

  • Amazon Web Services — hosting, authentication, file storage and our API, primarily in the UK (London) region.
  • PlanetScale — our Postgres database provider.
  • PostHog — product analytics and error tracking, hosted in the EU.
  • Paddle — payment processing for Pro subscriptions.
  • QRZ.com — callsign lookups. We send the callsigns of the stations that you log to QRZ.com, to get their details. We use our own QRZ.com account for this, or your account if you connect it. If you connect your QRZ.com logbook, we also send your contacts to it, except their private notes.
  • Parks on the Air (pota.app) — POTA spots. When you spot yourself, we send your callsign, park, frequency, mode and comment to pota.app. pota.app shows this spot to the public.
  • Cloudflare — DNS for our domains.

Where your data is stored

Our primary infrastructure operates in the AWS London (eu-west-2) region. Some of our service providers, such as Paddle and QRZ.com, can process data outside the UK or the European Economic Area. When you use Fieldbook, you consent to this international processing.

Data retention and deletion

We keep your information while your account is active. You can delete individual contacts or logbooks at any time in the app.

To delete your account and all the data related to it, use the option in Settings. Or, send an email to hello@jackcoble.dev.

Your rights

You have the right to access, correct, export or delete your personal information. This right applies to all users, in all countries. You can export your logbooks as ADIF at any time in the app. For all other requests, send an email to hello@jackcoble.dev.

Age requirement

Fieldbook is for persons who are 16 years old or older. We do not knowingly collect information from persons who are younger.

If we find that an account belongs to a person who is younger than 16, we will terminate the account. We will also delete all the data related to it.

If you are a parent or guardian, and you think that your child has an account, send an email to hello@jackcoble.dev. We will terminate the account and delete all the data related to it.

Security

We encrypt all traffic in transit (HTTPS). The managed authentication and access controls of our providers keep your data isolated and secure.

We encrypt third-party credentials that you give us, such as a connected QRZ.com password or QRZ Logbook API key, at rest. For this, we use AWS KMS with AES-256 encryption.

Changes to this policy

We can update this policy at any time. If we make material changes, we will change the date at the top of this page.

Contact

If you have questions about this policy, send an email to hello@jackcoble.dev.