This Privacy Policy explains what information Kapakos LLC ("Field Ledger," "we," "us") collects when you use the Field Ledger service (fieldledger.app), how we use it, who we share it with, and the choices you have. It applies to all users of the Service, including organization admins, invited members, and customer-support users.
If you do not agree with this Policy, please do not use the Service.
1. Information We Collect
1.1 Information you provide
- Account information: email address, password (stored only as a salted hash — never in plain text), full name (optional), organization name.
- Profile updates: any changes you make to your name or password.
- Customer Data: properties, trips, mileage, activities, expenses, transactions, supporting documents (receipts and invoices), guest stays, personal-use day records, and any other records you enter into the Service.
- Support communications: messages you send through the in-app support form (
/app/support), including the message body, the category you select, and any attachments you include in future versions. When you submit a support message, we also snapshot your name, email, organization name, current plan, the app page you were on, and your browser's user-agent string to help us diagnose the issue.
1.2 Information collected automatically
- Operational logs: IP address, browser/user-agent string, request URI (path only — query strings are not logged), and timestamps. We use these to operate, secure, and debug the Service.
- Cookies and similar technology: see Section 5.
- Email delivery events: when we send you transactional email (verification, invites, password resets, support acknowledgements), our email provider Mailgun records delivery status (sent / delivered / bounced / complained). We use these signals to maintain reliable email delivery.
- Usage events: when you take actions in the Service (visit a page, save an entry, change a plan, submit a support message), we record an internal usage event to a private database table we control. Each event includes the action you took, an anonymous session identifier, a timestamp, and — after you log in — your user and organization identifiers (plus environment-tag metadata used only for internal debugging, such as whether the event came from the production app or a staging environment, and whether the event was fired by your browser or by our own server in response to a backend action). We use these events only to measure and improve the Service. We do not record the contents of your entries, the bodies of your support messages, or any other content you write in the Service. Usage events are processed exclusively on our own infrastructure and are not sent to any third-party analytics provider. (The only exceptions to sending content you provide to a third party are the two optional AI features — AI-assisted capture and AI receipt reading — see Section 1.3.)
1.3 Information collected by third parties
- Payment information: when you subscribe to a paid plan, Stripe, Inc. collects your payment-card details directly on its own infrastructure. We never see or store your full card number. We receive only the Stripe Customer ID, Subscription ID, plan code, current billing period dates, and high-level subscription status. Stripe's privacy policy applies to the data it collects: https://stripe.com/privacy.
- Files you upload as supporting documents: receipts, invoices, photos, and other files you attach to transactions are stored on Cloudflare R2 object storage on our behalf. The files are encrypted at rest by Cloudflare. We control access to your files; downloads are served via short-lived signed URLs (valid for approximately five minutes) that the Service generates on your behalf when you request a file. Cloudflare's privacy policy applies to the data stored on its infrastructure: https://www.cloudflare.com/privacypolicy/.
- Text you submit to AI-assisted capture: the Service offers an optional feature that turns plain-language notes you type into structured ledger entries. When, and only when, you use this feature (by clicking "Create Records" in the batch capture box), the text you typed is sent to our AI sub-processor, Anthropic, PBC, which processes it and returns the structured entries for you to review. We send only the text you submit to that feature — not your other ledger data, your account details, or your name. Anthropic processes the text to generate the response and, under its commercial API terms, does not use it to train its models. Anthropic's privacy policy applies to the data it processes: https://www.anthropic.com/legal/privacy.
- Receipt images you submit to AI receipt reading: the Service offers a separate optional feature that reads a receipt or invoice image you have uploaded and suggests the expense fields printed on it (vendor, date, amount, and a suggested bookkeeping category) for you to review. When, and only when, you use this feature (by choosing "Upload receipt," or "Extract details" on a file you already uploaded), the image is sent to the same AI sub-processor, Anthropic, PBC, which reads it and returns the suggested fields. We send only that image — not your other ledger data, your account details, or your name. Anthropic processes the image to generate the response and, under its commercial API terms, does not use it to train its models. The image itself remains stored as your supporting document (see the Cloudflare entry above); using this feature does not change where the file is stored. These two AI features are the only features of the Service that send content you provide to a third party; if you use neither, none of your in-app content leaves our infrastructure. Anthropic's privacy policy applies to the data it processes: https://www.anthropic.com/legal/privacy.
1.4 What we do NOT collect
- We do not use third-party advertising or analytics cookies.
- We do not track you across other websites.
- We do not sell or rent your personal information to anyone.
- We do not knowingly collect information from anyone under the age of 13.
2. How We Use Your Information
We use the information we collect to:
- Provide the Service: authenticate you, render your dashboard, generate reports, process exports, and store your records.
- Process payments: transmit billing-related identifiers and amounts to Stripe to manage your subscription.
- Send transactional email: verify new accounts, deliver invitations and password-reset links, acknowledge support messages, and send billing-related notifications. We use Mailgun to deliver these emails.
- Provide customer support: route your messages to our support team along with the diagnostic snapshot described in Section 1.1, so we can respond accurately.
- Operate and improve the Service: monitor performance, debug issues, and protect against fraud, abuse, or security threats.
- Structure notes you submit to AI-assisted capture: when you use the "Create Records" feature, we send the text you typed to Anthropic to convert it into structured ledger entries you then review (see Sections 1.3 and 3).
- Read receipt images you submit to AI receipt reading: when you use the "Upload receipt" / "Extract details" feature, we send the receipt image to Anthropic to suggest the expense fields printed on it, which you then review (see Sections 1.3 and 3).
- Comply with law: respond to lawful requests from authorities, enforce our Terms, and protect our rights or the safety of users.
We do not use Customer Data to train machine-learning models or to build user-level profiles for marketing purposes. Our AI sub-processor (Anthropic) likewise does not use the text or receipt images you submit to these AI features to train its models, under its commercial API terms.
3. Sub-processors and Third Parties
We use the following sub-processors to operate the Service. Each is bound by data-processing agreements and security obligations consistent with its public privacy policy.
| Sub-processor | Purpose | Data shared | Privacy policy |
|---|---|---|---|
| Stripe, Inc. | Payment processing and subscription management | Customer name, email, billing address, full payment-card details (collected directly by Stripe), transaction amounts and history | https://stripe.com/privacy |
| Mailgun (Sinch) | Transactional email delivery | Recipient email, sender, subject, plain-text and HTML bodies, delivery events | https://www.mailgun.com/privacy-policy/ |
| Render Services, Inc. | Web application and database hosting | All Customer Data and account data stored by the Service, encrypted at rest and in transit | https://render.com/privacy |
| Cloudflare, Inc. | Object storage for files you upload as supporting documents (receipts, invoices, photos attached to transactions) | The file contents you upload, the filename you provide, and the MIME type. Files are stored encrypted at rest and are not publicly addressable. We grant time-limited signed download links (approximately five minutes) only to you. | https://www.cloudflare.com/privacypolicy/ |
| Anthropic, PBC | AI-assisted capture (structuring plain-language notes into ledger entries) and AI receipt reading (suggesting the expense fields printed on a receipt image) | For AI-assisted capture: only the text you submit to "Create Records." For AI receipt reading: only the receipt image you submit to "Upload receipt" / "Extract details." Used solely to generate the suggested response; not used to train Anthropic's models (per its commercial API terms). Not shared for any other feature; no other ledger data, account details, or name is sent. | https://www.anthropic.com/legal/privacy |
| Datadog, Inc. | Operational log aggregation, application-performance monitoring (APM), and infrastructure metrics for the Service | Structured application log entries (event names, HTTP status, request path, server timestamps, operational counters); APM request traces (endpoint/resource name, response latency, database-query shapes, and HTTP status codes — never request or response bodies); and custom operational metrics (request/error counters and latency gauges, tagged only with low-cardinality values such as subscription plan tier and environment — never a user ID, organization ID, email address, property name, or dollar amount). Does not include the contents of your ledger entries, supporting documents, support messages, or any free-text you write in the Service. Failure-pattern log events may include the domain portion of an email address (e.g. gmail.com) — never the full address. |
https://www.datadoghq.com/legal/privacy/ |
| Plausible Insights OÜ | Marketing-site analytics (visits to getfieldledger.com only — NOT the Service) | Page path visited, referring URL, browser type, screen size, and country derived from your IP address (your IP address itself is not stored). No cookies are set. No personal identifier is shared. | https://plausible.io/privacy |
| Twilio Inc. | Operational SMS alerts to the Service operator's internal phone when a critical server error is detected. No Customer Data is transmitted. | The Service operator's own phone number, plus the affected internal route (e.g. /api/billing), an event identifier, an HTTP status code, and the time. Customer phone numbers are never used. |
https://www.twilio.com/legal/privacy |
| Formspree, Inc. | Form-submission processing for the marketing site's lead-magnet email-capture forms (currently the Schedule E template download at getfieldledger.com/airbnb-schedule-e-template/ and the guest-stay tracker download at getfieldledger.com/airbnb-guest-stay-tracker-template/ — NOT the Service) | The email address you enter in the form and your opt-in consent to marketing communications. Formspree stores the submission briefly and forwards it to Kapakos LLC's support inbox; no other data is collected. You may unsubscribe at any time. | https://formspree.io/legal/privacy-policy |
Important: Plausible and Formspree process data only for the marketing site getfieldledger.com — Plausible for visit analytics, Formspree for the lead-magnet email-capture forms (currently the Schedule E template and guest-stay tracker pages). Neither is integrated into the Service itself (fieldledger.app); no in-app activity or Customer Data is sent to either, nor to any other third-party analytics provider.
Each sub-processor may engage its own sub-processors under its public data-processing terms; the linked privacy policies above describe those arrangements.
We do not transfer your data to other third parties for marketing or advertising. If a sub-processor's role materially changes, we will update this list and bump the policy version.
4. How We Share Information
We share personal information only as follows:
- With sub-processors listed above, to operate the Service.
- With other users in your organization. If you are part of a multi-user organization, the org's admin and other members may see your account email, name, role, and Customer Data scoped to properties you both have access to.
- For legal compliance. We may disclose information if required by law, subpoena, court order, or to enforce our Terms or protect rights, property, or safety.
- In a business transfer. If we are involved in a merger, acquisition, or sale of assets, your information may be transferred. You will be notified before your information becomes subject to a different privacy policy.
We do not sell your personal information.
5. Cookies and Local Storage
The Service uses:
- A session cookie (
ring-session) — HTTP-only, Secure (in production), SameSite=Strict — to keep you signed in. The cookie is encrypted with a session secret known only to our servers. It is required for the Service to function. - Local storage entries — your browser stores small preferences on your device (
property-id,sidebar-collapsed?, etc.) so the Service remembers your selection across sessions. These never leave your device. - A session-storage entry (
fl-session-id) — an anonymous identifier (a random UUID) used to correlate your activity within a single browser tab for the internal usage events described in Section 1.2. It is included with each usage event we record server-side. The identifier is reset when you close the browser tab and never persists across tabs or sessions. - Stripe checkout cookies — when you start a Stripe Checkout or Billing Portal session, you are redirected to
checkout.stripe.comorbilling.stripe.com. Cookies set on those domains are controlled by Stripe (including fraud-prevention cookies) and described in Stripe's Cookie Notice: https://stripe.com/cookie-settings/legal.
We do not use any cookies for advertising, behavioral profiling, or third-party analytics. The Service does not load any third-party analytics script. (Our marketing site getfieldledger.com uses Plausible — a cookieless analytics tool — as disclosed in Section 3; the Service itself does not.) Separately, if you use the optional AI features — AI-assisted capture or AI receipt reading — the text or receipt image you submit is sent to our AI sub-processor to process it — see Sections 1.3 and 3.
You can clear cookies and local storage at any time through your browser's settings. Doing so will sign you out and reset your preferences.
6. Data Retention
- Active accounts: Customer Data is retained for as long as your account is active.
- Cancelled or trial-expired accounts: Customer Data is retained for 30 days after cancellation or trial expiry, then permanently deleted from active systems. This includes both database records (operated by Render) and uploaded files (operated by Cloudflare R2) — both are deleted as part of the same purge process. Backups maintained by our hosting providers roll forward on a schedule typically not exceeding 90 days.
- Content submitted to the AI features: for AI-assisted capture, the text you submit is processed by Anthropic to return the structured result; for AI receipt reading, the receipt image you submit is processed by Anthropic to return the suggested fields. In neither case does the submitted content become part of our systems beyond the result you review — we store only the structured entries you choose to save (as ordinary Customer Data) and, for receipt reading, the image you already uploaded remains your supporting document under the retention rules above. Anthropic's own handling and retention of API inputs is governed by its commercial API terms, under which it does not use the text or images to train its models. See Sections 1.3 and 3.
- Support messages and email-outbox records: retained for 30 days after delivery (or failure), then purged.
- Billing records: invoices and transaction records are retained for the period required by applicable tax and accounting law (typically 7 years in the United States), even after account deletion.
- Legal holds: records subject to a legal hold are retained until the hold is lifted.
7. Security
We take security seriously:
- In transit: all data is transmitted over HTTPS. The Service sends an
HTTP Strict-Transport-Securityheader in production to require encrypted connections. - At rest: customer data is stored in a PostgreSQL database operated by Render, encrypted at rest by the hosting provider. Files you upload as supporting documents are stored on Cloudflare R2, also encrypted at rest by the hosting provider, and are downloadable only via short-lived signed URLs we generate on your behalf.
- Passwords: stored only as bcrypt+sha512 salted hashes; we cannot recover your password.
- Session cookies: encrypted with a server-side secret; rotated periodically.
- Per-organization isolation: all customer queries are scoped by organization ID; cross-organization data access is blocked by middleware and is never exposed through the customer-facing API.
- Internal access: access to production systems is limited to authorized personnel and logged.
No system is perfectly secure. If you become aware of a security issue affecting the Service, please report it to security@getfieldledger.com.
8. Your Rights
You have the right to:
- Access the personal information we hold about you.
- Correct inaccurate information through your account profile or by emailing us.
- Delete your account and associated data (subject to legal retention obligations). If you are the only member of your organization, you can do this yourself using the Delete account control in the web app (under Account settings) or in the mobile app; if your organization has more than one member, email support@getfieldledger.com to request deletion and we will process it within the timeframe described below.
- Export your Customer Data using the CSV export feature in the Service, or by written request to privacy@getfieldledger.com for a one-time bulk export.
- Object to processing or withdraw consent where applicable.
To exercise any of these rights, contact privacy@getfieldledger.com. We will verify your request and respond within 45 days, as required by applicable law (typically sooner), unless we are legally required to retain the information.
8.1 California residents (CCPA / CPRA)
If you are a California resident, you have additional rights under the California Consumer Privacy Act and the California Privacy Rights Act, including:
- The right to know what personal information we collect, use, disclose, and (if applicable) sell.
- The right to delete personal information.
- The right to correct inaccurate personal information.
- The right to opt out of the "sale" or "sharing" of personal information. We do not sell or share personal information for cross-context behavioral advertising.
- The right to non-discrimination for exercising any of these rights.
To exercise these rights, contact privacy@getfieldledger.com.
8.2 Other US state laws
Depending on where you reside, you may have similar rights under Virginia, Colorado, Connecticut, Utah, or other state privacy laws. Contact us at the address above to exercise them.
9. Children's Privacy
The Service is not directed at, and not intended for use by, children under the age of 13. We do not knowingly collect personal information from anyone under 13. If you believe a child has provided us with personal information, please contact us so we can delete it.
10. International Users
The Service is offered exclusively to residents of the United States. It is operated and hosted in the United States and is not intended for users in the European Economic Area, the United Kingdom, Switzerland, or other jurisdictions outside the United States. We do not knowingly accept signups from individuals residing outside the United States. If you reside outside the United States, please do not use the Service.
By creating an account, you confirm that you reside in the United States and consent to the processing of your information by us and our sub-processors in the United States, where US law applies.
11. Changes to This Policy
We may update this Privacy Policy from time to time. The version number and effective date are shown at the top of this document. When we publish a new version, you will be required to review and accept the updated Policy the next time you log in. The current version is always available at fieldledger.app/privacy.
12. Contact
For privacy questions, data-rights requests, or anything else covered by this Policy, contact:
Field Ledger Privacy
Kapakos LLC
Email: privacy@getfieldledger.com
Address:
c/o United States Corporation Agents, Inc.
7014 13th Avenue, Suite 202
Brooklyn, NY 11228
© 2026 Kapakos LLC. All rights reserved.