Privacy Policy

1. Introduction

LayerV, Inc. (“LayerV,” “we,” “us,” or “our”) respects your privacy and is committed to protecting your personal data. This privacy policy explains how we collect, use, disclose, and safeguard your information when you visit our website or use our services, including the LayerV Discord Bot, the LayerV Slack Bot, any other LayerV bot or integration offered through a third-party communication platform (the “Bot”), the LayerV API and developer offerings, the qURL Desktop application, the qURL command-line tool (CLI), the qURL mobile apps for iOS and Android, the qURL Connector, the qURL MCP server, the qurl.link website, and the qurl.site addresses through which shared apps, files, and services are reached.

This policy also covers people who do not have a LayerV account, including people who publish with qURL without an account and people who open or request access to something shared through qURL (“Recipients”). When you open something shared through qURL, the app, file, or service you reach is run by the person who shared it (the “Publisher”), not by LayerV. What the Publisher's app collects from you is governed by the Publisher's own practices, not this policy.

LayerV, Inc. is a Delaware corporation. For privacy inquiries, contact us at privacy@layerv.ai.

2. Information We Collect

Information You Provide

• Contact Information. Name, email address, phone number, organization, and job title when you apply for early access or contact us.
• Identity Provider. Which identity provider your organization uses (e.g., Okta, Microsoft Entra ID).
• Use Case Information. Description of your intended use of our services.
• Communications. Records of correspondence when you contact us.
• Developer Information. Information you provide when registering for an API key or developer account.
• Account and Survey Information. Your email address and sign-in method when you create a LayerV account, and, if you answer them, sign-up questions such as how you heard about us and your email preferences.
• Billing Information. If you purchase a paid plan, your billing details and payment status. Payment card details are collected and processed by our payment processor (see Section 4); LayerV does not store full card numbers.

Information Collected Automatically

• Log Data. IP address, browser type, pages visited, referring URL, and access times.
• Device Information. Device type, operating system, and browser version.

For our own website analytics, we do not use advertising cookies, cross-site tracking, or third-party analytics services. Embedded YouTube videos are described below. Beyond the first-party analytics described below, we keep server and content-delivery logs for security and operations. These include records of requests from automated clients such as AI crawlers and agents, which may include the requesting IP address (shortened where it may belong to an individual). Our website and dashboard also use your browser's local and session storage for things like remembering your sign-in method, display settings, and the campaign that brought you to the site; our sign-in provider may set cookies needed to keep you signed in.

Anonymous Page Analytics

We collect anonymous, cookieless page analytics to understand how visitors use our website. This includes pages visited, referrer domain, UTM campaign parameters, device type, browser family, scroll depth, and time on page. This data is collected by our own first-party service with no cookies, no personally identifiable information, no fingerprinting, and no third-party analytics services. We honor the Do Not Track (DNT) and Global Privacy Control (GPC) browser signals and skip collection for users who enable either one. We also record when visitors click certain buttons or complete actions such as copying a setup command, without identifying the visitor.

Embedded YouTube Videos

Our founder film uses YouTube's privacy-enhanced player. When the video scrolls into view, it loads and plays muted on a loop. If your browser requests reduced motion, playback starts only when you choose to watch. You can use the player controls to pause or turn on sound. The preview image is served by LayerV. Loading and playing the video connects your browser to YouTube/Google, which receives your IP address and may collect device information and playback activity under the Google Privacy Policy. This is separate from LayerV's first-party page analytics described above.

Information Collected Through the LayerV Bot

When you use the Bot, we collect the following categories of information:

