Privacy

1. Who this notice applies to

This notice applies to visitors, registered users, free-preview users, and paid users of Adrenn. Adrenn is owned and operated by Djamal Garoud, an individual based in Sweden. Djamal Garoud is responsible for the personal information Adrenn processes as a data controller for its own account, billing, security, and service operations. Where Adrenn processes data on behalf of customers through their deployed applications, the roles and responsibilities may differ depending on the service.

2. Information Adrenn processes

Adrenn may process account information such as your email address and authentication details; project information such as your Vision Lock, prompts, queued instructions, generated application content, checkpoints and project history; uploaded images and associated metadata where the feature is used; subscription plan, billing status, payment-provider customer references, and transaction records where paid services are enabled; and technical information needed to operate and secure the service. Payment-card details entered at a hosted checkout are handled by the payment provider rather than collected directly through Adrenn's project workspace.

Technical information may include browser or device identifiers, IP-related information, timestamps, request frequency, generation events, error information, and security or abuse-prevention signals. For supported authenticated account and navigation events, Adrenn may also temporarily store the IP address observed at the server, country code when available, and browser user-agent information associated with that specific event for account security and abuse investigations. Background processes may not have an independently observed IP address. These details are available only to authorized operators with multi-factor authentication; event IP addresses and user-agent details are redacted after 30 days. Older events may not have this information.

3. How Adrenn uses your information

Adrenn uses information to create and manage accounts, generate and edit applications, preserve project history and checkpoints, provide previews and publishing features, enforce free and paid usage limits, administer subscriptions and support billing and tax records when payments are enabled, diagnose failures, improve reliability, secure the service, prevent misuse, and respond to user requests.

3A. Account and platform activity

To operate Adrenn, monitor reliability, investigate failures, and protect accounts, Adrenn records limited activity metadata such as successful sign-in and sign-out actions, workspace, project and account page visits, project creation and changes, saved versions, publishing changes, and build-job status. These records can include the associated account identifier, project identifier, action type and timestamp. They do not include passwords, full prompts, generated code, payment-card details or keystrokes.

Platform activity records are accessible only to authorized administrators who have completed additional authentication. Browser-reported navigation and sign-in events are operational observations, not conclusive proof of a person's actions. Logs are kept only for legitimate operational and security purposes, and requests about access, correction or deletion can be sent to hello@adrenn.com, subject to applicable legal requirements.

4. AI generation

When you ask Adrenn to build or edit an application, relevant project content is sent to an AI model provider so the requested output can be generated. This may include your project brief, queued instructions, and the current generated application code where necessary to perform an edit.

Adrenn aims to send only the context needed for the requested generation. Users should avoid entering secrets, passwords, payment-card information, highly sensitive personal information, or other data that is unnecessary for the build.

4A. Image uploads and safety screening

When paid-plan image uploading and AI-assisted visual editing are available, Adrenn may process the images you supply, related file metadata, and associated project and account identifiers to operate those features. Uploaded images may be decoded and converted into safer formats before storage. To enforce content-safety policies, Adrenn may send the converted image to an AI moderation provider for automated assessment before making it available for use in a project.

Images accepted for incorporation into published applications may be hosted at publicly accessible asset URLs. Such URLs are not appropriate for private, confidential, or sensitive images. Even when an image is removed from a project, access through previously distributed links or backups may persist for a period. Requests about image access or deletion may be directed to hello@adrenn.com.

Where required to investigate suspected abuse or comply with the law, Adrenn may process limited safety decisions, timestamps, account and project identifiers, and relevant reports. We aim to minimize unnecessary retention and exposure of prohibited or sensitive image content.

5. Abuse prevention and free usage

To protect Adrenn from repeated exploitation of free usage allowances, automated abuse, and circumvention of usage limits, Adrenn may process account identifiers, a first-party device or browser identifier, hashed IP-related information, generation timing and frequency, and indicators of similarity between recent generation requests.

Similarity checks are used as one signal among several. They are not treated as proof that two accounts belong to the same person. A request may be slowed, blocked, or reviewed when several signals indicate likely misuse.

6. Cookies and device identifiers

Adrenn may place a first-party device identifier in your browser so the service can recognize repeated use of the free preview and protect against abuse. This identifier is used for service protection and is not intended for advertising.

7. Service providers

Adrenn relies on specialist service providers to operate the product. These currently include Supabase for authentication and database services, Vercel for application hosting and deployment, GitHub for source-code infrastructure, and OpenAI for AI generation. When subscription payments are enabled, Stripe may process checkout, payment, subscription, and billing information. Providers process relevant information under their applicable agreements, roles, and privacy terms. Adrenn does not receive full payment-card details through its own hosted checkout.

8. Legal bases

Where the GDPR or similar law applies, Adrenn processes information when necessary to provide the service you request, to comply with legal obligations, and for legitimate interests such as securing the service, preventing abuse, maintaining reliability, and protecting fair access to Adrenn. Where consent is legally required, Adrenn will request it separately.

9. Data minimisation and retention

Adrenn aims to collect and retain only what is reasonably necessary for the relevant purpose. Account and project information may be retained while your account remains active and for a reasonable period afterwards where needed for security, dispute resolution, legal obligations, or backup integrity.

Abuse-prevention data is designed to be more limited. Technical identifiers are transformed or hashed where practical, and persistent abuse-event records are periodically removed when they are no longer needed for fair-use and security purposes.

10. International data transfers

Some service providers may process information outside your country of residence. Where required, Adrenn relies on appropriate contractual, organizational, or legal safeguards for such transfers.

11. Security

Adrenn uses technical and organizational safeguards intended to protect account, project, uploaded-image, billing, and usage data. No online service can guarantee absolute security, but Adrenn is designed to limit unnecessary access, keep sensitive infrastructure credentials server-side, and separate user projects through access controls.

12. GDPR and your data protection rights

If you are in the European Economic Area and the GDPR applies to Adrenn's processing of your personal data, you may have rights to request access to, correction or deletion of, or restriction of processing of your personal data; to receive certain personal data in a portable format; and to object to certain processing. Where processing is based on consent, you may withdraw that consent at any time without affecting the lawfulness of processing before withdrawal.

You may also have the right to lodge a complaint with the competent data-protection authority. Requests can be made by email to hello@adrenn.com. Adrenn may need to verify your identity before acting on a request. Depending on your location and the applicable rules, the competent Swedish supervisory authority is Integritetsskyddsmyndigheten (IMY).

13. Age requirements

Adrenn is intended for users who meet the minimum age required to use online services independently in their jurisdiction. Where a user is below that age, access to Adrenn should only occur with any parental or guardian authorization required by applicable law. If Adrenn becomes aware that personal information has been collected in circumstances that do not meet those requirements, it will take reasonable steps to address the situation.

14. Sale of personal information

Adrenn does not sell users' personal information to advertisers. Adrenn's product and infrastructure decisions are not based on selling user project data for advertising purposes.

15. Changes to this notice

This notice may be updated as Adrenn's product, payment system, hosting, security controls, or legal obligations evolve. Material changes will be reflected on this page and the last-updated date revised. Questions or privacy requests can be sent to hello@adrenn.com.