Privacy Policy · Effective May 2026

Privacy Policy

This policy describes what IssueLedger collects, why, and what it does with it. Questions: legal@issueledger.com.

1. What We Collect

Account information

When you sign in, we collect your email address. We use magic-link authentication — no password is stored. We retain your email address for the life of your account and use it only to send authentication links and material service notices.

Property and issue data

Everything you enter into IssueLedger — property names, unit labels, issue descriptions, event notes, vendor information, access preferences — is stored and associated with your account. You own this data. We do not sell it, use it for advertising, or use it for any purpose other than operating, securing, supporting, and improving the service as described in this policy.

Tenant submissions

When a landlord shares a submission link, a tenant may submit an issue without creating an account. That submission — description, photos, timestamp, access preference — is stored in the unit record owned by the landlord account. Tenants have no account with us; their data is held under the landlord's account. Landlords bear responsibility for informing tenants that submissions are recorded.

Files and photos

Uploaded files are stored in AWS S3. Each file is hashed on receipt (SHA-256). We do not process, analyze, or access file contents beyond what is necessary to store, display, export, secure, debug, or support the service.

Log and usage data

We collect standard server logs: IP address, browser type, pages accessed, timestamps. This data is retained for up to 90 days and used only for security, debugging, and uptime monitoring. We do not run behavioral analytics.

2. How We Use It

We use collected data to: authenticate users; store, retrieve, and export your records; send authentication emails; send service notifications from notifications@issueledger.app; monitor service health; and respond to support requests. We do not sell data, use it for advertising, train AI models on it, or share it with third parties except as described below.

3. Third-Party Services

Operating the service requires the following subprocessors. Each processes data only as necessary to provide their function:

  • Supabase — database and authentication. Data stored in the United States.
  • Amazon Web Services (S3) — file storage with Object Lock. Data stored in the United States.
  • Netlify — web hosting and CDN. Logs processed in accordance with Netlify's privacy policy.
  • Resend — transactional email delivery for tenant-submission notifications and service messages.
  • Stripe — subscription checkout, billing, invoices, and payment processing. Payment card details are handled by Stripe, not stored by IssueLedger.
  • Sentry — error monitoring and performance diagnostics, configured to help us diagnose failures without using the service for behavioral advertising.

We do not use advertising networks, tracking pixels, or behavioral analytics services.

4. Cookies and Sessions

We set one first-party session cookie to maintain your authenticated session. We do not use tracking cookies, third-party cookies, or persistent identifiers beyond what is required for authentication.

5. Data Retention

IssueLedger is designed to retain issue records for documentation purposes, but it is not your only archive. You should keep independent copies of original photos, videos, texts, emails, notices, invoices, and exported PDFs outside IssueLedger.

Account data, issue records, audit records, and uploaded files are retained or deleted according to our operational retention rules, legal obligations, payment status, storage controls, and account status. Files in S3 may be subject to Object Lock retention and may not be deletable before the applicable retention period expires, even after account closure. After account closure, retained files may no longer be accessible through the service.

Server logs are retained for up to 90 days. We respond to verified deletion and access requests within 30 days, but deletion may be limited by legal obligations, security needs, billing records, fraud prevention, audit records, backup timing, or storage retention controls.

6. Security

Files are stored with controls such as SHA-256 hashing, private S3 storage, and S3 Object Lock where applicable. Access to production systems is restricted and logged. We use industry-standard encryption in transit (TLS) and at rest. These controls reduce risk but do not guarantee uninterrupted access, perfect security, successful export, or preservation of every record forever. No security measure is perfect; we will notify you of a reportable breach affecting your data as required by applicable law.

7. Your Rights

You may request a copy of your data, correction of inaccurate data, or deletion of your account by emailing legal@issueledger.com. We will respond within 30 days. Tenant submitters may request deletion of their submission by contacting the landlord account holder directly; we will honor deletion requests forwarded to us by the account holder where deletion is legally and technically available.

8. Children

IssueLedger is not directed at and does not knowingly collect information from anyone under 18. If we become aware of such collection we will delete the data promptly.

9. Changes

We will post changes to this policy at this URL with an updated effective date. Material changes affecting your rights will be communicated by email before they take effect.

10. Contact

IssueLedger · San Francisco, CA
legal@issueledger.com