• Platform Account Identifiers. Your user identifier and username on the underlying communication platform (such as your Discord user ID or your Slack member ID), and identifiers for the server, workspace, or channel in which the Bot is invoked. We receive this data directly from the underlying platform pursuant to that platform's developer terms.
• Bot Command Data. The commands you issue to the Bot, the timestamps of those commands, and any parameters submitted with them.
• qURL Token Metadata. For each qURL token generated through the Bot, we collect the token identifier, generation timestamp, expiration timestamp, configured access policy, and records of successful and unsuccessful access attempts.
• Content Submitted to the Bot. Any image, file, link, or other content you submit to the Bot for sharing or processing. Content is encrypted in transit and at rest. LayerV's architecture is designed so that LayerV does not hold or have routine operational access to the cryptographic credentials required to decrypt or view the unencrypted content. Content is stored on LayerV cloud infrastructure (currently Amazon Web Services) in the United States and is purged on an operational cadence determined by LayerV. See Section 27.7 of our Terms of Service for additional detail.
• Conversation Messages (Assistant and Agent Features). When you mention the Bot, message it directly, or enable its in-channel assistant in a channel it has been added to, the Bot receives the messages in that conversation in order to generate its responses. The Bot uses these messages solely to produce replies within that conversation and does not use them to build user profiles or for advertising. See Section 4 below for the third-party AI provider that processes this content.

