LineReconPrivacy Policy
Last updated .
This policy covers the LineRecon app at app.linerecon.com and this website, including the Talk to us form. Our terms of service set out the rules for using LineRecon.
Who we are
LineRecon is operated by Oakrelay Labs LLC, a limited liability company registered in Wyoming. Contact: support@linerecon.com.
What we collect
Website and the Talk to us form.
Your email, plus a description of your workflow, company name and monthly comparison volume if you choose to provide them. We also record a request ID, submission time, form version, and limited campaign codes from the page URL. Please do not include confidential document contents or customer information.
Your account.
When you sign in with Google, we receive your Google account ID, email address and name. We ask Google only for the openid email profile scopes, so we cannot read your Gmail or Google Drive. You can also sign in with a one-time code sent to your email address. For sign-in rate limits we keep a keyed hash of your IP address, not the raw address. The app uses a cookie to keep you signed in.
Workspace content.
The files your workspace uploads, the page images made from them, and what LineRecon produces from them: extracted values, evidence, model responses, comparisons, corrections, review decisions and exported reports. We also keep workspace membership, invitations, and records of who did what in the workspace.
Billing.
Your trial claims, workspace credit history, order and payment identifiers, payment status, and credit and entitlement records. Payments are processed by Stripe through hosted Checkout. Stripe processes your card details; LineRecon does not store full card numbers.
Usage.
Records of the processing your workspace runs and the credits it uses, so we can charge, return credits and show the credit history.
How we use it
- to sign you in and keep your account and workspace secure;
- to process your documents and show the results to your workspace;
- to record credit usage, return credits and manage trial claims;
- to send sign-in codes, invitations and other service emails;
- to understand the workflow you describe on the website and respond to your request;
- to understand website and app use through analytics, heatmaps and session recordings, as described below.
Submitting the website form does not subscribe you to a newsletter. We do not accept document uploads or payments on the website itself.
AI processing
To read your documents, LineRecon sends page images to Google Vertex AI. Google processes them under Google Cloud's terms for that service. We do not use your documents to train AI models.
Service providers
- Oracle Cloud: hosting the backend, database and document-processing workers.
- Google Cloud: sign-in with Google (Google Identity Services), document reading (Vertex AI) and storage of uploads, page images and backups (Cloud Storage).
- Cloudflare: network and edge services for the app and website, sending email, storing website form requests (Cloudflare Workers and Cloudflare D1), and Cloudflare Turnstile, which helps prevent automated form submissions.
- Stripe: hosted Checkout and payment processing, including card details supplied during checkout. See Stripe’s privacy policy for its data handling practices.
- Google Analytics: measurement on the marketing website and app.
- Plausible Analytics: cookieless, aggregate page-view measurement on the marketing website and app.
- Microsoft Clarity: heatmaps and session recordings on the marketing website and app.
Network requests to these services include technical information such as your IP address. A short-lived hash of the IP address is used for website form request limits; raw IP addresses are not stored in our leads database.
We also send the submitted website form details through Cloudflare Email Service to the operator’s Gmail inbox so we can follow up. Google processes and stores this email copy as the mailbox provider.
Where data is stored
The current deployment runs the backend, database and document-processing workers in Seoul, South Korea. Google Cloud object storage and Vertex AI model processing are in the United States. Cloudflare's global delivery network and other service providers may process information in other regions.
Retention and deletion
- Website form requests: our policy is to delete submitted requests after 90 days unless you agree to an ongoing evaluation. Short-lived rate-limit records expire after approximately 10 minutes and are cleared during subsequent requests. Database retention runs automatically. The operator handles deletion of notification emails and related mailbox copies separately under the same retention policy, including deletion requests.
- Original uploads and page images: workspace admins can turn on automatic deletion of original uploads and page images a set number of days after the last upload in a batch (30 days unless the admin chooses another period). Until it is turned on, originals are kept until you delete them or ask us to. Deleted uploads and page images remain recoverable by the storage provider for 7 days under its soft-delete policy.
- Results: extracted values, evidence, model responses, review decisions, comparisons and exported reports stay until the workspace is deleted or you ask us to delete them. Exported reports keep working after the original files are deleted.
- Records of past activity: credit history and activity records keep the email address of the person who acted, including members who have since been removed.
- Backups: database backups are retained for at least 14 days before they become eligible for lifecycle deletion. Deleted backup objects have an additional 7-day soft-delete recovery period; versioning and asynchronous lifecycle processing can retain backup data longer than 21 days.
There is no self-service delete button for accounts or workspaces. To ask us to delete an account, a workspace or specific content, email support@linerecon.com.
Security
- Uploaded files are kept in private storage.
- Your browser uploads files through short-lived upload links that cannot overwrite existing files.
- Session tokens and sign-in codes are stored only as hashes in our authentication database.
- The app requires HTTPS, and access to servers and storage is restricted.
- The app and the database migrations use separate database roles with different permissions.
- Database backups use the minimum retention and provider recovery windows described above.
No system is perfectly secure. If you think your account has been misused, contact us.
Website measurement
We count page views, demo step views, demo tab clicks and pauses, sign-up button clicks, guide link clicks, checklist downloads, and contact form starts and submission outcomes in aggregate. Guide counts use a fixed page label, not a full URL or search query. These first-party counts do not include your email, company name, or requirement text, and do not use a visitor identifier or tracking cookie. Counts are not unique visitor numbers. Preview interactions are excluded.
We also use Google Analytics 4 to measure page views on the public website and app. On the public site, it also measures enabled interactions such as scrolling and outbound-link clicks, and where visits come from. The Google tag may use cookies and collect information about your browser, device, and visit. Google processes this information under its Privacy Policy. We do not send the information entered in the request form to Google Analytics. App page-view events use route labels in place of workspace, batch and other record IDs, exclude URL queries and fragments, and use a fixed page title. We do not send account details, document contents or reconciliation values in these events. Local development, app test builds and unpublished marketing previews do not load the Google tag.
We also use Plausible Analytics to count page views on the public website and app. Plausible does not use cookies or a persistent visitor identifier, and reports only aggregate visit statistics. In the app it receives the same route labels as Google Analytics, never record IDs, URL queries or fragments. Unpublished marketing previews and app test builds do not load Plausible.
We also use Microsoft Clarity to understand how people navigate the website and app through heatmaps and session recordings. Clarity may use cookies and collect browser, device and interaction data. The app's page content is marked for masking in Clarity recordings. Microsoft processes this information under itsPrivacy Statement. Local development and unpublished marketing previews do not load Clarity.
Your choices and requests
Email support@linerecon.com to ask for a copy of your personal information, to correct it, or to delete it. Workspace admins can remove members and turn on automatic deletion of original uploads. If your information is part of a workspace someone else administers, we may ask that workspace's admins before acting on the request.
Children
LineRecon is for business use by people 18 or older. It is not directed at children, and we do not knowingly collect children's personal information.
Changes to this policy
We may update this policy. When we do, we change the date at the top of this page. If a change is material, we will email workspace admins before it takes effect.
Contact
Questions or requests about privacy: support@linerecon.com.