Privacy Policy

LensReport ("we", "our", or "us") operates the LensReport mobile application (the "App"), available on iOS and Android. This Privacy Policy explains what information we collect, how we use it, who we share it with, where it is stored, how long we keep it, and the rights you have over it.

By downloading, installing, or using LensReport, you agree to the practices described in this Privacy Policy. If you do not agree, please do not use the App.

1. Information We Collect

1.1 Information you provide

• Email address (optional) — collected if you choose to create an account via email, Google, or Apple sign-in. You may use the App with anonymous authentication and provide no personal information at all.
• Name / display name (optional) — collected from Apple Sign-In or Google Sign-In if you choose those providers. Used only to personalize your account and to show team members who added an entry to a shared report.
• Document images — photographs of receipts, invoices, expense reports, and similar documents that you capture with the camera or import from your photo library or PDFs. These images often contain personal or financial information printed on the documents themselves (vendor names, amounts, card last-four digits, names, addresses). We treat them as personal data.
• Extracted and manual entry content — the structured data pulled out of your document images by our AI pipeline (vendor, date, amount, tax, notes, etc.), plus any text you enter manually into a report.
• Business profile (paid tiers only) — business name, logo, address, and tax number that you optionally provide so that your exported reports can be branded. Stored only in your own account and used only on your exports.
• Team join-request data — if you are on a Team or Enterprise plan, you can generate a personal invite code (a short string in the form LENS-XXXXXX) and share it with the people you want to collaborate with. When someone enters your code in their own copy of the App, we create a join-request record containing their user ID, display name, and the email address on their Firebase Auth record, and we send you a notification so you can approve or decline. Pending requests expire after 30 days. We do not collect the recipient’s email separately from you, and we do not send an invitation email to anyone on your behalf.
• AI Insights questions and feedback — if you use the AI Insights advisor (Section 4), the text of your question and any thumbs-up / thumbs-down feedback you submit are processed and stored as described in that section.
• Onboarding industry tag (optional) — if during first-launch onboarding you select an industry from the tiled list, the resulting tag is stored on your profile so we can pre-select the most useful templates. No free-text industry input is collected and no AI classification call is made.

1.2 Information collected automatically

• Device identifier — a Firebase installation ID assigned to your app install, used to associate your device with your account.
• Push notification token — if you enable notifications (we only ask you to enable them after a deliberate action, never on first launch), we register a Firebase Cloud Messaging token with our backend so we can notify you when a teammate adds an entry to one of your reports.
• Scan and entry usage counts — the number of entries you create each billing period, broken down by team member for shared plans. Used to enforce your plan’s monthly entry limits (the free tier permits 5 entries per calendar month).
• AI usage counts — the number of AI Insights queries you have made today, used to enforce per-tier daily caps and to power abuse-prevention rate limits.
• App Check attestation token — a cryptographic token issued by Apple App Attest or Google Play Integrity that proves the request came from a genuine, unmodified LensReport install. The token is sent with each backend call and discarded after verification.
• Crash data — collected via Firebase Crashlytics to diagnose and fix app crashes. Includes device model, OS version, and stack traces. No document content is included in crash reports.
• Anonymized usage events — collected via Firebase Analytics to understand how features are used and improve the App. No document content or personally identifiable information is included.
• Language and country preference — stored locally so the App can pick sensible defaults for number, date, and currency formatting.

1.3 Information we do not collect

• We do not use Apple’s App Tracking Transparency (ATT) framework or any cross-app tracking technologies. We do not request the IDFA.
• We do not include any advertising SDKs or ad networks.
• We do not collect your precise or coarse location, contacts, calendar, microphone audio, biometric identifiers, health data, financial-account credentials, or advertising IDs.
• We do not perform cross-app or cross-site tracking of any kind.
• We do not read or process your message inboxes, SMS, or email.

2. How We Use Your Information

We use the information we collect for these purposes:

• AI-powered data extraction. Your scanned document images are sent to our Firebase backend, which calls the OpenAI API to extract structured fields (vendor name, amounts, dates, etc.). The extracted values are written to your report in Firestore.
• AI Insights advisor (optional). If you tap the AI Insights button on a report, we send a PII-redacted summary of that report’s entries plus your question to OpenAI to generate an answer grounded in your data. See Section 4 for full detail.
• Account management. To create and maintain your account, authenticate sign-in, and enforce your subscription plan’s entry limits and feature entitlements.
• Team collaboration. If someone enters your invite code, we store the resulting join-request record, notify you, and (after you approve) associate the new contributor with the reports they then have access to. Contributor activity (who added which entry) is visible to the report owner.
• Subscription management. To process your subscription purchases, renewals, and entitlements through the App Store / Google Play and RevenueCat, and to honor any scan top-up packs you purchase.
• Push notifications. To notify report owners in real time when a teammate adds an entry to one of their reports or when their monthly quota is exhausted. Notifications are only sent if you grant permission, which we request contextually, not on first launch.
• Share links. If you create a public share link for a report, we store a snapshot of the report’s verified entries so that the link recipient can view it without installing the App. You control whether the link is PIN-protected and when it expires.
• Service improvement. Anonymized crash data and usage analytics help us identify bugs, improve performance, and prioritize features.
• Security, integrity, and fraud prevention. We verify each request with App Check (Section 6), maintain server-side rate limits (for share-link PIN guesses, team invitations, and AI queries), enforce burst-violation lockouts, and keep an internal audit log of account-level and AI-related events to detect and respond to abuse.

3. Who We Share Your Data With (Subprocessors)

LensReport does not sell, rent, lease, or trade your personal data to any third party. We do, however, rely on a small number of trusted service providers ("subprocessors") to operate the service. Each of them acts under a written data-processing agreement and may only use your data to provide the services we ask them to:

3.1 OpenAI zero data retention

We use OpenAI’s API with zero data retention (ZDR) enabled for LensReport’s account. Under ZDR, OpenAI does not retain your submitted images, prompts, completions, or extracted data after the request completes, and does not use your data to train, improve, or fine-tune their models. This applies to all OpenAI calls we make: document-image extraction and the AI Insights advisor (questions and answers).

If you want to verify this commitment, you can contact us at info@lensreport.app and we will confirm our current ZDR status.

3.2 PII redaction before AI Insights calls

Before the AI Insights advisor (Section 4) sends any text to OpenAI, our backend automatically redacts the following categories from notes, descriptions, and your typed question:

• Email addresses (replaced with placeholders such as [email-1]);
• Phone numbers in any common locale format;
• Government identifier patterns (national IDs, tax IDs, social security numbers);
• Credit card numbers that pass the Luhn check;
• IBAN-style bank account numbers.

Vendor names, merchant names, and payee names are deliberately preserved because the advisor needs them to answer questions like “how much did I spend at X?”. PII redaction applies to the AI Insights surface; the underlying document-image extraction itself necessarily transmits the visible image content under ZDR.

3.3 No sale of data, no profiling for advertising

We do not sell, rent, lease, or trade your personal information to any third party. We do not share your data with any third party for their own marketing, advertising, profiling, or behavioral-advertising purposes.

4. AI Features

LensReport offers two optional features that involve calls to OpenAI’s API. Both run under the zero-data-retention agreement described in Section 3.1.

4.1 AI-powered document extraction

This feature is the core of the App. When you scan or import a document, the image is uploaded to Firebase Cloud Storage, then forwarded to OpenAI to identify the vendor name, date, amounts, line items, and other fields appropriate to the template you chose. The extracted values are written to your report in Firestore. The image is retained alongside the entry until you delete it; the OpenAI request and response are not retained by OpenAI per ZDR.

If you would prefer not to send any image to OpenAI, you can use the App’s manual-entry feature to type the values directly — this still creates a normal entry, just without the AI extraction step.

4.2 AI Insights advisor

AI Insights is an optional in-app feature available to paid subscribers on any tier. Free contributors on a paid owner’s shared report do not automatically inherit AI Insights access — they see a paywall when they tap the AI button and must subscribe to use the feature themselves. AI Insights lets you ask questions about a report in natural language and receive answers grounded in your own entries. Some questions are descriptive (“what was my biggest purchase last month?”); others are advisory (“am I spending too much on fuel?”). The advisor is informational only and is not a substitute for professional advice; this is disclosed in-product on every advisory answer.

What we send to OpenAI for an AI Insights query:

• Your question text, after PII redaction (Section 3.2);
• A structured summary of the relevant entries from the current report (vendor, date, amount, category, and similar already-extracted fields), with PII redacted from any free-text description or notes columns;
• The display name of the column (e.g. “Vendor”, “Amount”) and your preferred currency and language — so the answer can be formatted correctly;
• For follow-up questions, the last few question/answer turns from the same report’s conversation history (see “Conversation memory” below).

What we do NOT send to OpenAI for an AI Insights query:

• Your scanned images (only the structured fields extracted from them);
• PII tokens that the redactor caught (they leave our backend as opaque placeholders);
• Other reports you own — each query is scoped to one report;
• Your account email, display name, or device identifier.

Audit log. Every AI Insights call is recorded in an append-only audit log stored at users/{your-id}/aiAudit/{event}. Each audit row contains the operation type, the outcome (success / hard-refused / crisis-redirect / no-match / etc.), a SHA-256 hash-prefix of your question (never the question text itself), latency, and a timestamp. No document content and no answer text is written to the audit log. The log is retained for the lifetime of your account and is removed when you delete your account; we keep it only for product / abuse-monitoring purposes during the life of the account, on the legitimate-interest basis under GDPR Article 6(1)(f). It is not used for any other purpose.

Conversation memory. So that follow-up questions feel coherent (“and what about last month?”), we keep a per-report conversation history at users/{owner-id}/reports/{report-id}/aiConversations/{turn}. For most turns we store the PII-redacted question, the question’s identity hash, a 1–2 sentence summary of the answer narrative (used to give the LLM continuity context on follow-ups), the outcome, and the timestamp — never the full answer body, never any document content. Two exceptions: hard-refused turns (medical / legal / etc.) store only the refusal category, with no question text and no summary; crisis-redirect turns are never stored at all so distress signals do not propagate to anyone else with access to the report. On a shared report, this conversation history is readable by every collaborator with access to the report: if your teammate asks about Q3 fuel spend yesterday, the AI knows that context when you ask a follow-up today. The history is retained for 12 months from the last turn (Firestore TTL), stored under the owner’s namespace, and deleted when the report is deleted or when the owner’s account is deleted.

Response cache. To keep AI costs predictable and to make repeat questions feel instant, we cache successful answers for up to 24 hours per (report, question, data state) tuple at users/{owner-id}/reports/{report-id}/aiCache/{key}. Cached entries expire automatically and are deleted when the report is deleted.

Daily usage caps. AI Insights is rate-limited per Firebase user account. Free users have no AI Insights quota; every paid tier (Individual, Family, Enterprise) gets a flat 30 queries per day. Each user draws from their own counter — including contributors on a shared report, who must subscribe in their own right to use the feature. Within the daily cap, a short-burst limiter (8 queries per minute) prevents accidental script loops; three burst-limit hits in 10 minutes triggers a 15-minute lockout on the affected account.

Feedback (optional). Every answer has a thumbs-up / thumbs-down control. If you tap thumbs-down, you can pick a closed-list reason (“wrong about my data”, “bad recommendation”, “felt judgmental”, “not helpful”, “other”). The feedback row stores only the question identity hash, your reason selection, and a timestamp — no free-text comment is collected and no question or answer text is included. Feedback is stored at users/{your-id}/aiFeedback/{event} and is used to improve prompts and detect regressions.