Note on Third-Party Platform Storage. When you upload content to a Discord server, Slack workspace, or any other third-party communication platform on which the Bot operates, that platform also stores a copy of the content on its own infrastructure (for example, on Discord's content delivery network). LayerV does not control that storage, the URLs generated by the platform, or the access controls the platform applies. Platforms commonly process uploaded content in ways that are independent of LayerV, including but not limited to: serving content from their own content delivery networks under URLs the platform controls; caching attachments on the recipient's mobile device in operating-system attachment caches; transmitting attachment thumbnails through push-notification services (such as Apple Push Notification service or Firebase Cloud Messaging); generating link-unfurl preview images cached on third-party servers; and retaining content for periods determined by the platform's own retention policies, which may differ materially from LayerV's.

The encryption and architectural representations described above apply only to content stored on LayerV infrastructure, not to content stored or processed by the underlying communication platform. See Section 27.7A of our Terms of Service for additional detail, including the specific exposure scenarios described in that section.

• Operational Logs. Bot performance, error, and security logs, including the IP address from which Bot interactions originate where this information is available to us.

We do not request or collect platform email addresses, payment information, or any other sensitive personal data through the Bot beyond what is described above.

Data Received but Not Used. When you invoke the Bot, the communication platform includes incidental metadata with each request that the Bot does not use to provide any feature. On Slack, this includes the workspace name, channel name, and your display name sent alongside a slash command; these are used only as a transient security cross-check to prevent form-replay (for example, in the “/qurl feedback” form) and are then discarded. The Bot also receives routing and envelope metadata (such as event and view identifiers) that is not used for any feature and appears only in operational logs used for troubleshooting and abuse prevention. The Bot does not retrieve message history, enumerate workspace members, or access files beyond the content you explicitly submit to it.

Information Collected Through the LayerV API and Developer Offerings

When you use the LayerV API or developer offerings, we collect:

• API Key Identifiers and Usage Data. API key identifiers, request timestamps, endpoint usage patterns, rate limit data, and error logs.
• Source Identifiers. IP addresses and other technical identifiers from which API requests originate.
• Developer Account Information. Information you provided when registering as a developer.

Information Collected When You Publish or Share With qURL

When you publish or share with the qURL CLI, qURL Desktop, the qURL MCP server, an AI agent, or the qURL Connector, with or without a LayerV account, we collect:

• Machine Identity. When you first publish from a computer without an account, the qURL software creates an identity for that computer and sends LayerV its public key and identifiers. The private key stays on your computer.
• Share Details. For each address or link you create: identifiers, the label (which may be a file name or a local address such as http://localhost:3000), the access mode you choose, expiry and session settings, and whether the share is running.
• Publisher Details You Choose to Show. A publisher name, description, and any images or video you add. These are shown to Recipients. Publisher names are not verified unless LayerV marks them as verified.
• Verification Information. If you ask LayerV to verify you as a Publisher, the information and documents you give us for that purpose. We use them to decide on and maintain verification and to investigate abuse reports.
• Recipient Email Addresses You Provide. If you invite people by email, the addresses you (or your agent) enter. LayerV uses them to send the invitation and manage access.
• Access Decisions. Requests, approvals, denials, invitations, and revocations, with times.
• Connection Data. The IP address of the computer running the qURL software, connection times, and the amount of data carried.

Traffic you share. When a Recipient opens something you published, the connection passes through LayerV's network to reach your computer. LayerV is only the transit network for that connection. We process traffic transiently to carry it, including terminating TLS where needed to route it. LayerV infrastructure can access unencrypted traffic at those points, but we do not retain the content of relayed traffic. We keep the connection records described above. See Version 2.0, Section 29.5 of our Terms of Service.

Information About People Who Open Something Shared Through qURL

You do not need a LayerV account to open something shared through qURL. When you open a qURL link or visit a qurl.link or qurl.site address, we collect:

• Connection Data. Your IP address, browser type, the address or link you opened, times, and whether access was allowed. We use your public IP address to let your network reach what was shared for the length of the visit, so other devices on the same network address may also reach it during that visit.
• Information You Enter to Get Access. Depending on the access mode the Publisher chose: your email address and the confirmation that you control it, a name you type, and your agreement to share them with the Publisher.
• Passkey and Device Keys. If you set up a passkey or device key to get access, LayerV receives its public key and identifier. The private key stays on your device.
• Browser Storage and Cookies. The qurl.link page stores a hint about your passkey (its identifier and public key, not your name) in your browser's local storage, and device keys for each address in your browser's IndexedDB storage. The qurl.site address you are sent to sets a cookie to keep your visit open. The qurl.link page does not run analytics and uses no analytics or advertising cookies.

What the Publisher receives. Only when the access mode the Publisher chose uses your email address or a name (for example, an invitation or a request for access) and you agree, we give the Publisher your verified email address or the name you typed, plus the time of your request, so they can decide whether to let you in. In that case your access is not anonymous to the Publisher. Otherwise, for example when you open a one-time link, LayerV does not tell the Publisher who you are. The Publisher uses any information we give them under their own responsibility, not LayerV's. Whatever the access mode, the Publisher's own app can see anything you do or enter in it.

The qURL App. The qURL mobile apps for iOS and Android (the “App”) are for people 18 and older. You do not need an account to open public posts in the App. When you use the App:

• Opening Posts. We collect the connection data described above for each post you open. Opening a post is anonymous to its creator unless its access mode uses your email address (see “What the Publisher receives” above).
• Asking for a Private Post. You follow the post's access steps in the App, or on qurl.link for a step the App cannot do, and the information above applies. Depending on the access mode, the App sends us the email address you enter, which we confirm with a code we email to it and, with your agreement, give to the creator with your request; the identifier and public key of a passkey you create or use (the passkey itself stays in your password manager); and the public half of a key the App makes for that post on your phone. An invitation already carries the email address the creator chose.
• Information That Stays on Your Phone. Your Library, the creators you block, your App settings, the keys and progress of your private-post requests, and, if you are a creator, your sign-in are kept in the App on your phone.
• Delete My Data. “Delete my data” (Me > Settings) deletes what the App saved on your phone. When server deletion is available, it first asks you to remove from qURL the access to private posts you requested in the App and the email address you gave for it. If server deletion is unavailable or you choose to delete only the phone data, that access and email address stay with qURL until removed by the creator or LayerV. A creator keeps an email address they already received, and we keep records for security and abuse prevention as described in Section 5.
• Creators. If you sign in as a creator, we process your email address and sign-in information through Auth0 (see Section 4), and the App shows you the email addresses of people who ask for access to your posts so you can approve, deny, or revoke access. Where available, you can request account deletion in the App (Me > Settings > “Delete qURL account”) or by emailing privacy@layerv.ai.
• Reports. When you report a post in the App, we receive the post's address, the reason you choose, and any note you add, with the connection data described above. The report is not tied to your account.
• Push Notification Tokens. If you are a creator and turn on notifications, we keep a push token and a random install identifier for your phone and send notifications through Apple Push Notification service or Firebase Cloud Messaging.
• Scanning QR Codes. When you tap Scan, the App uses the camera on your phone only to read a qURL code. The camera images and the code stay on your phone. On Android, the code reader is Google's ML Kit, which sends Google device and app information, a per-installation identifier, and performance metrics for its own diagnostics.
• No Analytics or Crash SDKs. Apart from ML Kit's diagnostics on Android, the App does not include analytics, advertising, or crash-reporting software, and does not track you across other companies' apps or websites. Apple and Google may give us aggregate information through their app store consoles, as described in their own policies.

Demos and Events Published by LayerV

Some qURL links are published by LayerV itself, for example product demos we show at conferences and events. When you open one of these and enter your email address, LayerV is the Publisher, so your verified email address and the time you opened the demo come to LayerV. We tell you this before you enter your email.

• To give you access. We use your email address to verify it and let you into the demo.
• To follow up, only if you agree. If you tick the box to hear from LayerV, we may email you about LayerV products and news. You can unsubscribe at any time using the link in any email or by contacting privacy@layerv.ai. If you don't tick the box, we use your email address only for access, security, and the records described in Section 5.
• No sale, no marketing to the EEA or UK. We do not sell these email addresses, and we do not send marketing email to contacts we identify as located in the European Economic Area or the United Kingdom.

Information Collected Through qURL Desktop

qURL Desktop is a desktop application that shares files and local services from your own computer. The categories below describe the information that stays on your device and the information that is transmitted when you use it.

• Information That Stays on Your Device. The contents of your files are never read into any log or report. Operational logs produced by the qURL Connector (the background component of qURL Desktop that carries your shares), including local service addresses, shared-service hostnames, and route identifiers, are stored only on your device. They are rotated by size when the qURL Connector starts, and a log to which no new entries have been written for seven days is cleared or deleted automatically the next time the application starts. They are never transmitted to LayerV.
• Service Operation Data. When you create a share or sign in, qURL Desktop sends the request you make to the LayerV API: resource identifiers, expiration and access policy settings, session parameters, and the share's label. The label is set automatically unless you choose your own: for a file it is the file's name, and for a local service it is that service's local address (for example, http://localhost:3000/admin). It is stored with the share so you can recognize it in your dashboard. The folder paths where your files are stored are never sent. You may also add an optional description, which is stored with the resource. When sharing is set up on your computer, the application creates a short-lived, single-use setup credential whose name includes your computer's hostname, and the qURL Connector uses it to register the device with LayerV using a randomly generated device identifier, a public key, your computer's hostname, and the Connector's software version, which LayerV uses to route your shares. The qURL Connector stays connected to LayerV's Connector network, which receives your IP address. The contents of your files are never sent to the LayerV API; when someone opens a qURL for a shared file or service, its content is carried to them through LayerV's Connector network. Sign-in itself takes place in your web browser; see Section 4 below for the identity service that processes it.
• Automatic Update Checks. While it is running, the application checks layerv.ai (staging.layerv.ai for pre-release builds) for application updates shortly after it starts and about once an hour thereafter. These checks disclose your IP address and a user-agent string to LayerV and contain no identifier or other information about you or your use of the application. Updates are downloaded only when you choose to install them.
• Optional Anonymous Diagnostics. With your explicit opt-in consent (off by default, requested when a new installation is first launched, changeable at any time in the application's settings), qURL Desktop may send anonymous diagnostics: counts of actions (such as “a file share was created”), the application version and operating system, a timestamp rounded to the hour, and error reports limited to the type of error and a code location within the application. Diagnostics contain no identifier of any kind — no device, installation, or user identifier — and cannot be linked to your account. Error reports never include file names, folder paths, service addresses, or error message text. The application honors the “DO_NOT_TRACK” environment variable, which disables diagnostics regardless of the consent setting. As of the effective date of this policy, no diagnostics collection endpoint is active, and no diagnostics are transmitted.

3. How We Use Your Information

We use the information we collect to:

• Process your early access application and evaluate fit for our pilot program
• Communicate with you about our services, including scheduling demos and onboarding
• Respond to your inquiries and provide support
• Send account and security notices: security alerts (for example, a new sign-in or a new API key), billing notices, and service changes such as deprecations, breaking changes, significant disruptions, and planned maintenance. These go to the account holders they concern for as long as the account exists.
• Send Product updates and Announcements and promotions (events, offers, and other news), only while you have these turned on. New accounts start with both on, and you can turn either off at any time in your account's email preferences or with the unsubscribe link in those emails.
• Maintain security and prevent fraud
• Comply with legal obligations

For information collected through the Bot, the API, qURL Desktop, and qURL sharing (including information about Recipients), we additionally use it to:

• Operate the relevant service, process your commands or API requests, and generate and validate qURL tokens
• Enforce rate limits and detect abusive usage patterns
• Carry connections to Publishers' computers, apply the access mode each Publisher chose, send invitation and verification emails, and give Publishers the information described in Section 2
• Investigate reports of phishing, malware, impersonation, and other abuse, and block or disable abusive addresses, links, machines, and network addresses
• Detect, investigate, and prevent abuse, fraud, infringement, illegal activity, and security incidents
• Enforce our Terms of Service
• Comply with legal process, court orders, and regulatory or law enforcement requests
• Report suspected child sexual abuse material to the National Center for Missing & Exploited Children as required by 18 U.S.C. § 2258A
• Respond to DMCA notices and other intellectual property complaints
• Respond to valid TAKE IT DOWN Act removal requests and state law analogs regarding non-consensual intimate imagery

4. Service Providers and Data Processing

We do not sell your personal information. We share data with the Publishers you choose to request access from (as described in Section 2) and with service providers necessary to operate our business:

• Amazon Web Services (AWS). Cloud infrastructure hosting, including delivery of qURL Desktop downloads and updates. Data is stored in AWS US regions. AWS maintains its own security certifications, including SOC 2, ISO 27001, and FedRAMP.
• Email Services (including Resend). Transactional email delivery for application confirmations and communications, account and security notices, qURL invitation and verification emails, and delivery of product update and marketing emails, including subscription and unsubscribe management. Our email provider keeps a list of addresses that bounced or reported our email as spam and does not send to them.
• Discord, Inc. Communications layer through which the Discord Bot operates. LayerV is not affiliated with Discord, and Discord's collection and use of your information is governed by Discord's own Privacy Policy.
• Slack Technologies, LLC (a Salesforce company). Communications layer through which the Slack Bot operates. LayerV is not affiliated with Slack, and Slack's collection and use of your information is governed by Slack's own Privacy Policy.
• Anthropic, PBC. When you use the Bot's assistant or agent features, the content of the relevant conversation is sent to Anthropic's API to generate the assistant's responses (currently the Claude model family). LayerV is not affiliated with Anthropic, and Anthropic's processing of that content is governed by Anthropic's commercial terms and privacy policy. Under those commercial terms, content submitted through the API is not used to train Anthropic's models.
• Okta, Inc. (Auth0). Sign-in for LayerV services, including qURL Desktop, is processed by the Auth0 identity platform operating under LayerV's domain. Auth0 processes your email address, authentication credentials, and IP address to authenticate you. LayerV is not affiliated with Okta, and Okta's processing is governed by Okta's own Privacy Policy.
• Apple Inc. and Google LLC (the qURL App). Distribution of the qURL App through the App Store and Google Play, delivery of App notifications through Apple Push Notification service and Firebase Cloud Messaging, and, on Android, Google's ML Kit code reader. Their processing is governed by their own privacy policies.
• Google LLC. If you choose to sign in with Google, Google shares your name, email address, and profile image with LayerV through Auth0. Google's processing is governed by Google's own Privacy Policy.
• Stripe, Inc. If you purchase a paid plan, Stripe processes your payment and billing details. Stripe's processing is governed by Stripe's own Privacy Policy.

We may also disclose information:

• When required by law, subpoena, or legal process
• To protect our rights, privacy, safety, or property
• To enforce our Terms of Service
• To report suspected illegal activity to the appropriate authorities
• To law enforcement, the National Center for Missing & Exploited Children, or other appropriate parties when we believe in good faith that it is necessary to prevent death or serious physical injury, to protect a child, or to respond to an emergency
• In connection with a merger, acquisition, or sale of assets (with notice to affected users)

5. Data Retention

LayerV retains personal information for the period necessary to fulfill the purposes described in this policy, including providing our services, complying with legal obligations, resolving disputes, enforcing our agreements, and supporting business continuity. Specific retention periods are operational and may change over time based on legitimate business need, security, regulatory requirements, and applicable law.

Information collected through the Bot is retained only as long as needed to operate the service. qURL token metadata is retained for the lifecycle of the token plus a limited period afterward to support security, abuse prevention, and audit. Content submitted through the Bot is encrypted and purged on an operational cadence tied to token expiration, as described in Section 27.7 of our Terms of Service; LayerV does not retain Bot content longer than necessary for these purposes.

qURL Desktop stores its operational logs only on your device, where they are rotated and cleared or deleted as described in Section 2; LayerV does not receive or retain them. Information that qURL Desktop sends to the LayerV API is retained on the same basis as other API data: qURL token metadata for the lifecycle of the token plus a limited period afterward to support security, abuse prevention, and audit. Records of the setup credential and the Connector device registration, including your computer's hostname, are retained to operate your shares and support security, abuse prevention, and audit. Setup-credential retention is based on when the credential is used, expires, or is revoked, plus a 30-day security and audit period. Device-registration records become eligible for deletion after 90 days without activity. Deletion occurs through automatic database cleanup.

Records about qURL sharing, including share details, access decisions, Recipient email addresses provided under an access mode, and connection data, are retained while the share exists and for a limited period afterward to support security, abuse prevention, and audit. Relayed traffic is not retained (see Section 2). Information in your browser's storage stays on your device until you clear it. Push tokens and reports made in the qURL App are retained for as long as needed to deliver notifications and handle the report, and for a limited period afterward for security and abuse prevention.

Files uploaded through LayerV browser extensions are subject to the retention practices described in the applicable extension privacy policy. For the qURL Gmail extension, see the qURL Gmail Extension Privacy Policy.

CSAM reports and related records are retained as required by 18 U.S.C. § 2258A and applicable law. DMCA notices and counter notices may be retained for the period required to support enforcement of LayerV's repeat infringer policy.

You may request deletion of your data at any time by emailing privacy@layerv.ai. For qURL accounts, see Delete your qURL account. We will honor deletion requests except where retention is required by law, necessary to resolve disputes, or necessary to protect LayerV's rights or the rights of third parties.

6. Data Security

We implement technical and organizational security measures including:

• Encryption in transit and at rest
• Access controls and authentication requirements for personnel
• Regular security assessments
• Incident response procedures
• Time-limited, revocable qURL access controls

Content submitted through the Bot is encrypted such that LayerV does not hold or have routine operational access to the cryptographic credentials required to decrypt or view the unencrypted content. See Section 27.7 of the Terms of Service for additional detail.

No method of transmission over the internet is 100% secure. If you believe your data has been compromised, contact us at security@layerv.ai.

7. Your Privacy Rights

All Users

You have the right to:

• Request access to your personal information
• Request correction of inaccurate data
• Request deletion of your data
• Request a portable copy of the personal information you have provided to us
• Opt out of marketing communications, using the unsubscribe link in any marketing email, your account's email preferences, or by contacting info@layerv.ai. Account and security notices are part of the service and continue while you have an account.

If you are a Recipient and want a Publisher to delete information LayerV gave them, ask the Publisher directly. To exercise your rights over information LayerV holds about you, contact privacy@layerv.ai.

California Residents (CCPA/CPRA)

If you are a California resident, you additionally have the right to:

• Know what personal information we collect, use, and disclose
• Request deletion of your personal information
• Opt out of the sale or sharing of personal information (we do not sell or share your data)
• Non-discrimination for exercising your privacy rights

Other U.S. State Privacy Laws

If you are a resident of any U.S. state with applicable consumer privacy legislation (such as Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, Tennessee, Iowa, Indiana, New Jersey, Delaware, New Hampshire, Maryland, Minnesota, Nebraska, or Rhode Island), you may have rights similar to those described above. To exercise rights under any such law, contact us at privacy@layerv.ai.

European Users (GDPR)

LayerV, Inc. is a U.S.-based company. LayerV currently focuses on customers in the United States and does not actively market its services to individuals or organizations in the European Economic Area or the United Kingdom, and does not send marketing email to contacts we identify as located there. If you are located in the EEA or UK and use our services, your data will be transferred to and processed in the United States.

EU and UK organizations that wish to use LayerV services and require a Data Processing Agreement, Standard Contractual Clauses for cross-border transfers, or other GDPR-aligned arrangements should contact us at info@layerv.ai before integrating. We will respond to data subject requests as required by applicable law.

Response Time

We respond to privacy requests within the time frame required by applicable law. To submit a request, email privacy@layerv.ai.

8. Children's Privacy

Enterprise Services. Our enterprise services are intended for business use and are not directed at individuals under the age of eighteen.

The qURL App. The qURL App is for people 18 and older. Contact us at privacy@layerv.ai if you believe a person under 18 has used it.

The Bot. The Bot is available to users who meet the minimum age requirements of the underlying communication platform (for example, Discord's general minimum age, or Slack's eligibility rules and any age requirements imposed by the workspace administrator). The age requirements applicable to your use are set by that platform, not by LayerV.

Hard Floor. Regardless of the underlying platform's age policy, we do not knowingly collect personal information from any individual under the age of thirteen in the United States, or under the applicable age of digital consent in any other jurisdiction. If we learn that we have inadvertently collected personal information from a child under the applicable age, we will delete that information as soon as reasonably possible.

If you are a parent or legal guardian and you believe we have collected personal information from your child, please contact us immediately at privacy@layerv.ai and we will delete it.

CSAM Reporting. If LayerV becomes aware of any content that may constitute child sexual abuse material, LayerV will report that content to the National Center for Missing & Exploited Children (NCMEC) in compliance with 18 U.S.C. § 2258A and will preserve and disclose related records to law enforcement as required by law. Because LayerV's architecture does not provide LayerV with routine operational access to the unencrypted content of communications transmitted through the Bot, traditional content scanning is not available to LayerV; see Section 27.13 of the Terms of Service for additional detail.

9. International Data Transfers

Your information is processed and stored in the United States. By using our services, you consent to the transfer of your data to the U.S. We use AWS infrastructure to protect data in transit and at rest.

10. Changes to This Policy

We may update this privacy policy to reflect changes in our practices or legal requirements. Material changes will be communicated by:

• Posting the updated policy with a new effective date
• Email notification to users who have provided contact information

We encourage you to review this policy periodically.

11. Browser Extensions

LayerV publishes browser extensions that interact with third-party applications (currently the qURL Gmail extension). Each LayerV browser extension has its own dedicated privacy policy describing the data processed by that extension. For the qURL Gmail extension, see the qURL Gmail Extension Privacy Policy. For matters specific to a given extension, that extension's policy controls; this Privacy Policy controls for all other LayerV services.

12. Contact Us

For questions about this privacy policy or to exercise your privacy rights: