FieldNote

FieldNote

Privacy Policy

Last updated: November 3, 2026

This policy explains how the FieldNote hackathon demo handles information when you sign in, capture work, use AI, and test PayPal Sandbox invoices.

Who operates FieldNote

FieldNote is operated by the FieldNote project owner. For privacy questions or requests about your information, contact n3rd1991@gmail.com.

The hosted application is an experimental demonstration. Please use synthetic customer details and Sandbox payment accounts when testing it.

Information we handle

  • Account information: Google account identifiers, name, email address, profile picture information, and authentication/session metadata supplied through Google sign-in and Supabase Auth. Email-link sign-in, when available, uses the email address you enter.
  • Workspace records: customer names and contact details, service descriptions and prices, job dates, field notes and saved transcripts, generated and reviewed line items, and approval states.
  • Invoice records: the Sandbox recipient, invoice contents, amounts, invoice identifiers and links, status, and related processing or webhook information.
  • Audio: recordings or files you choose, held in the browser for preview and sent for transcription when you select that feature.
  • Operational information: hosting and authentication services may process IP addresses, browser information, timestamps, request metadata, and error/security logs to run and protect the service. If you contact support, we also receive the information you send.

How information is used

Information is used to authenticate your account, keep workspace records associated with their owner, save and edit your work, transcribe audio, suggest invoice line items, create and send Sandbox invoices after your actions, update invoice status, and investigate support or security issues.

The project owner has administrative access to the demo's services for operation, support, and handling data requests. Account-based access controls restrict ordinary users to their own workspace.

Google account information

FieldNote requests basic identity permissions: OpenID, email, and profile. It does not request access to Gmail messages, Google Drive files, contacts, or calendars. Google account information is used for sign-in and account identification.

FieldNote does not sell Google account information or use it for advertising. Google profile information is not explicitly included in the app's AI prompts; those requests contain the audio or work content described below.

FieldNote's use and transfer of Google account data follows the Google API Services User Data Policy, including its Limited Use requirements.

AI processing and audio

When you choose transcription, audio is sent through Vercel AI Gateway to the configured transcription provider. When you choose AI generation, the selected field note and active price-book entries, including descriptions and prices, are sent for processing. The currently configured model provider is OpenAI. Names or other personal information you put into a recording, note, or catalog may therefore be included in that request.

FieldNote does not save the original audio file in its database or file storage. An unsaved recording's preview is temporary browser data. Saved transcripts and reviewed work remain in your workspace. Processing providers may retain request information under their own service terms and settings; this is not a promise that every provider immediately deletes audio or prompts.

Services that process information

  • Google: account authentication and the basic profile information you authorize. See Google's privacy policy.
  • Supabase: authentication, session management, and storage of account and workspace records. See Supabase's privacy information.
  • Vercel: website hosting, server-side requests, operational logs, and AI Gateway routing. See Vercel's privacy notice.
  • OpenAI: processing the audio or work content submitted to the configured models. See OpenAI's API and business privacy information.
  • PayPal: the recipient and reviewed invoice data needed to create, send, and track Sandbox invoices. Checkout and payment-account credentials are handled on PayPal's pages. FieldNote's forms do not collect payment-card numbers or PayPal passwords.

These providers operate their own services and may process information in countries other than your own. Their applicable service terms, processing arrangements, and retention settings also govern their handling of information.

Cookies and browser preferences

Supabase authentication uses cookies to maintain the session and complete sign-in. FieldNote also stores your Light, Dark, or System appearance choice in browser storage. The application code does not include advertising trackers or a third-party analytics SDK. Hosting and authentication services still process operational information as described above.

Retention and deletion requests

Workspace records do not currently expire on an automatic schedule. They remain in the project database until removed by the project owner, including in response to a verified deletion request, or the project is shut down. Provider logs and backups may persist according to the providers' retention arrangements.

You can edit customer and service information in the app. To request access, correction, an export, or deletion of your account or workspace, email n3rd1991@gmail.com from the address associated with your account. We may ask for information needed to verify ownership. There is currently no self-service account-deletion button. Requests are reviewed and handled according to applicable obligations and the service's technical capabilities.

You can also remove FieldNote's Google connection in your Google Account settings. Revoking that connection does not by itself delete records already saved in FieldNote.

Security and policy changes

The hosted service uses HTTPS and account-based database access rules. No system can guarantee complete security. Please keep your sign-in account secure and avoid adding confidential production records to this demo.

Updates to this policy will appear here with a new updated date. Changes to the use of Google account information will be disclosed before the new use, with further authorization requested where required.