Privacy Policy
Lahyer, a product of Pryme Labs
Last updated:
This Privacy Policy applies to Pryme Labs LLC (“Pryme Labs,” “we,” “us,” or “our”) and explains how and why we access, collect, store, use, and otherwise process personal information when you use Lahyer, which is a product of Pryme Labs (the “Services”), including when you visit https://lahyer.com, create an account, connect a repository, build or deploy an application, use Lahyer Studio or another AI feature, manage a domain or database, or contact support.
Lahyer is an AI-powered cloud for building and launching applications. Developers can create applications with Lahyer Studio, deploy code from a connected GitHub, GitLab, Bitbucket, or other supported repository, or use the command line, and host applications on Lahyer. The Services may also include managed PostgreSQL databases, domains and HTTPS, deployment and build logs, and AI assistance for development and troubleshooting. Features may change over time.
When this Policy refers to personal information, personal data, or information, it means information that identifies or can reasonably be linked to an individual, as defined by the privacy law that applies. Some project information may not be personal information by itself, but may include personal information depending on what you or your organization puts into the service.
1. Who we are and when this notice applies
Lahyer, which is a product of Pryme Labs, is covered by this Policy. This Policy covers our website, accounts, workspaces, builds, billing and support interactions, and our processing of project or application content as described below. It applies to visitors, individual developers, team members, customers, and people who contact us.
If you use Lahyer through an employer, client, school, or other organization, that organization may control the workspace and decide why certain information is processed. Its privacy notice and instructions may also apply. For questions about data held inside an organization’s workspace, contact that organization first.
2. Our role: controller or processor
Pryme Labs generally acts as a controller (or equivalent business) for information it uses to operate its own business, including account registration, billing contacts, website measurement, service security, and support. We decide why and how that information is used, subject to applicable law.
When an organization uses Lahyer to connect repositories, build or host applications, or process information through a workspace, database, or project, that organization generally decides what information is submitted and for what purpose. In those cases, Pryme Labs generally acts as a service provider or processor and handles the information to provide Lahyer under that organization’s instructions and our agreement. Where required, a data processing agreement applies. If your request concerns information controlled by an organization, we may refer you to that organization or assist it in responding.
The actual role depends on the use case and applicable law. This description does not replace a signed data processing agreement or other customer contract.
3. Information we handle
The information we handle depends on the Services and features you use, the permissions you grant, and the content you or your organization choose to submit. It may include:
- Account and workspace information, such as your name, email address, authentication records, team or organization name, role, preferences, and account settings.
- Repository and project information, such as the account and permission details needed to connect GitHub, GitLab, Bitbucket, or another supported provider; repository names and content; commits, branches, configuration, build settings, deployment activity, and project identifiers.
- Application and infrastructure information, such as files and configuration needed to build and host an application, deployment and runtime logs, domain and DNS settings, database configuration, and information stored in or transmitted through a Lahyer-managed service. What an app collects from its end users depends on how you build and configure it.
- AI feature inputs and outputs, such as prompts, app descriptions, code or project context you provide or authorize the feature to inspect, generated code or content, and relevant logs or build evidence used to answer your request.
- Device, usage, and security information, such as IP address, browser and device details, timestamps, pages and features used, diagnostic events, performance information, and signals used to detect abuse, protect accounts, and maintain reliability.
- Payment and subscription information, such as the plan, amount, currency, payment status, invoice or receipt details, and transaction reference. Payment-card, bank, or wallet credentials are handled by the payment provider or financial institution shown at checkout; we receive payment results and limited billing information needed to manage your subscription.
- Support and communication information, such as support tickets, messages, attachments you choose to send, and our responses.
We do not buy personal information from data brokers or collect it for unrelated profiling. We may receive information from a service you choose to connect, such as repository permissions, authentication results, build status, payment status, or technical diagnostics. We also generate technical records as Lahyer authenticates accounts, builds, deploys, hosts, and protects applications.
4. Where information comes from
We receive information directly from you when you register, configure a workspace, submit a prompt, upload or connect content, make a payment, or contact support. We receive information from an integration when you choose to connect it and authorize the requested access. Infrastructure, AI, analytics, payment, communications, and security providers may return transaction, usage, or diagnostic information needed for their role. We create some information automatically through service logs and operational events.
5. Why we use information and our legal grounds
We use information for specific service and business purposes, including to:
- create and secure accounts and workspaces, authenticate users, and administer access;
- connect the repositories you select, build and deploy code, host applications and databases, manage domains, and provide the AI features you request;
- show usage, credits, billing, and subscription information; process transactions; and investigate payment questions;
- answer support tickets, diagnose errors, explain build failures, and communicate operational, product, or security notices;
- monitor capacity and reliability, detect fraud or misuse, prevent security incidents, enforce our Terms, and protect Lahyer, users, and third parties;
- understand how our website and Services perform and improve them in line with your privacy choices and applicable law; and
- meet legal obligations, respond to valid legal requests, and establish, exercise, or defend legal claims.
Where privacy law requires a legal basis, we use a basis that fits the purpose and the circumstances. Depending on the activity and law, this may include providing a service or taking steps you request before a contract, complying with a legal obligation, pursuing a legitimate interest that does not override your rights, protecting vital interests, performing a public task where relevant, or your consent. We do not treat consent as the basis for every activity. If we rely on consent, you may withdraw it; withdrawal does not make earlier processing unlawful.
6. AI features and responsible use
Lahyer offers features, products, or tools powered by artificial intelligence, machine learning, and related technologies. These features may support AI-assisted development, automation, deployment, and troubleshooting. For example, an AI feature may use a prompt and relevant build logs or project context you authorize it to inspect to generate an application or explain an error.
When you use an AI feature, the information needed for that feature may be sent to a third-party AI service provider to produce the requested output. Depending on the feature, that information may include prompts, selected code or project context, files, configuration, or logs. The provider processes that information under its service terms and the contractual or technical settings Pryme Labs has configured.
We design AI features to assist development. AI output can be inaccurate, incomplete, insecure, or unsuitable for a particular purpose. Review and test generated code and other output before relying on or deploying it. Do not submit sensitive personal information, secrets, credentials, or information you are not authorized to share unless the feature and your agreement are designed for that use.
We do not use AI output alone to make decisions about your eligibility for employment, credit, housing, healthcare, or another legal or similarly significant matter. If a feature is introduced that makes or supports such a decision, we will provide additional information and choices required by applicable law.
7. When information is shared
We do not sell personal information for money, and we do not share it for third-party targeted advertising. We disclose limited information only as needed to provide the Services, carry out your instructions, protect the service, or meet legal requirements. Recipients may include:
- cloud hosting, infrastructure, database, monitoring, security, and communications providers that operate Lahyer;
- AI model or API providers when an AI feature you choose needs to process a prompt or relevant project context;
- GitHub, GitLab, Bitbucket, domain registrars, DNS providers, or other integrations you choose to connect;
- payment providers and financial institutions involved in checkout, billing, refunds, or payment disputes;
- analytics or measurement providers consistent with the privacy choices you make;
- professional advisers, regulators, courts, law-enforcement authorities, or other parties where disclosure is required by law or reasonably necessary to protect rights, safety, and security; and
- a buyer, investor, successor, or other party involved in a reorganization, financing, merger, or transfer of the Lahyer business, subject to applicable law.
Service providers are authorized to process information for their service role and under the applicable contract or settings. They may have their own privacy notices for information they process as independent controllers. When you connect a third-party integration, that provider’s terms and privacy practices also apply.
Some privacy laws use “sale,” “sharing,” or similar terms more broadly than an exchange of information for money. If our practices fall within one of those definitions, we will provide the notices and opt-out choices required by law. The Lahyer website’s privacy-choice controls may include analytics and advertising-storage settings.
8. Cookies, analytics, and privacy choices
Lahyer’s website may use cookies, local storage, pixels, or similar technologies for essential functions, security, analytics, and measurement. The website currently presents a Privacy choices control for analytics and advertising storage. The information collected depends on the settings you select, the feature enabled, and the law that applies. Some providers may receive limited cookieless measurement information even when optional storage is off.
You can change the choices presented in the Privacy choices control. You can also manage cookies through your browser. Blocking essential technologies may affect site functionality. Where required, we will ask for consent before using optional technologies and honor legally recognized opt-out signals.
9. International processing
Lahyer serves developers in Africa and beyond. Application servers or content delivery systems may operate in Africa and other regions, and our providers may process information in countries where they or their infrastructure operate. Those countries may have privacy protections different from the laws where you live.
Where a cross-border transfer requires a legal mechanism, we use a mechanism permitted by the applicable law, such as an adequacy decision, contractual safeguards, or another lawful basis. You may contact us for more information about relevant safeguards, subject to legal and security limits.
10. Retention and security
We keep information for the time reasonably needed to provide Lahyer, maintain accounts, resolve support and billing issues, meet legal and accounting requirements, investigate abuse, and protect the service. Different records may have different retention periods. When we no longer need information, we delete it, de-identify it, or securely dispose of it where practical and lawful. Some copies may remain in backup systems for a limited period or be retained when required to comply with law or resolve a dispute.
We use technical and organizational safeguards designed to protect information from unauthorized access, loss, or misuse. Access is limited according to operational need. No method of electronic transmission or storage is completely secure, and we cannot guarantee absolute security. You are responsible for protecting account credentials and API keys and for configuring your own applications and databases appropriately. If we become aware of a personal data breach that triggers a notification duty, we will notify affected individuals and regulators within the periods required by applicable law.
11. Your privacy rights and choices
Depending on your location and the law that applies, you may have the right to ask us to:
- confirm whether we process your personal information and provide access to it;
- correct inaccurate or incomplete information;
- delete information, restrict or object to certain processing, or withdraw consent where consent is the legal basis;
- provide a portable copy of information you supplied;
- opt out of certain sales, sharing, targeted advertising, or profiling, where those rights apply;
- not discriminate against you for exercising a privacy right; and
- review or challenge a decision made solely by automated means where the law provides that right.
These rights are not absolute. We may need to verify your identity or authority, protect another person’s rights, retain information required by law, or decline a request where an exception applies. If we act as a processor for an organization, we may direct your request to that organization or help it respond.
To make a request, open a Lahyer support ticket or email support@lahyer.com. Tell us the account email, your request, and the country or state where you live. We may ask for reasonable information to verify identity or authority. We will respond within the time required by applicable law, explain any extension or refusal where required, and tell you how to complain or appeal if the law provides that route.
12. Regional privacy information
Nigeria
Where the Nigeria Data Protection Act 2023 applies, you may have rights including to be informed, access information, correct it, object to processing, restrict processing, request portability or erasure, complain to the Nigeria Data Protection Commission, and not be subject to certain automated decisions, subject to the Act and applicable exceptions.
European Economic Area and United Kingdom
Where the GDPR or UK GDPR applies, you may have rights of access, rectification, erasure, restriction, objection, data portability, withdrawal of consent, and rights concerning certain automated decisions. You may also complain to your data protection supervisory authority. The rights and exceptions depend on our role, legal basis, and circumstances. Where required, we will provide the controller identity, purposes, legal basis, legitimate interests, recipient categories, retention criteria, transfer safeguards, and rights information.
Canada
Where Canadian privacy law applies, you may have rights to access and request correction of personal information, withdraw consent where permitted, and complain to the appropriate privacy regulator. The applicable rules may include PIPEDA and substantially similar provincial private-sector laws, depending on where the information is handled and the nature of the activity.
United States
Some U.S. state privacy laws provide rights to know or access, correct, delete, and obtain a portable copy of personal information; opt out of sale, sharing, targeted advertising, or certain profiling; and receive equal service for exercising privacy rights. Some laws also provide appeal rights and additional controls for sensitive data. The rights available, response times, and exceptions vary by state and may depend on whether the law covers Pryme Labs and the processing at issue.
Other locations
Other countries, including countries across Africa, may provide additional or different rights. We will apply the protections and complaint routes required by the law that applies to your information and circumstances.
13. Children and age requirements
Lahyer is designed for developers and organizations and is not directed to children. Users must be at least 18 years old and legally able to enter into a contract. If you believe a child has provided personal information in violation of this rule, contact support@lahyer.com so we can review the request and take appropriate action.
14. Complaints and Contact
For questions, privacy requests, or complaints, open a Lahyer support ticket or email support@lahyer.com. We will investigate complaints without unjustifiable or excessive delay, keep you informed of progress, and provide a response. If you are not satisfied, you may also complain to the privacy regulator with authority over your location or the relevant processing. We will acknowledge complaints within 30 days of receipt. This acknowledgement period does not replace any shorter or different deadline required by applicable law.
Pryme Labs LLC
Contact: support@lahyer.com
Registered office: Austin, Texas, United States
15. Changes to this Privacy Policy
We may update this Policy when Lahyer, our data practices, or legal requirements change. We will post the updated version with a new “Last updated” date. If a change materially affects how we use information already collected, we will provide additional notice or seek consent where required.