Crisis and refusal handling. If your free-text question matches one of our hard-refusal categories (medical / clinical, legal advice, specific investment advice, tax-filing decisions, drastic operational actions, attempts to extract another user’s personal data, or prompt-injection attempts), the request is rejected before we call OpenAI — no tokens are sent. If the question matches our crisis-detector keyword bag (mental-health distress, financial distress, threats of harm to others), we return a card pointing to the appropriate local support resources (suicide-prevention hotline, financial-counselling service, etc.) instead of any AI-generated answer. The crisis card never reaches OpenAI and the crisis turn is not added to the report’s conversation history; only the audit-log entry exists.

Cost monitoring. We run an automated daily summary that aggregates AI usage across all users to detect abuse and runaway cost. The summary contains only counts and totals (e.g. “1,200 calls today, $3.40 spend”) — no per-user or per-query detail is included. If the daily total exceeds an internal threshold, an email alert is sent to our operations address.

4.3 Opting out of AI Insights

AI Insights is opt-in by definition: it only runs when you tap the AI button on a report. If you never tap it, no AI Insights data is processed or stored. To remove an existing conversation history, delete the report (which deletes all associated AI conversation, context, and cache rows under the owner’s namespace) or delete your account (which deletes the same data plus your AI audit log and AI feedback rows).

AI Insights is not available on the free tier. Each user who wants to use the feature must hold a paid subscription in their own right; the owner of a shared report does not pay for a contributor’s AI usage. Owners can remove a contributor from a team at any time from the Collaborate screen, which also revokes the contributor’s read access to the conversation history on every report they previously had access to.

5. Data Storage and Retention

5.1 Account-level audit log retention

LensReport maintains a server-only audit log that records account-level operations: account deletion, data export requests, team invitations (created / accepted / rejected), team member removals, and share-link creation and revocation. Each audit entry contains only the actor’s anonymized user ID, the action type, and a timestamp. No document content, no images, no answer text, and no contents of your reports are ever written to the audit log.

These audit entries are retained indefinitely, even after account deletion, because they support our ability to investigate security incidents, respond to legal requests, and comply with anti-fraud obligations. This is the legitimate-interest basis under Article 6(1)(f) of the GDPR.

6. Data Security

We implement appropriate technical and organizational measures to protect your data:

• All traffic between the App and our servers is encrypted with TLS 1.2 or higher. Cleartext HTTP is explicitly disabled on both iOS and Android.
• Document images are uploaded directly to Firebase Cloud Storage, which enforces Firebase Security Rules so that only you (or a contributor you have invited to the report that owns the entry) can read them.
• App Check device integrity. Each backend call carries a cryptographic attestation token issued by Apple App Attest (with DeviceCheck fallback) on iOS and Google Play Integrity on Android. Tokens are short-lived and verified server-side; their purpose is to prove the request came from a genuine, unmodified LensReport install rather than a reverse-engineered or scripted client. The tokens never carry personal data.
• PII redaction (Section 3.2) is applied before any text is sent to the AI Insights endpoint.
• Sensitive local state — specifically, the share-link PIN cache so that the link owner can re-share the same PIN later — is stored in the platform secure enclave (iOS Keychain / Android EncryptedSharedPreferences), scoped per-user so that a second account on the same device cannot see another account’s cached values.
• Account deletion requires fresh re-authentication: if your session is older than 5 minutes, the App will prompt you to sign in again before completing the deletion. This protects against a stolen session being used to irreversibly destroy an account.
• Share-link PINs are hashed with bcrypt (cost factor 12) and enforce per-token rate limiting: after 5 incorrect PIN attempts, the link is locked for 15 minutes. Share-link expiry is capped at 30 days to bound any attacker’s total guess budget.
• Team join requests are rate-limited per requesting user (maximum 10 join-request submissions in any 24-hour window) to prevent code-guessing and bulk join attempts. Invite codes themselves use a 6-character Crockford base-32 alphabet (~1 billion combinations); requesters who try invalid codes receive a generic “try again later” response rather than a code-not-found error so the rate limit cannot be used to enumerate valid codes.
• AI Insights enforces per-tier daily caps and a per-minute burst limit. Three burst violations within 10 minutes trigger a 15-minute lockout on the offending account (Section 4.2).
• OpenAI extraction errors are sanitized before being returned to the client: internal error details and request IDs stay on our servers, and the client receives only a generic “extraction failed” message with a correlation ID for support.
• Firebase Security Rules enforce access control at the database level, preventing anyone except the report owner (and explicitly-invited contributors) from reading or writing your reports and entries. Audit, feedback, conversation, and cache collections are server-only: clients have no read or write access to them.

