1. Introduction and scope
Layrin is operated by Priova Intelligence, a sole proprietorship registered in Québec, Canada (“Priova Intelligence,” “Layrin,” “we,” “us,” or “our”).
This Privacy Policy explains how we collect, use, disclose, retain, and protect information when you use the Layrin desktop application, layrin.com, the account dashboard, licensing services, managed AI workflow, billing flows, and support channels.
Layrin is designed for professional use by adults. It is a local-first privacy layer before cloud AI, not a general chatbot or document repository.
2. About Priova Intelligence and Layrin
Priova Intelligence operates Layrin from Québec, Canada. The full public business identity for the operator is set out in the Terms of Service.
Layrin helps users protect sensitive professional text locally—from short messages and emails to longer reports and other pasted professional content—review the protected version, use AI on the protected version when they choose, and restore final responses locally on their device.
3. The Layrin privacy model
Layrin separates three categories of information: original/local content, reviewed protected content used for the managed AI workflow, and account, billing, licence, and aggregate usage data.
Original pasted text, original names and confidential values, token-to-original mappings, the local token vault, restored AI responses, local review and manual-hide decisions, and local corrections applied before a cloud send remain on your device and are not stored in Priova Intelligence’s account database.
For Layrin Pro, after protection occurs locally and you review the protected content, the protected context and protected instruction are transmitted through Priova Intelligence’s authenticated managed AI service to the AI provider. Priova processes this protected content and the tokenized response only temporarily to provide the Pro feature. Priova does not receive the original text or the local token mappings, and does not log or persistently retain the managed-AI content payloads. The restored response is created on your device.
Layrin Protect does not include Layrin-managed AI. Protect users keep their own direct/user-supplied AI path after local protection and review.
4. Information we collect
We collect limited information needed to operate accounts, access, billing, and support:
- Account information, including name or display name, email address, authentication and verification status, account identifiers, and account creation/update timestamps.
- Licence and desktop access information, including hashed licence records, hashed desktop session identifiers, entitlement status, activation, expiry, revocation, and last-seen timestamps, and application version where operationally necessary.
- Subscription and billing information, including Stripe customer identifiers, subscription status, plan, trial dates, renewal status, invoices, transaction metadata, payment/refund/dispute status, billing country, postal code, tax information, and other billing data supplied by Stripe.
- Safe aggregate usage information, including request count, token count where applicable, entitlement status, and quota status. Usage counters do not include prompts, original text, protected text, AI responses, or token mappings.
- Support communications, including email address, messages, attachments intentionally supplied to support, and correspondence history.
- Technical and security information, including IP address and request metadata generated by hosting, authentication, fraud-prevention, or security systems, browser/device information for the website, timestamps, error events, and security events.
5. Information processed locally by the desktop application
The Layrin desktop application performs the protect, review, manual-hide, token-vault, and restore workflow locally. Original text and token mappings are not sent to Priova Intelligence’s account database.
Online account deletion does not automatically erase local desktop data that already exists on your device. Removing local application data is controlled by the device and application environment. If you need help clearing local Layrin data, contact us at privacy@priova.io.
6. Managed AI workflow and OpenAI
Layrin Pro includes Layrin-managed AI. After local protection and your review, the protected context and protected instruction transit through Priova Intelligence’s authenticated managed AI service to OpenAI (or another provider configured for the applicable plan). Priova temporarily processes those protected payloads and the tokenized AI response only to provide the service, then returns the tokenized response to the desktop application. Priova does not receive original values or local token mappings and does not log or persistently retain managed-AI content payloads.
OpenAI processes information under its own business/API terms and privacy documentation. OpenAI states that API inputs and outputs are not used to train OpenAI models by default unless the API customer explicitly opts in. See OpenAI data-use documentation.
Customer-managed or enterprise-controlled AI endpoints are not part of the current individual Protect or Pro plans and remain deferred until after the beta.
7. Account, licence, and usage information
Layrin account and licence systems use minimal records to authenticate users, issue and manage licences, verify desktop entitlement, and enforce plan limits. Server-side licence and desktop session records store hashes, not plaintext licence keys or desktop session tokens.
Aggregate usage counters record monthly request and token totals where applicable. They are designed for entitlement, quota, billing support, and operational reliability, not for storing the content of your private text.
8. Payments and Stripe
We use Stripe to process trial enrolment, subscription payments, invoices, refunds, and related billing operations. Payment card information is collected and processed by Stripe. Priova Intelligence does not store complete payment card numbers on its own systems.
Layrin may offer a 7-day free trial or private-access period. A payment card is required when the trial begins; no subscription charge is made during the trial; monthly billing begins on day 8 unless cancelled. Cancellation stops future renewals, and access continues until the end of the current trial or paid billing period. We do not provide prorated refunds except where required by law or for confirmed duplicate charges or billing errors.
Stripe may process name, email, billing address, payment-method information, transaction amount, subscription and trial status, tax information, invoices, refunds, disputes, and fraud/risk signals. See Stripe Privacy Policy.
9. Website analytics and advertising technologies
The public marketing site and conversion pages may use Google Analytics, Meta Pixel, and TikTok Pixel after consent. These tools are not used inside the Layrin desktop application or in any user interface that displays or processes original text, protected text, prompts, AI responses, token mappings, or local vault data.
These tools may collect page views, referral source, campaign identifiers, approximate location derived from IP address, browser/device information, interactions with marketing pages, conversion events, and cookie or advertising identifiers where consented.
Advanced matching is disabled at launch. We do not send user-entered text fields as analytics event parameters, and we do not transmit sensitive document or desktop-app content to advertising platforms. Non-essential analytics and advertising technologies require consent before activation, and you can reject them.
10. How we use information
We use information to:
- create and manage accounts and authenticate users;
- issue and manage licences and verify subscription or entitlement status;
- provide the managed AI workflow and return protected responses to the desktop app;
- process payments, trials, invoices, refunds, and billing support;
- measure aggregate usage and enforce plan limits;
- secure the service, detect abuse, prevent fraud, and troubleshoot reliability issues;
- respond to support requests and privacy inquiries;
- measure marketing campaigns after consent; and
- comply with legal, accounting, tax, dispute, and security obligations.
We improve reliability without using the content of your private text as an application database record or application log.
11. When information is disclosed
We disclose information only where needed to operate Layrin, complete the transaction or workflow you request, use service providers, comply with law, protect rights and safety, prevent abuse or fraud, or handle a business transfer such as a reorganization or sale.
We do not sell original desktop text, local token mappings, restored content, or local vault data. We do not send those local-only values to advertising platforms.
12. Service providers
We use service providers to operate Layrin. They process information for the purposes described below and under their own terms, contracts, privacy commitments, and legal obligations.
| Provider | Purpose | Information |
|---|---|---|
| Priova Intelligence / Layrin infrastructure | Service operation, authentication, licence management, entitlement, and managed AI routing. | Account, licence, entitlement, aggregate usage, and reviewed protected content in transit for the managed AI workflow. |
| Stripe | Trials, subscriptions, payment processing, invoices, refunds, fraud prevention, and billing. | Billing, payment, transaction, subscription, and tax information. |
| OpenAI | Generate AI responses in the managed workflow. | Reviewed protected context, protected instruction, and protected AI response. |
| Neon / Neon Auth | Authentication and database infrastructure. | Account authentication data and minimal Layrin-owned account, licence, session, entitlement, and aggregate usage records. |
| Vercel | Hosting of layrin.com and serverless API infrastructure. | Website/API requests and operational or security metadata; protected managed-AI content is processed in transit but must not be logged or stored by Layrin application code. |
| Website analytics and campaign measurement after consent. | Marketing-site usage, browser/device, campaign, cookie, and conversion data. | |
| Meta | Advertising measurement and campaign attribution after consent. | Marketing-site interaction, advertising identifiers, campaign, and conversion data. |
| TikTok | Advertising measurement and campaign attribution after consent. | Marketing-site interaction, advertising identifiers, campaign, and conversion data. |
| Transactional email provider | Account, authentication, billing, trial, security, and support emails. | Name, email address, message metadata, and message content. |
13. International processing and transfers
Priova Intelligence is based in Québec, Canada. Our service providers may process information in Canada, the United States, Europe, or other jurisdictions where they or their subprocessors operate.
When information is processed outside your province, state, or country, it may be subject to the laws of that jurisdiction. We use contractual, technical, and organizational safeguards appropriate to the service and information involved.
14. Retention and deletion
We retain information only as long as needed for the purposes described in this policy, unless a longer period is required for legal, tax, accounting, dispute, fraud, abuse, or security reasons.
| Information | Retention period | Notes |
|---|---|---|
| Active account records | While the account remains active. | Includes account identifiers, authentication status, licence and entitlement status. |
| Deleted account information | Deleted or de-identified within 30 days, except where legal retention applies. | Some billing, tax, fraud, dispute, security, or legal records may be retained as required. |
| Active sessions and access credentials | Revoked promptly after account deletion or a security action. | Plaintext licence keys and desktop session tokens are not stored server-side. |
| Security and operational logs | Up to 90 days unless longer retention is needed for abuse, fraud, or security investigation. | Application logs must not include protected request bodies, original text, token mappings, authorization headers, API keys, licence keys, or session tokens. |
| Aggregate usage counters | Up to 12 months. | Counters include request and token counts where applicable, not prompts or document text. |
| Support communications | Up to 24 months after the request is closed. | Includes messages and attachments intentionally supplied to support. |
| Invoices, transactions, tax, refunds, and disputes | Up to 6 years, or longer if required by law. | Managed with Stripe and retained for accounting, tax, dispute, and compliance purposes. |
| Original text, local token mappings, local vault, and restored content | Not stored by Priova Intelligence. | These remain on your device in the Layrin desktop workflow. |
| Managed AI request and response content | Not stored in Priova Intelligence’s application database or application logs after the request completes. | Protected content is processed in transit to complete the requested AI operation. |
15. Account deletion and local desktop data
Cancelling a subscription stops future renewals but does not, by itself, delete your Layrin account. Access continues until the end of the current trial or paid billing period unless the account or entitlement is otherwise revoked.
You can request account deletion from the dashboard when that control is available or by contacting privacy@priova.io. We revoke eligible sessions and access credentials and delete or de-identify eligible account information within 30 days. Account deletion does not remove records we must keep for tax, accounting, refunds, disputes, fraud prevention, security, or legal obligations.
Online account deletion does not automatically erase local Layrin data already stored on your device, including local vault or token mapping data. You are responsible for managing local files and app data on your device.
16. Security safeguards
We use technical and organizational safeguards designed to protect Layrin accounts, licence systems, API routes, and operational infrastructure. These include local-first processing for the desktop workflow, authenticated API access, server-side entitlement checks, hashed licence and session records, limits on request payloads, safe error messages, and application logging rules that prohibit sensitive request bodies and secret headers.
No system is risk-free. Layrin reduces exposure by protecting text before cloud use and keeping restore mappings local, but you should still review protected text before sending.
17. Privacy choices and rights
Depending on where you live and the information involved, you may have rights to access, correct, delete, or receive information about how your personal information has been used or disclosed. You may also withdraw consent for optional processing such as non-essential analytics or request help with account deletion.
We may need to verify your identity before responding. To make a privacy request, contact privacy@priova.io. Québec residents may also contact or file a complaint with the Commission d’accès à l’information du Québec.
18. Children and age requirements
Layrin is intended for professional use by adults who are at least 18 years old. We do not knowingly collect personal information from children.
19. Third-party services and links
Layrin and layrin.com may link to third-party websites or services, including Stripe, OpenAI, account authentication services, and external support resources. Their privacy practices are governed by their own policies. Review those policies before providing information to them directly.
20. Changes to this policy
We may update this Privacy Policy as Layrin evolves, service providers change, or legal requirements change. The effective date and last-updated date show when this version applies. If changes are material, we will provide notice appropriate to the change and the information involved.
21. Contact and privacy requests
Privacy questions and requests should be sent to:
Privacy OfficerPriova Intelligence
privacy@priova.io
877-240-2233