Privacy Policy

Loom Privacy Policy

Effective Date: July 21, 2026. This page explains what Loom collects, how it is used, where it is stored, what optional permissions do, and how to manage your privacy choices.

Contact

Privacy questions or deletion follow-up: spencer@loomlife.us

Support and privacy-management page: support.html#privacy-choices

Contents

Use this page as the public privacy policy for Loom.

Get Loom on iPhone

Loom is built for people who want purpose, goals, tasks, habits, reflection, and LoomAI in one life-management app.

1. What Loom Collects

Account and identity data

  • Name and email address
  • Account identifiers associated with Firebase Authentication, Sign in with Apple, Google Sign-In, or email/password sign-in
  • Subscription entitlement status and current plan label used by the app

Content you create in Loom

  • Purpose, vision, passions, fulfillment areas, goals, plans, action blocks, little wins, reflections, notes, and related archives or progress records
  • Diagnostic and onboarding answers, personalization snapshots, profile outputs, and other product-generated insights
  • LoomAI chat messages, prompts, and related context used to generate replies or suggestions
  • Feedback submissions, ratings, support details, and message text you choose to send through Loom

Shared, imported, and attached content

  • Text, links, images, videos, and files shared into Loom from other apps through the Share into Loom extension
  • Photos or files you import into actions or plans
  • Link metadata and previews when Loom renders link previews

Optional permission-based data

  • Apple Health data you choose to connect, such as steps, workout minutes, sleep, or selected outcome metrics
  • Camera images, imported photo attachments, and Photos library saves when you use Loom camera or attachment features
  • Reminder data from Apple Reminders if you connect that integration

Usage, diagnostics, website activity, and app state

  • Production-only funnel, setup, paywall, purchase, retention, and app engagement events collected by Firebase Analytics in eligible production installs
  • App instance or device-level identifiers used by Firebase services to support analytics and diagnostics in eligible production installs
  • Website page views and interactions collected by Google Analytics, including ambassador application open, submit, success, and error events. These custom events do not include the information entered into application fields
  • Browser and device details, referring page, analytics identifiers, and approximate location derived from network information when Google Analytics operates on the website
  • Aggregate Apple App Store campaign information, such as a broad audience or campaign label attached to a Loom-owned App Store link
  • Crash and performance diagnostics collected by Firebase Crashlytics in production builds
  • Local app settings, session flags, cached previews, notification settings, and other saved preferences

Analytics events are designed not to include your name, email address, customer record, or user-authored Purpose, Fulfillment, Goal, diagnostic, LoomAI chat, reminder, feedback, or free-text planning content. Loom does not use anonymous analytics identifiers to identify an individual purchaser.

Billing and Apple-managed purchase data

  • StoreKit product and entitlement status used to unlock features
  • Renewal status and subscription period information returned by Apple
  • Purchase and subscription interaction events, selected product identifiers, restore outcomes, and StoreKit revenue details may be recorded in Firebase Analytics when analytics collection is enabled in eligible production installs
  • Loom does not receive your full Apple payment card details

Website and ambassador application data

  • Name, email address, country or region, and any website or portfolio you provide
  • Audience type, primary platform, social handles or profile links, audience-size range, content focus, and audience description
  • Your Loom experience, prior ambassador or affiliate experience, referral source, proposed promotion plan, and reasons Loom fits your audience
  • Your eligibility, accuracy, age, and contact confirmation, plus the application page URL, source label, and submission timestamp

2. How Loom Collects Information

  • Directly from you when you create an account, sign in, complete onboarding, type content, chat with LoomAI, submit feedback, or configure plans and goals
  • From your device and app use through local storage, notification settings, analytics, diagnostics, and saved app state
  • From Apple frameworks and system services you choose to use, such as HealthKit, EventKit reminders, camera, Photos, and notifications
  • From sign-in providers you choose to use, including Sign in with Apple and Google Sign-In
  • From content you share into Loom using the Share into Loom extension
  • From aggregate Apple App Store campaign reporting when you follow a Loom-owned campaign link to the App Store
  • Directly from you when you submit an ambassador application or another form on Loom's website
  • From your browser and website use through Google Analytics when it operates on the site

3. How Loom Uses Information

  • To create and manage your account, authenticate sign-in, and keep your session active
  • To provide Loom's planning, goal, fulfillment, capture, reminder, attachment, and reflection features
  • To personalize the app, generate inferred profiles or insights, and tailor setup or AI suggestions to your context
  • To enable optional integrations you request, such as Health or Reminders
  • To process purchases, restore purchases, and determine premium access through Apple's StoreKit systems
  • To improve app quality, reliability, and performance through analytics, diagnostics, and feedback review
  • To measure, in aggregate, which Loom-owned audience campaigns lead to App Store views, downloads, or purchases
  • To respond to support requests, bug reports, and feedback you submit
  • To evaluate ambassador applications, contact applicants, administer the ambassador program, and prevent fraud or abuse
  • To understand website use and whether the ambassador application flow is functioning, without sending application field values in custom analytics events

4. Where Data Is Stored