No method of transmission or storage is 100% secure. While we strive to use commercially reasonable means to protect your data, we cannot guarantee absolute security.

7. Your Rights and Choices

7.1 Delete your account

You can delete your account at any time from Settings → Delete Account. Deletion is a two-step confirmation flow and requires fresh re-authentication. Once confirmed, we remove from our systems:

• Every report, entry, scanned image, and Business Profile asset in your account.
• Every team membership and share link you created.
• Your scan and entry quota history and any outstanding top-up balance.
• Your Firebase Auth record (email, display name, social sign-in links).
• Any pending team join-requests addressed to you and your personal invite code.
• Your AI Insights conversation history, response cache, audit log, and feedback rows.

Some data is retained for legitimate-interest reasons even after deletion: the server-side account-level audit log described in Section 5.1 (which contains only action type, timestamp, and an anonymized identifier — no scan content, no question text, no answer text), and subscription records held by the App Store / Google Play / RevenueCat for legal and tax compliance.

Reminder: deleting your LensReport account does not automatically cancel any active subscription billed by the App Store or Google Play. Cancel the subscription separately through your iOS Settings or Google Play Store.

7.2 Anonymous use

You may use LensReport with anonymous authentication — no name, no email, no social account required. Most features that do not involve collaboration, AI Insights, or export are available anonymously. Creating a real account (by adding email, Google, or Apple sign-in) is required only when you want to subscribe, export a report, use AI Insights, collaborate, or back up your data to the cloud.

7.3 Export all your data (data portability)

You have the right to receive your personal data in a structured, machine-readable format. LensReport offers two complementary export paths:

• Individual report export — in any report, tap the upload icon to export that report as PDF, Excel, or CSV. Excel exports preserve live formulas (Smart Columns), not hard-coded values.
• Full account export (GDPR Article 20) — from Settings → Export my data, you can request a full JSON bundle containing your profile, every report, every entry, quota history, team memberships, invitations, and active share tokens, together with short-lived signed URLs to download each scanned image. The JSON is delivered via a signed Cloud Storage link valid for 7 days. You can request a fresh export at any time.

7.4 Manage share links

Every share link you create is listed under Settings → Manage Shared Reports, where you can revoke any link immediately. Revoking a link deletes its Cloud Storage snapshot and prevents further views.

7.5 Leave or remove from a team

Report owners can remove a contributor from a team at any time via the Collaborate screen. Removal takes effect immediately: the contributor loses access to all shared reports and a 30-day cooldown applies before they can rejoin the same team. If you are a contributor and want to leave a team you no longer wish to be part of, email us at info@lensreport.app and we will process the request within 5 business days.

7.6 Opt out of AI Insights

AI Insights is opt-in by use: it only runs when you tap the AI button on a report. To clear any conversation history that has built up, delete the report (which removes all associated conversation, context, and cache rows under the owner’s namespace) or delete your account (which removes the same data plus your AI feedback rows). The audit log entries remain per Section 4.2.

