Privacy Policy
Last updated: May 21, 2026
This Privacy Policy explains how HAZE PARK collects, uses, stores, shares, and protects personal information when you access or use Lena Code.
Lena Code is a universal code platform operated by HAZE PARK. This Privacy Policy applies to our website, applications, software tools, APIs, account services, paid subscriptions, customer support, and related services.
By using Lena Code, you acknowledge that your personal information will be handled as described in this Privacy Policy.
1. Service Operator
Lena Code is operated by:
- Business name상호
- HAZE PARK
- Representative대표자
- Matt Park
- Business Registration Number사업자등록번호
- 609-45-01302
- Address사업장 주소
- 97, Centum jungang-ro, Haeundae-gu, Busan, Republic of Korea (48058)
- Privacy Contact개인정보 보호책임자
- Matt Park
- Email이메일
- support@lenacode.com
2. Information We Collect
We may collect the following categories of information.
2.1 Account Information
When you create an account or use Lena Code, we may collect:
- name;
- email address;
- username or account ID;
- password or authentication credentials;
- company or organization name;
- workspace name;
- account settings;
- subscription plan;
- login and authentication records.
2.2 Billing and Payment Information
When you purchase a paid plan, we may collect or receive billing-related information, including:
- billing name;
- billing email;
- billing address;
- company name;
- tax information;
- subscription plan;
- payment status;
- invoice records;
- transaction ID;
- payment date;
- refund or cancellation history.
Payments are processed through our designated payment provider. Payment Provider: Lemon Squeezy. We do not store full credit card numbers on our own servers. Full payment card details are handled by the payment provider according to its own terms, privacy policy, and security standards.
2.3 Service Content
When you use Lena Code, you may submit code, text, files, prompts, instructions, configuration data, comments, documentation, or other materials to the Service.
In this Privacy Policy, we refer to these materials as “Service Content.”
Service Content may include:
- source code;
- code snippets;
- technical documentation;
- prompts or instructions;
- files submitted for transformation or validation;
- generated outputs;
- validation results;
- language pair information;
- transformation history;
- project or workspace data.
2.4 Usage and Technical Information
We may collect technical and usage information when you use the Service, including:
- IP address;
- device information;
- browser type;
- operating system;
- approximate region;
- referring URL;
- pages viewed;
- features used;
- timestamps;
- session duration;
- API usage;
- error logs;
- crash logs;
- system performance data;
- security logs.
2.5 Communications
When you contact us, we may collect:
- your name;
- email address;
- message content;
- support request details;
- feedback;
- attachments;
- customer service history.
3. How We Use Information
We use personal information for the following purposes.
3.1 To Provide the Service
We use information to:
- create and manage accounts;
- provide code transformation and validation features;
- process Service Content;
- generate Output;
- manage workspaces;
- provide API access;
- authenticate users;
- maintain user sessions;
- deliver subscribed features.
3.2 To Process Payments and Subscriptions
We use billing and payment-related information to:
- process paid subscriptions;
- issue invoices and receipts;
- confirm payment status;
- manage renewals;
- process cancellations;
- handle refunds;
- prevent payment fraud;
- comply with tax, accounting, and legal obligations.
3.3 To Maintain and Improve the Service
We use information to:
- monitor service performance;
- debug errors;
- improve reliability;
- develop new features;
- analyze feature usage;
- improve user experience;
- optimize supported language pairs;
- evaluate transformation quality;
- improve validation accuracy.
3.4 To Protect the Service
We use information to:
- detect abuse;
- prevent unauthorized access;
- investigate suspicious activity;
- enforce usage limits;
- prevent fraud;
- protect users, our systems, and third parties;
- maintain security logs;
- respond to security incidents.
3.5 To Communicate With You
We use information to:
- respond to support requests;
- send account notices;
- send billing notices;
- notify you of changes to the Service;
- provide security alerts;
- send administrative messages;
- provide product updates where permitted.
3.6 To Comply With Legal Obligations
We may use information to:
- comply with applicable laws and regulations;
- respond to lawful requests;
- maintain required business records;
- enforce our Terms of Service;
- resolve disputes;
- protect legal rights.
4. Service Content and Code Privacy
We understand that Service Content may include sensitive technical materials, proprietary code, confidential business information, or internal development logic.
We process Service Content to provide, maintain, secure, troubleshoot, and improve Lena Code.
Unless you explicitly opt in or we separately agree with you, we do not use your Service Content to train general-purpose AI models.
We do not sell your Service Content to advertisers or data brokers.
Submitted source code is not persisted beyond the request lifecycle in Lena Code infrastructure.
Generated result caches may store AI-generated output, not submitted source bodies, keyed by request hash, with TTL no longer than 30 minutes.
AI request ledger entries store request hashes, plan, token counts, cost, and usage metadata only; those entries expire after 30 days.
Logs and metrics retain request hashes and operational metadata only; submitted source bodies are not retained.
We may access Service Content only when reasonably necessary for purposes such as:
- providing the requested Service;
- debugging technical issues;
- responding to support requests;
- preventing abuse or security threats;
- complying with legal obligations;
- enforcing our Terms of Service;
- improving reliability, quality, and safety of the Service.
4.1 AI Provider Boundary
AI model providers (currently Google Gemini) process redacted request content to return results under their own data terms.
For paid Gemini API services, Google states that prompts and responses are not used to improve Google products. Limited transient logging may occur for safety, policy, legal, and regulatory purposes under Google's Gemini API terms and applicable data processing commitments.
5. Legal Bases for Processing
Where applicable, we process personal information based on one or more of the following legal bases:
- performance of a contract with you;
- your consent;
- our legitimate interests;
- compliance with legal obligations;
- protection of rights, safety, and security;
- establishment, exercise, or defense of legal claims.
7. Third-Party Service Providers and Subprocessors
We may use third-party service providers to operate, secure, and improve Lena Code.
The service providers and subprocessors we currently use are listed below.
| Provider | Purpose | Location |
|---|---|---|
| Vercel | Hosting, infrastructure, serverless functions, static edge delivery | United States / Global edge |
| GitHub | User authentication (OAuth sign-in) | United States |
| User authentication (OAuth sign-in) | United States | |
| Google Gemini API | AI inference for explanation and reconstruction using redacted submitted source content | United States |
| Upstash Redis | Daily quota counters, abuse-prevention metering, temporary usage limits, and short-window hash-keyed result cache for AI-generated output | United States |
| Neon Postgres | Identity, subscriptions, entitlements, payment-event ledger, API token hash metadata, and usage counters | United States |
| Lemon Squeezy | Payment processing, subscription billing | United States |
| Resend | Transactional emails and account notices | United States |
| Vercel | Product analytics and usage measurement | United States / Global edge |
8. International Processing and Transfers
Lena Code is operated from the Republic of Korea and may be used globally.
Your information may be processed, stored, or transferred in countries other than your country of residence, depending on our infrastructure, service providers, payment provider, and operational needs.
Where required by applicable law, we will take appropriate measures for international transfers of personal information.
The international transfers we currently make are described below.
| Recipient | Country | Information Transferred | Purpose | Retention |
|---|---|---|---|---|
| Vercel | United States / Global edge | Account information, submitted source content (ephemeral processing only), generated results, usage logs | Hosting, serverless function execution, static edge delivery, and service operation | Per provider data processing agreement; submitted source code is not persisted by Lena Code beyond the request lifecycle; logs and operational metadata follow operational retention |
| GitHub | United States | Account identifier, email address, OAuth profile (name, avatar) | User authentication (OAuth sign-in) | Per the provider’s data processing agreement; for the duration of authentication |
| United States | Account identifier, email address, OAuth profile (name, avatar) | User authentication (OAuth sign-in) | Per the provider’s data processing agreement; for the duration of authentication | |
| Google Gemini API | United States | Redacted submitted source content and generated responses | AI inference for explanation and reconstruction | Per provider data processing agreement and Gemini paid API terms; prompts/responses not used to improve Google products; limited transient logging for safety, policy, legal, and regulatory purposes |
| Upstash Redis | United States | Daily quota identifiers such as account email-derived keys, IP-derived keys, request counters, reset TTLs, request hashes, and AI-generated output cached for result rehydration; no submitted source body | Quota enforcement, abuse prevention, temporary usage limits, and short-window result rehydration | TTL-based daily counters; generated result cache TTL no longer than 30 minutes; per provider data processing agreement |
| Neon Postgres | United States | Account identifiers, OAuth provider account links, subscription and payment-event records, API token hashes, and daily usage counters | Identity, billing, and quota system of record | Payment and contract records retained for at least 5 years where required by law; other records until account deletion or as required by law |
| Lemon Squeezy | United States | Billing information, payment status, transaction records | Payment processing | Per the provider’s data processing agreement; until account deletion or as required by law |
| Resend | United States | Email address, account notices | Email delivery | Per the provider’s data processing agreement; until account deletion or as required by law |
| Vercel | United States / Global edge | Usage and technical information | Analytics and product improvement | Per the provider’s data processing agreement; until account deletion or as required by law |
9. Data Retention
We retain personal information only for as long as necessary for the purposes described in this Privacy Policy, unless a longer retention period is required or permitted by law.
Retention periods may vary depending on the type of information, the reason for collection, legal requirements, security needs, and dispute resolution needs.
9.1 General Retention
| Type of Information | Retention Period |
|---|---|
| Account information | Until account deletion, unless retention is required by law |
| Submitted source code | Not persisted beyond the request lifecycle in Lena Code infrastructure |
| Generated result cache | AI-generated output only, not submitted source bodies; hash-keyed; TTL no longer than 30 minutes |
| AI request ledger | Request hash, plan, token counts, cost, and usage metadata only; TTL 30 days |
| Operational logs and metrics | Request hashes and operational metadata only; submitted source bodies are not retained; retained up to 12 months unless a shorter operational TTL applies |
| Support inquiries | 3 years |
| Billing and payment records | 5 years |
| Security logs | 12 months |
| Marketing consent records | Until consent withdrawal or as required by law |
9.2 Legally Required Retention
Where applicable, we may retain certain records for legally required periods, including:
| Record Type | Required Retention Period |
|---|---|
| Records of contracts or withdrawal of subscriptions | 5 years |
| Records of payment and supply of goods or services | 5 years |
| Records of consumer complaints or dispute resolution | 3 years |
| Records of display or advertising | 6 months |
10. Deletion
When personal information is no longer necessary for the purposes described in this Privacy Policy, we will delete or anonymize it in accordance with applicable law and our internal retention procedures.
Deletion may be delayed where retention is necessary to:
- comply with legal obligations;
- resolve disputes;
- enforce agreements;
- prevent fraud or abuse;
- maintain security;
- complete backup deletion cycles;
- comply with tax, accounting, or audit requirements.
11. Your Rights
Depending on your location and applicable law, you may have rights regarding your personal information, including the right to:
- request access to your personal information;
- request correction of inaccurate information;
- request deletion of personal information;
- request suspension of processing;
- withdraw consent;
- object to certain processing;
- request data portability, where applicable;
- file a complaint with a relevant data protection authority.
You may exercise these rights by contacting us at: Email: support@lenacode.com. We may need to verify your identity before responding to your request. We may deny or limit a request where permitted by applicable law, such as when retention is required for legal obligations, security, dispute resolution, fraud prevention, or legitimate business purposes.
12. Account Controls
Where available, you may access, update, export, or delete certain information through your account settings; otherwise, you may contact support to make such a request.
Available controls may include:
- updating account profile information;
- changing email address;
- changing password;
- managing workspace settings;
- managing subscription status;
- deleting account data;
- contacting support for privacy requests.
Some information may not be editable or deletable through the account interface if it is required for legal, billing, security, or operational reasons.
14. Marketing Communications
We may send you product updates, announcements, or marketing communications where permitted by law.
You may opt out of marketing emails by using the unsubscribe link in the email or by contacting us.
Even if you opt out of marketing communications, we may still send non-marketing messages, such as:
- account notices;
- billing notices;
- security alerts;
- service updates;
- legal notices;
- support replies.
15. Security
We use reasonable technical, administrative, and organizational measures to protect personal information.
These measures may include:
- encryption in transit;
- access controls;
- authentication controls;
- logging and monitoring;
- backup controls;
- vulnerability management;
- internal access restrictions;
- service provider review;
- incident response procedures.
However, no method of transmission or storage is completely secure. We cannot guarantee absolute security.
16. Data Breach Notification
If a security incident occurs that affects personal information, we will take appropriate steps in accordance with applicable law.
These steps may include:
- investigating the incident;
- limiting further harm;
- notifying affected users where required;
- notifying relevant authorities where required;
- improving safeguards to prevent similar incidents.
17. Children’s Privacy
Lena Code is not intended for children.
We do not knowingly collect personal information from children under the minimum age required by applicable law.
Minimum Age: 14
If we learn that we have collected personal information from a child without appropriate consent, we will take reasonable steps to delete it.
If you believe a child has provided us with personal information, please contact us at: Email: support@lenacode.com
18. Do Not Track
Some browsers may send “Do Not Track” signals.
Because there is no uniform industry standard for responding to such signals, we may not respond to Do Not Track signals unless required by applicable law.
19. Third-Party Links
The Service may contain links to third-party websites, services, documentation, or integrations.
We are not responsible for the privacy practices, content, security, or policies of third-party services.
You should review the privacy policies of any third-party services you use.
20. Changes to This Privacy Policy
We may update this Privacy Policy from time to time.
If we make material changes, we will take reasonable steps to notify you, such as by posting the updated Privacy Policy on our website, sending an email, or displaying an in-service notice.
The updated Privacy Policy will be effective as of the date stated at the top of the policy.
Your continued use of the Service after the updated Privacy Policy becomes effective means you acknowledge the updated policy.
21. Contact
If you have questions, requests, or concerns about this Privacy Policy or our handling of personal information, please contact us at:
HAZE PARK
Privacy Contact: Matt Park
Email: support@lenacode.com
Address: 97, Centum jungang-ro, Haeundae-gu, Busan, Republic of Korea (48058)