Privacy Policy

Effective October 28, 2026

Formlore is operated by Zhiwei Wang. It helps you create and share interactive assembly instructions. For privacy questions or requests, contact [email protected].

Information we use

When you continue with Google, we receive your Google account identifier, email address, name, profile picture and email verification status. We request only OpenID, email and profile permissions. We do not request access to Gmail messages, Google Drive files or contacts.

For email accounts, we store your email address, account name and a password hash. We also store your products, assembly instructions, publication settings, API credentials in protected form, login sessions and technical security logs. Materials you send directly to an external AI service are governed by that service's policies.

Why we use it

We use this information to sign you in, protect your account, save your projects, deliver account emails, operate authorized API requests and publish instructions when you choose to do so. Published instruction links can be viewed without signing in. Your unpublished projects require authorized access.

Service providers

We use Netcup for hosting in Germany, Cloudflare for DNS, traffic protection and backup storage, Brevo for account emails, Google for optional sign-in, and PostHog US Cloud for product analytics. They process information needed to provide these services. Data may be processed outside your country. We do not sell personal information or use Google account data for advertising.

Product analytics

On the production website, PostHog records page and feature events to help us understand how visitors find Formlore, where creation and viewing flows fail, and whether guides are published and used. Events can include an identifier kept in memory for the current page load, internal account or product identifiers, interface language, coarse referral category, device information, event time, status and standardized error codes. We do not write that identifier or the referral category to local storage or cookies. Each full page load starts with a new in-memory identifier. After you sign in, later events from that same page load use your account identifier. Events from before that sign-in, and anonymous visits on other page loads, are not tied to it by a stored browser identifier. We do not send account email addresses, names, product names, manual files, prompts, passwords, tokens or authorization keys in our analytics events. URLs are reduced to safe page categories. Automatic click analytics and heatmaps are disabled. Analytics failure does not prevent using the service.

We also use privacy-masked session replay on the production website to investigate usability problems. It reconstructs page layout, navigation, clicks and scrolling. Page text and form values are masked before transmission; media, 3D canvases, embedded frames, code blocks and inline stylesheets are excluded. Public bundled stylesheets are retained to reconstruct page layout. Link destinations and other content-bearing element attributes are removed, and page URLs are reduced to safe categories. We do not record console logs, network request bodies or headers. Recordings are retained for up to 30 days under our current configuration.

Cookies and storage

Essential cookies keep you signed in and protect the sign-in flow. Browser storage saves interface preferences and tutorial progress. Product analytics does not save a visitor identifier or a first-touch referral category in local storage or cookies. The referral category is calculated for the current page load and kept in memory only. When analytics starts on the production website, it removes any previously stored analytics identifier, first-touch category, and internal-traffic marker from local storage, and expires the PostHog analytics cookie if one is still present. That cleanup leaves sign-in cookies, interface preferences, and tutorial progress in place. You can remove browser storage in your browser settings. Clearing it removes local preferences and progress, and it does not by itself prevent analytics collection when you revisit. Contact us for questions or requests about analytics data. We do not currently provide a separate in-app analytics opt-out control.

Retention and your choices

We keep account and project information while needed to provide the service. You can delete individual projects in your product library. Contact us to request account deletion, access to your information or correction of account details. Deleted information may remain temporarily in security logs and rotating backups; backups are retained for up to 30 days. You can revoke Formlore's Google access in your Google account settings; this does not by itself delete your Formlore account.

Security and updates

We use HTTPS, hashed passwords, access controls and encrypted OAuth access tokens. No service can guarantee absolute security. We will update this policy when how we handle data changes, and publish the effective date here.