8. Team Collaboration

Team and Enterprise subscribers can generate a personal invite code (in the form LENS-XXXXXX) and share it with the people they want to collaborate with. Anyone who knows your code can submit a join request from inside the App; you then approve or decline it. Approved contributors sign in with their own accounts and consume their own scan / entry / AI quota — we do not operate a shared-pool model.

• When someone submits a join request using your code, we store their user ID, display name, and Firebase Auth email on the join-request record so you can see who is asking. We do not ask you for the recipient’s email and we do not send any email on your behalf.
• Pending join requests expire after 30 days if you do not respond.
• When a contributor adds an entry to one of your reports, their user ID and display name are attached to that entry so that you can see who added what, and you may receive a push notification.
• Contributors see each other’s display names within the shared report. They do not see each other’s email addresses unless the report owner chooses to share them.
• Team activity (per-contributor scan counts, recent activity, quota consumption) is visible to the report owner on the Team Activity dashboard.
• AI Insights conversation history on a shared report is readable by every collaborator with access to the report, so follow-up questions retain context (Section 4.2).

9. Public Share Links

LensReport lets owners of a paid plan generate a public share link for a report. The link points to a read-only snapshot of the report’s verified entries hosted at share.lensreport.app. The recipient does not need to install the App or sign in to view it. Optionally, the owner can require a 6-digit PIN to open the link.

• The snapshot stored in Cloud Storage intentionally excludes sensitive metadata: contributor identifiers, per-entry timestamps, verification status, and duplicate-detection fingerprints are stripped before the snapshot is written.
• You choose the link’s expiry from the following options: 1 hour, 24 hours, 7 days, or 30 days. Expired links stop working automatically.
• You can revoke any share link at any time; revocation deletes the snapshot and invalidates the URL immediately.
• The number of times a share link has been viewed is visible to you in the App.
• PIN-protected links enforce a 5-attempts-per-15-minutes lockout per link to prevent brute forcing.

10. Rights for Users in the European Economic Area, United Kingdom, and Switzerland (GDPR)

If you are located in the European Economic Area (EEA), the United Kingdom, or Switzerland, you have the following rights under the General Data Protection Regulation (GDPR) and related data-protection laws. We honor these rights regardless of your location.

Legal bases for processing. We process your data based on (a) the performance of a contract with you under Article 6(1)(b) — to provide the scanning, extraction, AI Insights, collaboration, and export features you asked for; (b) your consent under Article 6(1)(a) where applicable — for optional analytics, push notifications, and any AI Insights interaction; and (c) our legitimate interests under Article 6(1)(f) — to keep the account-level and AI audit logs and to enforce security rate limits, App Check verification, and anti-fraud controls.

10.1 EU representative

LensReport is operated from Fiji and does not currently have an appointed representative in the European Union under Article 27 of the GDPR. We are working to close this gap. Until then, EEA / UK / Swiss users who wish to exercise their rights can contact us directly at info@lensreport.app. We will update this section with the representative’s name and contact details as soon as one is appointed.

10.2 Response time

We aim to acknowledge every request within 5 business days and to complete it within 30 days, in line with the GDPR’s one-month response window. Where a request is unusually complex or we have received a large number of requests, we may extend by up to two further months in accordance with Article 12(3) GDPR, and we will let you know why.

11. Rights for Users in California (CCPA / CPRA)

If you are a California resident, the California Consumer Privacy Act (CCPA) and the California Privacy Rights Act (CPRA) give you the following rights:

• Right to know — this Privacy Policy is the disclosure of what we collect, why, and who we share it with.
• Right to delete — use Settings → Delete Account in the App, or email info@lensreport.app.
• Right to correct — edit your profile and your reports directly in the App.
• Right to opt-out of sale or sharing — we do not sell or share your personal information for cross-context behavioral advertising, so there is nothing to opt out of. We also do not use sensitive personal information for any purposes outside of providing the service you requested.
• Right to limit use of sensitive personal information — we do not process sensitive personal information for purposes that are outside the consumer’s reasonable expectation of the service.
• Right to non-discrimination — we will not discriminate against you for exercising any of your CCPA rights.