On your device

  • Main app data is stored locally using SwiftData, Application Support files, and UserDefaults
  • Imported files and photos are stored in local app storage for attachment features
  • Shared content from the Share into Loom extension is first written into Loom's shared app-group container so the app can ingest it
  • Loom does not sync its main app database through iCloud or CloudKit

Remote storage and service providers

  • Firebase Authentication is used for account sign-in and identity
  • Firebase Firestore may store personalization snapshots for authenticated users
  • Firestore also stores app feedback submissions you choose to send from the app
  • Firebase Analytics and Firebase Crashlytics may receive usage and diagnostic data in eligible production installs
  • Ambassador applications are delivered through FormSubmit to Loom's email inbox for review and program administration
  • HealthKit data, Reminders data, imported attachments, and link preview cache entries are not uploaded to Loom-managed servers as part of their core feature flow

5. Third Parties and Service Providers

Loom does not sell your personal information. Loom uses the following service providers and platform services when needed to operate the app and website:

  • Apple for Sign in with Apple, StoreKit purchases, App Store campaign reporting, notifications, HealthKit, EventKit reminders, camera/photos access, and other Apple frameworks you use
  • Google / Firebase and Google Analytics for authentication, app and website analytics, crash diagnostics, Firestore-backed personalization sync for authenticated users, and app feedback submissions
  • FormSubmit to process, temporarily store, and email ambassador application form submissions to Loom

Loom-owned App Store campaign links use fixed campaign labels for broad audience groups. They do not put a recipient's name, email address, CRM identifier, or other recipient-specific identifier in the link. Loom uses the resulting Apple reports only in aggregate and does not combine them with third-party data to track a person across apps or websites owned by other companies.

6. AI Features

  • Some Loom AI features can run on device using Apple Intelligence when available and enabled on a supported device
  • On devices without Apple Intelligence support, Loom uses built-in local compatibility logic to provide suggestions and guidance on device
  • AI features use the text you send plus related planning and personalization context needed to answer the request

7. Optional Permissions and Integrations

  • Health: You can choose whether to connect Apple Health data. Loom reads selected health metrics and does not write data to Apple Health. That data remains on your device and in Apple's Health framework unless you separately share it elsewhere
  • Reminders: You can choose whether Loom can read and update Apple Reminders you sync into Capture. Reminder data stays on device and in Apple's Reminders framework unless you separately share it elsewhere
  • Camera and Photos: You can choose whether Loom can use the camera, import photo attachments, or save generated images to Photos
  • Notifications: You can choose whether Loom can schedule local reminders and alerts

You can revoke most app permissions at any time in iOS Settings.

8. Link Previews, Shared Content, and Attachments

  • If you add or share a web link, Loom may request link preview metadata through Apple system frameworks to render a preview card
  • If you share text, links, images, videos, or files into Loom, that content may be written into Loom's shared app-group storage before you review and save it
  • Imported files and images are stored locally for attachment features
  • Link preview cache entries are stored locally on your device
  • Loom does not upload attachment files to Loom-managed servers as standalone files
  • Loom does not send your links to Loom-managed servers to generate preview cards

9. Data Retention

  • Loom keeps your local app data until you delete it, delete your account, remove the app, or clear the relevant local state
  • Firestore personalization records are retained while needed for the signed-in Loom account and are cleared when the app's account-deletion flow resets that state
  • Feedback submissions may be retained as support or product records even if you later delete your account
  • Analytics and crash data may be retained for operational, security, fraud-prevention, debugging, legal, or provider-policy reasons
  • App Store campaign results may be retained as aggregate business records; Loom does not retain a campaign-to-purchaser identity mapping
  • Received ambassador applications may be retained while Loom evaluates the application, administers the program, prevents fraud, and maintains appropriate business or legal records. FormSubmit states that it retains form submissions for 30 days

10. Your Choices, Access, and Deletion

  • You can update some account information inside the app
  • You can revoke permissions in iOS Settings and disconnect optional integrations you no longer want to use
  • You can use Loom's in-app Account > Delete Account flow to delete your account and remove your local app data
  • For supported sign-in methods, Loom's deletion flow reauthenticates the account and, for Sign in with Apple, revokes Apple authorization before deleting the Firebase account
  • Deleting your Loom account does not automatically cancel Apple subscriptions. Apple subscriptions must be canceled separately in Apple Account Settings
  • For privacy choices, support, or deletion follow-up, you can also visit support.html#privacy-choices
  • If you need privacy help or a deletion-related follow-up, contact spencer@loomlife.us
  • Ambassador applicants may use that same email address to request access to, correction of, or deletion of their submitted application information

11. Security

Loom uses reasonable administrative, technical, and organizational safeguards appropriate to the app's size and design. No system can guarantee absolute security.

12. Children's Privacy

Loom is not intended for children under 13, and Loom does not knowingly collect personal information from children under 13.

13. International Processing

Loom, its service providers, and infrastructure providers may process information in countries other than your own.

14. Changes to This Policy

Loom may update this Privacy Policy from time to time. The current version will be posted at this URL with an updated effective date.

15. Contact