PAYESCROW.CO

PAYESCROW.CO

Privacy policy

How account information, purchase records and document submissions are handled. This draft awaits business approval and professional review.

Scope and responsible business

PAYESCROW.CO is the product brand. The legal controller and privacy contact have not yet been confirmed. This draft does not assert that any particular privacy law applies or certify compliance.

Account and session information

PAYESCROW uses Lovable Cloud for authentication, database and private storage. Account email, profile names and workspace preference support sign-in and account operation. Essential login storage keeps you signed in. Temporary browser session storage remembers your chosen return page and account-form details during onboarding, then expires or clears them. Google sign-in, when used, involves Google and the authentication service. Remote Google Fonts requests share normal request information with Google.

Orders, media and review information

Saved orders include buyer contact, merchant details, items, quantities, prices, terms and optional private billing/delivery information. Product/evidence media and tracking support the order record. Identity photos, selfie, review status, customer-visible reasons, private reviewer notes and access/audit events support human document review.

Purpose and access

The proposed purposes are account administration, order fulfilment records, document review, support and abuse investigation. Buyers access their linked records; merchants access their organisation’s orders but not identity photos or private review notes. Authorised reviewers access document submissions for human decisions. Privileged operational access is limited by application permissions.

Manual review, not biometric automation

The current workflow stores identity photographs and a selfie. It does not generate biometric templates or perform automated facial matching/liveness. A human decision is not provider-verified KYC and does not activate payments.

Visitor analytics

According to Lovable’s analytics documentation and privacy policy, visitor analytics provides aggregate traffic, pages, referrers, country, browser, operating system, device, duration, performance and error information. Lovable says this analytics service does not use cookies or browser storage and does not build cross-visit profiles. It describes retention of detailed data for 90 days, and per-visit summaries and daily totals for one year. Click and app-event collection depends on settings and consent; Lovable says Global Privacy Control (GPC) prevents click/event collection. These are the provider’s descriptions, not a guarantee that all information processed by this site is anonymous. Essential login and temporary onboarding storage are separate from visitor analytics.

Lovable analytics documentationLovable’s privacy policy

Service providers and disclosures

Lovable Cloud processes the account/database/storage information needed to operate the workspace; Google processes sign-in/font requests when those features are used. Necessary merchant access is limited to order information. Exact processor contractual details, hosting countries, backup arrangements and legally required disclosures need confirmation before this notice is finalised.

Retention and deletion limits

Identity photos are held privately for document review. The final retention and deletion schedule, including abandoned drafts, backups and order/review records, is awaiting confirmation. Current deletion timing is not guaranteed. Some records may need to be retained for legal obligations or to document a purchase or review decision.

Requests and corrections

Where applicable law provides rights, individuals may request access, correction or deletion and ask about processing. A privacy request contact and identity-check process must be confirmed before this policy takes effect. Order snapshots cannot be silently edited: corrections require a replacement record. This draft does not promise unlimited deletion or a response deadline.

Review before publication

Confirm the following once, then obtain appropriate professional review.

  • Legal entity, trading name and registration address.
  • Owned support, privacy and complaints contacts.
  • Markets, providers, custody arrangement and any required authorisations.
  • Processor locations, backup and audit retention, and final deletion policy.
  • Approved pricing, release, cancellation, refund and dispute terms.
  • Confirm click/event collection and any consent configuration before publication.