Categories of personal information we collect. Identifiers (Firebase UID, email address, display name, device installation ID); commercial information (subscription state, purchase history); internet or other electronic network activity information (entry counts, AI usage counts, anonymized analytics events, crash reports); visual information (document images you choose to scan or import); inferences (the industry tag derived from your onboarding choices, used to suggest templates).

Categories of personal information we disclose for a business purpose. Visual information (document images) is disclosed to our OpenAI subprocessor solely to perform AI extraction, and to our Firebase / Google subprocessor solely for storage. PII-redacted report summaries and your typed AI Insights questions are disclosed to OpenAI solely to generate the requested AI Insights answer. Identifiers and commercial information are disclosed to Firebase, RevenueCat, Apple, and Google solely for the purposes described in Section 3.

12. Children’s Privacy

LensReport is not directed at children under the age of 13, and we do not knowingly collect personal information from children under 13. The App is rated for users aged 4+ on the App Store and is not designed for use by children to record their own personal data. If you are a parent or guardian and believe that your child has provided us with personal information, please contact us at info@lensreport.app and we will delete it promptly.

13. International Data Transfers

Your data is stored and processed in countries other than your country of residence, including the United States (Firebase, OpenAI, RevenueCat, Postmark) and other regions where Firebase operates (EU, Asia-Pacific). When we transfer data to these jurisdictions, we rely on the data-processing and standard-contractual-clauses agreements of our subprocessors to provide an adequate level of protection as required by applicable data protection laws.

14. Apple App Store and Google Play Store Disclosures

This section maps our data practices to the disclosures we make in Apple’s App Privacy Nutrition Labels and Google Play’s Data Safety form, so you can cross-check.

• Data linked to you: email address, display name, scanned document images, extracted entries, subscription state, AI Insights questions and feedback, onboarding industry tag.
• Data not linked to you: hashed source IP for onboarding rate limiting; anonymized Firebase Analytics events; aggregated AI cost-monitoring counts.
• Data used to track you across other apps and websites: none. We do not use the IDFA, do not call requestTrackingAuthorization, and do not include any advertising or attribution SDKs.
• Required Reasons API declarations. The iOS Privacy Manifest (PrivacyInfo.xcprivacy) declares only the Required Reasons we actually use: UserDefaults (CA92.1, app preferences), file timestamps and disk space (C617.1 / E174.1, file management), and system boot time (35F9.1, performance measurement). We do not declare or use any tracking-related Required Reasons.
• Account deletion. You can delete your account in-app from Settings → Delete Account, satisfying App Store Review Guideline 5.1.1(v). See Section 7.1.
• Sign in with Apple is offered as an authentication option per App Store Review Guideline 4.8.

15. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. When we make material changes, we will notify you by posting the updated policy within the App or by other appropriate means, and we will update the “Last Updated” and “Version” fields at the top of this page. Continued use of the App after the effective date of the revised policy constitutes your acceptance of the changes. If you do not agree, please stop using the App and delete your account.

16. Governing Law

This Privacy Policy is governed by and construed in accordance with the laws of the Republic of Fiji, without regard to its conflict-of-law provisions. Any disputes arising under or in connection with this Privacy Policy shall be subject to the exclusive jurisdiction of the courts of the Republic of Fiji, except where the GDPR, CCPA, or other applicable local law gives you a mandatory right to bring proceedings in your own country.

17. Contact Us

For any privacy-related request, including access / deletion / portability requests, questions about this policy, or reports of a suspected data incident, please contact:

Email: info@lensreport.app

We aim to acknowledge privacy requests within 5 business days and to resolve them within 30 days.