Marketing email and checkout recovery consent
Optional marketing emails, including Creem abandoned-cart or checkout-recovery messages, are sent only where the legally required marketing-email consent exists. Transactional account, security, billing, and service messages may still be sent where necessary to provide and protect the service.
1. Who We Are
Aslax, LLC operates Aslax and acts as the controller for personal data processed through the public website, account system, billing flows, and product features described on this page.
For privacy or data-rights requests, contact aslan@aslax.eu.
Aslan Al-Abdali is our named legal and privacy contact at aslan@aslax.eu. Aslax, LLC is a US company. This contact listing does not represent a verified EU establishment or Article 27 representative appointment. Where legally required, we will provide the appointed EU representative’s current establishment and contact details.
2. Data We Collect
We collect the categories of data needed to provide the service, secure accounts, run billing, and respond to support or legal issues.
- Account data: name, email address, login identifiers, authentication events, account settings
- Compliance data: email-verification status, consent status for high-risk features, fraud or abuse review signals, and moderation-related records
- Consent records: user ID, timestamp, policy version, consent text version, feature, asset or generation identifiers, IP address where appropriate, and related audit metadata
- Billing data: plan, subscription status, invoices, payment metadata, anti-fraud results, limited tax and checkout information
- AI request data: prompts, uploaded files, generation settings, reference media, generated outputs, and related project history
- Community data: posts, comments, reactions, moderation status, and related activity
- Support and communications: emails, support tickets, complaints, and related attachments or references
- Usage and technical data: IP address, browser, operating system, device identifiers, logs, diagnostics, security events, and abuse-prevention signals
3. How We Use Data
We use personal data to create and manage accounts, fulfill AI and software requests, deliver files and outputs, process billing, prevent abuse, maintain product reliability, answer support requests, and meet legal obligations.
Aslax sells access to its own software service. Aslax does not operate a marketplace, does not facilitate peer-to-peer payments, and does not process payments on behalf of third-party sellers.
If you use features involving faces, voices, likenesses, or other sensitive media, you are responsible for having the permissions, notices, and consents required by applicable law.
We may use verification state, consent acceptance, device or network risk signals, and moderation outcomes to gate sensitive features, investigate abuse, and document policy decisions.
Community posts are private until approved. Approved posts may be visible to other users and visitors.
4. Legal Bases for Processing
Depending on the context, we process personal data because it is necessary to provide the service you request, comply with legal obligations, protect legitimate business and security interests, or because you gave consent where consent is required.
- Contract: account creation, sign-in, generation requests, file delivery, subscriptions, billing administration, and support tied to the service
- Legitimate interests: service security, abuse prevention, fraud review, logging, troubleshooting, product reliability, and defending legal claims
- Legal obligations: tax, accounting, sanctions, law-enforcement response, and recordkeeping duties
- Consent: optional analytics and any other processing we clearly present as consent-based
5. AI Processing, Model Providers, and Training
When you use AI features, we may send prompts, uploaded files, generation settings, and related technical metadata to selected model or infrastructure vendors to fulfill your request.
Certain requests may be routed through Vercel AI Gateway as an AI infrastructure and routing provider before being processed by the applicable downstream model provider.
Depending on provider and plan, those vendors may retain and use content to operate, secure, or improve their services, including model improvement or safety analysis.
Aslax may use limited content metadata to monitor quality, prevent abuse, and comply with legal obligations.
If you require providers that do not train on your content, contact support@aslax.eu before submitting sensitive materials. Availability of opt-out or enterprise terms varies by provider.
Authorized personnel may access limited account or content data when needed for support, security review, abuse prevention, billing disputes, moderation, or legal compliance.
Aslax does not use private customer inputs or outputs to train its own general-purpose AI models. Upstream-provider processing is separate: retention, safety review and any training restrictions depend on the selected route and its contractual configuration. A private workspace or paid plan alone is not a guarantee of no upstream training. Business customers can request a documented restricted provider configuration before submitting data.
6. Cookies and Optional Analytics
We use essential cookies and local storage for authentication, security, language, and product settings.
Optional analytics run only if the visitor accepts optional analytics through the available consent controls.
See the Cookie Notice for more detail about storage categories, consent controls, and how to change your choice later.
7. Face, Voice, Likeness, and Consent Records
Some AI media features may process faces, voices, likenesses, or reference media to fulfill a user request. These features are intended only for content the user owns or is explicitly authorized to process.
We may store consent attestations and moderation records to document that the user confirmed permission, to enforce the Acceptable Use Policy, and to respond to abuse, takedown, billing, or legal inquiries.
We do not permit biometric identification, face recognition, sensitive trait inference, or automated categorization of people through the service.
If Illinois or similar biometric privacy laws apply, we require written consent before processing biometric identifiers or voice/face data and we may request evidence of consent.
We do not sell biometric identifiers and do not use them for advertising.
8. Payments, Billing, and Fraud Checks
Payments are processed by the active checkout and billing providers. We receive payment status, invoice and receipt data, billing metadata, limited anti-fraud results, and other information needed to complete transactions and manage subscriptions.
We do not receive full card numbers. Card collection and payment authorization are handled by hosted checkout infrastructure.
We may review transaction, device, and account signals to detect fraud, chargeback abuse, sanctions issues, restricted-business activity, and other policy or compliance risks.
9. Recipients and Service Provider Categories
Our provider register at /subprocessors identifies integrated vendors, their roles, data categories and configuration-dependent processing. A model or vendor is used only when the relevant feature or account routes data to it. Contact aslan@aslax.eu for the actual recipients and safeguards applicable to your data.
- Hosting, infrastructure, database, storage, and email-delivery providers that support account operations, files, and service availability
- Authentication and identity providers that handle sign-in, email verification, and fraud checks
- Payment processors and billing providers used for checkout, subscriptions, invoices, receipts, tax handling, and payment-risk checks
- AI model, cloud, and media-processing providers used to execute prompts, uploads, generation requests, transformations, and output delivery
- Analytics and measurement providers, but only where optional analytics have been accepted
- Professional advisers, auditors, authorities, acquirers, or counterparties where disclosure is needed for legal, security, transaction, or compliance purposes
10. International Transfers
Some recipients process data in the United States or other countries outside your own. Depending on the recipient and destination, transfers may rely on an adequacy decision, contractual safeguards such as Standard Contractual Clauses, or another lawful transfer mechanism.
You can contact us if you need more information about the transfer safeguards relevant to your data.
11. Data Retention
We keep account, billing, support, security, and project data for as long as needed to provide the service, maintain records, investigate abuse or disputes, and meet legal obligations.
The table below shows our typical retention approach. Where a longer period is required for a dispute, legal hold, billing investigation, or security incident, we may retain the relevant record for longer.
Approved community posts may remain visible to other users until removed or moderated; you can request removal through support or moderation.
Moderation, complaints, fraud-review, and consent-verification records may be retained for longer where needed to enforce our policies, respond to disputes, or satisfy legal, billing, or security requirements.
You can request deletion of account content or generated media through support, account controls where available, /report-abuse, or /takedown when the request involves rights, safety, or non-consensual media concerns.
| Data category | Typical retention | Criteria / trigger |
|---|---|---|
| Account data | While active; closure and deletion requests trigger review | Account access, necessary security records and unresolved account obligations; erased when those purposes and applicable holds end |
| Project context / web research / uploads / outputs | Until user deletion or the selected retention cutoff | Where supported and enabled, Settings offers 7, 30, 90 or 365 days; active work may be skipped and category status identifies incomplete enforcement |
| Billing and tax records | For the applicable statutory accounting period | Determined by the seller, tax jurisdiction, transaction date and applicable recordkeeping law; restricted to required records |
| Security and moderation evidence | While needed for an identified incident, appeal or claim | Review at case closure and at any hold expiry; no indefinite retention merely because a record might be useful |
| Consent / contract records | For the acceptance period and applicable claim or legal-hold period | Versioned evidence of the relevant transaction or consent; access limited to operational and legal need |
| Support records | While the case, appeal, billing dispute or lawful hold remains open; then assessed for deletion | Case purpose and applicable limitation/recordkeeping period, with irrelevant attachments removed when no longer needed |
| Backups and vendor copies | According to the applicable backup rotation and vendor deletion obligations | Deleted data is restricted from normal use; restoration must reapply deletion decisions; request the applicable provider schedule from aslan@aslax.eu |
12. Your Rights
Depending on your location, you may have rights to request access, correction, deletion, restriction, objection, export, or withdrawal of consent for processing that relies on consent.
To exercise applicable rights, contact aslan@aslax.eu. You may also have the right to complain to your local supervisory authority.
We respond to GDPR rights requests without undue delay and normally within one month. Where law permits an extension for complexity or volume, we tell you within that month, with reasons. Identity checks are proportionate; we do not require unrelated sensitive documents. Requests are normally free unless an applicable legal exception permits a charge or refusal. We explain any refusal and available complaint or appeal rights.
13. Security
We use administrative, technical, and organizational measures designed to protect accounts, billing flows, and stored data. These measures include access controls, encrypted transport, service monitoring, and provider security features appropriate to the service.
Children and Age Restrictions
The service is not intended for anyone under 18 years of age. Users under 18 may not create an account, purchase credits, subscribe, upload content, or use the service.
We do not knowingly collect personal information from children in a manner prohibited by applicable law. If you are a parent or guardian and believe that a child has provided personal information to Aslax without required consent, contact us at aslan@aslax.eu or support@aslax.eu.
If we learn that we have collected personal information from a child without required parental or guardian consent where required by law, we will take steps required by applicable law. Those steps may include deleting the information, disabling the account, restricting access, or preserving limited records where necessary for safety, security, fraud prevention, legal compliance, or dispute handling.
Do Not Submit Sensitive Information
Do not submit confidential information, government identifiers, health information, financial account credentials, trade secrets, unlicensed proprietary material, or biometric information unless the specific feature clearly permits it and you have all required rights, consents, and legal authority.
Aslax is not designed for medical, legal, financial, employment, housing, insurance, migration, or other high-risk decisions.
Account and Content Deletion
Users may request account closure or deletion of account content by contacting support. Deleted content may not be immediately removed from backups, logs, fraud-prevention records, billing records, legal archives, or security systems.
We may retain limited records where reasonably necessary for legal compliance, tax or accounting obligations, dispute resolution, fraud prevention, chargeback handling, safety enforcement, abuse investigations, or security purposes.
Third-Party Login and Connected Accounts
If you sign in or connect Aslax using a third-party service such as Google, we may receive account information made available by that provider, such as your name, email address, profile image, account identifier, and authentication status.
Our use of information received from third-party authentication providers is limited to account access, security, authentication, support, and service operation, unless otherwise disclosed.
API, Automation, and Technical Limits
Aslax may apply limits to API calls, job concurrency, file size, processing time, credit usage, storage, rate limits, and other technical usage. We may modify limits to protect service reliability, prevent abuse, manage model-provider capacity, or comply with security, billing, and card-network requirements.
Users may not scrape, overload, bypass limits, reverse engineer, resell access, or use automation to abuse the service.
Service Interruptions and Provider Availability
Aslax may rely on third-party infrastructure, model providers, hosting providers, billing providers, and network services. We are not responsible for delays, interruptions, failed generations, degraded quality, or unavailability caused by events outside our reasonable control.
Examples include internet outages, model-provider downtime, cyberattacks, maintenance, sanctions or billing-partner restrictions, legal requirements, or infrastructure failures.
14. Policy Updates
We may update this policy for legal, technical, product, or operational reasons. Material changes will be reflected here with an updated effective date.
15. Contact
Aslax, LLC
Website: https://aslax.eu
Address: 1111B S Governors Ave, Suite 52762, Dover, DE 19904, United States
Phone: (302) 546-5151
Support: support@aslax.eu
Privacy / legal: aslan@aslax.eu
Regional Privacy Rights
For individuals residing in Saudi Arabia, applicable PDPL rights include being informed, access and obtaining a copy, correction and destruction subject to lawful exceptions. Contact aslan@aslax.eu; you may also complain to SDAIA. We assess applicable transfer safeguards before transferring protected personal data outside the Kingdom.
Where applicable US state privacy laws grant access, correction, deletion, portability, appeal, or opt-out rights, you may exercise them through aslan@aslax.eu without unlawful discrimination. Authorised agents may act with appropriate evidence of authority. Advertising technologies require your separate optional choice; we honour applicable legally required opt-out signals.
Rights depend on applicable law and the processing involved. Delaware governing law does not displace mandatory privacy, consumer, accessibility or platform obligations in your location.
Export Transparency and Privacy
AI exports may carry a machine-readable AI notice and an opaque public provenance reference. Aslax does not add your internal account ID, email address or private prompt to public provenance metadata. File formats that cannot safely carry an embedded notice can use an accompanying provenance manifest. Such metadata identifies AI involvement; it does not certify authorship, accuracy or absence of third-party rights.
Model + Beta Notices
Some features rely on third-party AI providers and additional policies.
- Third-party providers may apply their own terms and safety policies in addition to ours.
- Some requests may be routed through Replicate, fal.ai, Google Vertex AI / Gemini, Kling, Seedance, or similar providers depending on the selected model, feature, request type, availability, and performance.
- ASLAX is an independent product and custom software interface. It is not affiliated with, sponsored by, or endorsed by these providers or model creators. Model and provider names identify available integrations only.
- If users connect their own API keys, they are responsible for billing, rate limits, and compliance tied to those keys.
- Image and Video Beta features are governed by our Beta Terms.
AI Processing and Third-Party Model Providers
ASLAX provides AI-powered generation and editing features for images, video, audio, text, and related media. Some requests may be processed using third-party AI infrastructure or model providers, such as Replicate, fal.ai, Google Vertex AI / Gemini, Kling, Seedance, or similar providers, depending on the selected model, feature, request type, availability, and performance.
ASLAX is an independent product and custom software interface. ASLAX is not affiliated with, sponsored by, or endorsed by these providers or model creators. Model and provider names are used only to identify available integrations.
When users use these features, ASLAX may send the data necessary to process the request to these providers. This may include prompts, uploaded files, reference images, generation settings, and resulting outputs.
ASLAX does not send full payment card details to AI model providers. Payments are processed separately through hosted checkout infrastructure.
Available models and providers may change over time. ASLAX may add, remove, or replace providers to improve quality, speed, reliability, availability, safety, or security.
Vercel AI Gateway and Downstream Model Providers
Certain AI requests may be routed through Vercel AI Gateway, an AI routing and infrastructure service that enables ASLAX to interact with selected third-party AI model and inference providers.
When a feature uses Vercel AI Gateway, ASLAX may send the data necessary to process the request through Vercel and to the applicable downstream model provider. This may include prompts, uploaded files, reference media, generation settings, technical metadata, and resulting outputs.
The applicable downstream provider may process data under its own terms, privacy notices, safety policies, retention rules, and model-training practices. These conditions may vary by provider, model, account configuration, and plan.
By using features routed through Vercel AI Gateway, users must comply with the applicable ASLAX policies, the Vercel AI Product Terms, the Vercel Acceptable Use Policy, and any applicable downstream provider terms made available for the selected model.
ASLAX is an independent product and custom software interface. ASLAX is not affiliated with, sponsored by, or endorsed by Vercel or any downstream model provider. Available routing infrastructure and model providers may change over time to improve quality, performance, reliability, safety, or availability.
Reference: Vercel Notices and License Information.