Privacy
A default privacy overview for LOOM installations. Deployment owners should customize this notice for their own organization, jurisdiction, integrations, and data practices.
What LOOM can store
Depending on enabled modules and installation settings, LOOM can persist guest identities, permanent account details, project identities, project state, activity/audit records, referral attribution, uploaded assets, administrative configuration, and continuity metadata used to recognize a likely returning anonymous guest across browser contexts.
Anonymous continuity
LOOM can compare coarse browser/device traits together with already-recorded network metadata to decide whether a fresh browser is very likely to continue one recent, unclaimed Guest Identity. LOOM stores normalized hashes rather than a raw permanent hardware identifier, refuses automatic recovery when a device appears shared or the current network differs, and never treats continuity as authentication. Permanent-account, Admin, purchase, private-message, and other authenticated authority still require durable verification.
Sharing and referrals
Attributed share links contain an opaque referral code. A link is reusable and may be opened by many people. Opening your own share link is recorded as a self-visit but does not consume or disable the link and never earns referral credit. When a recipient follows one, LOOM can record the referring identity, destination, link-open counts, and a durable referral relationship after the recipient selects or creates a LOOM identity. Referral codes do not contain the referrer’s email or password.
Deployment owner responsibility
LOOM is deployable software. The operator of a particular LOOM installation controls its hosting, connected services, retention policies, user access, and legal notices. This packaged notice is a technical baseline, not a substitute for deployment-specific legal review.