Privacy Policy

Company and contact

Lanyrde is operated by Lanyrde LLC, a Virginia limited liability company. To ask about your information or make an access or deletion request, email lanyrde@polsia.app.

Information handled by Lanyrde

• Account and sign-in information: the name, email address, and password credential provided for an account, along with account and session records used to sign in.
• Workspace and roster information: the company name, vendor names and roster entries, requirements, vendor status, and related workspace records. A vendor record may include contact details, a website, and notes when a customer supplies them.
• Certificates and related records: uploaded certificate files and file details, extracted coverage lines and limits, endorsement wording, effective and expiration dates, additional-insured wording, review and assessment details, and renewal reminder history.
• Billing and quote information: the account email used for checkout, the quoted roster count and monthly amount, selected plan information, checkout identifiers, and subscription status and billing period details. Stripe-hosted checkout handles payment entry. The app’s database models do not contain a payment-card number field.
• Messages and support submissions: if a customer sends an inquiry or feedback, the app can store the name, email, and message. Feedback submissions can also include file attachments.

How information is used

• To create accounts, authenticate users, and provide workspace access.
• To organize customer workspaces, vendor rosters, requirements, certificate files, extracted certificate details, expiration dates, and follow-up records.
• To analyze certificate pages, compare saved details with customer-entered requirements, and display information for customer review. The system does not determine whether insurance coverage is in force.
• To prepare roster-based monthly quotes, create checkout sessions, confirm subscription status, and decide whether a workspace feature is available.
• To send account, onboarding, certificate-upload, and renewal-related emails when the relevant feature is used or enabled, and to respond to inquiries or feedback.
• To measure page visits and signup or purchase events as described below.

Services that receive information

• Stripe: Lanyrde sends the account email, monthly amount, and plan and roster identifiers through Polsia’s payments API to create a Stripe-hosted checkout. Stripe processes payment information entered in that checkout and subscription billing.
• Polsia application hosting and database: the app runs on Polsia’s platform and uses its provisioned PostgreSQL database for account, workspace, vendor, certificate, and billing-status records. The app’s deployment configuration does not identify the underlying hosting or database infrastructure operator.
• Polsia R2 file proxy: uploaded rosters, certificates, and related files are sent through Polsia’s R2 proxy for storage and retrieval. The app code identifies the R2 proxy but not a separate underlying storage operator.
• Polsia email proxy: the recipient, subject, and message content for transactional and vendor reminder emails are sent through this service. The app code does not identify the email delivery provider behind the proxy.
• Polsia AI proxy: certificate page images are sent with extraction instructions to read certificate details. The app code does not identify the upstream model or provider.
• Meta Pixel: the browser pixel records PageView, Lead, and Purchase events; Purchase events include a value and USD currency. The app code does not establish what additional information Meta may receive or infer through its browser pixel.
• Polsia analytics beacon, when enabled: when the deployment supplies its analytics setting, the app sends an app identifier and a random browser visitor identifier to Polsia’s beacon on page loads. Without that setting, the beacon component is not rendered.

Retention and cleanup

Some quote and upload-support records are temporary. A roster quote snapshot expires after two hours initially; when connected to checkout, its expiry is extended to seven days. Pricing cleanup removes eligible expired snapshots during later pricing activity. Quote-stage certificate review records have a 30-day review window, after which the cleanup code removes their snapshot and associated stored files. Pending upload authorization records that have not been registered are removed after 24 hours when a later upload authorization is created. These are code-triggered cleanup operations, not exact deletion-time guarantees.

Account, workspace, vendor, requirements, and customer certificate records do not have a general automatic deletion period in the app code. Removing a vendor can leave a record marked as removed. The app has a specific certificate undo action that deletes a certificate database record, but the code does not show a general account or workspace deletion flow or an automatic cleanup schedule for customer certificate files. The signup-prefill token stops working after seven days or once used, but the code does not show cleanup of expired token records. Session records have expiration timestamps; the cleanup of expired session records and the retention and deletion behavior of backups are not established by the app code.

You may email lanyrde@polsia.app to request access to or deletion of your information. The app does not contain an account-wide request workflow, so how a request is handled, whether all information can be deleted, and any response time cannot be confirmed here.