Aiomize
Privacy Policy
Last updated
This policy describes Aiomize's website and optimization service. The website provides product information and a customer portal. Subscriptions are purchased through secure Stripe checkout.
Who is responsible
Qleerly AI AB (reg. no. 559595-0246), Sweden is responsible for the personal data described here. Contact [email protected] for privacy requests.
Information processed
| Data | Purpose |
|---|---|
| Company details, contact name, contact email and optional phone number | Maintain a customer profile, deliver sign-in links and communicate about the software. |
| Registered website addresses and ownership verification | Identify authorized websites and confirm permission to manage them. |
| Public website content, scan results and findings | Assess technical and content issues and produce optimization suggestions. |
| Approved changes, snapshots and delivery records | Apply changes safely, support rollback and document work. |
| Plan, usage and audit records | Enforce access limits, maintain security and record service activity. |
| IP addresses and request information in server access logs | Operate the website, diagnose failures and detect abuse. |
| Connection credentials, where you authorize an integration | Deliver approved changes to the connected platform. |
Trial onboarding
If you request a trial, we collect your email address, website, business name and description, and website goals. How you found Aiomize and whether you would like optimization help are optional. We use these answers to set up your workspace, guide connection and tailor the service. They are not a subscription to marketing emails. Answers awaiting email verification are attached to the short-lived sign-in request and cleared after that request expires. Verified answers are saved with your account under the retention and deletion practices below. Trial activation, expiry and paid conversion are recorded to operate the service and prevent repeated trials.
Account guidance emails
We use your verified account email and actual setup, analysis, publication and report status to send relevant next steps and result notifications throughout your customer relationship. Trial guidance includes expiry and optional payment choices. You can stop guidance in Account & billing or through the unsubscribe link. Security and payment messages are separate. We retain delivery identifiers and minimal event history to prevent duplicates; stored message content is cleared seven days after successful delivery, or after thirty days for unresolved or cancelled deliveries. Guidance does not include fabricated results or use your questionnaire answers as permission for unrelated marketing.
Why we process data
We process customer data to provide the service and fulfill our agreement. Security and operational logs support our legitimate interest in running a reliable service. Legal records are retained where required by law. Optional marketing requires consent.
AI providers and integrations
When an AI feature is used, relevant website content and instructions may be processed through OpenRouter by the selected model provider. Visitors using an embedded Qleerly chatbot have their question and customer-provided business information sent to the selected provider. The portal records the model, time and usage cost, not the visitor question or answer. Providers have their own retention and processing policies; do not include confidential or sensitive information in material intended for AI processing unless you have a suitable legal basis and authorization.
Customer-authorized website platforms process the data necessary for their integration. Stripe processes payment and billing information for checkout, subscriptions and refunds. We do not store payment card numbers.
Google Tag Manager
Our Aiomize container (GTM-WMGBFLHN) loads on public information pages after you allow Analytics, Google Ads measurement and marketing cookies. Partial choices continue using their separate measurement settings. Tag Manager does not load in the customer portal, sign-in or checkout pages.
Google sign-in and customer API keys
If you choose Google sign-in, Google processes the authentication request and provides your account identifier and verified email address. We store the Google account identifier to link future sign-ins to your customer account. Temporary cookies named aig and aigl support the sign-in and account-linking process and expire after fifteen minutes. You can also sign in by email.
Customer API keys provide read-only access to the customer profile. Key secrets are shown only when created and stored as hashes. Keep them in server-side environment configuration; they can be revoked from the portal. Contact details are not automatically included in the public chatbot context.
Cookies and advertising measurement
Optional marketing cookies are off until you choose Allow marketing cookies. On public information pages, the Meta Pixel (ID 1434234365571629) measures page visits and helps us assess advertising and show relevant ads. When allowed, Meta receives the visited page address, browser and network information, and advertising identifiers such as _fbp and _fbc. We do not send customer form contents, sign-in details or payment information through this integration. Advertising code is not installed in the customer portal or checkout. Automatic event detection is disabled; this integration sends PageView only.
Use Cookie settings at the bottom left to allow or reject marketing cookies, or withdraw your choice at any time. We store your choice in your browser for up to 180 days. Rejecting stops future pixel loading and clears accessible Meta cookies set by this integration. Without JavaScript the pixel does not load. Meta processes information under its Privacy Policy. Google Analytics (measurement ID G-F3512YPK40) loads on public information pages only after you separately choose Allow analytics. A marketing-cookie choice does not grant analytics permission. Analytics helps us understand page visits; Google receives browser and network information and may set _ga cookies. The page address we configure excludes query parameters and fragments, and referring addresses are reduced to their origin. Google signals are disabled for Analytics. Separately, you can allow Google Ads measurement (destination AW-18479616359) in Cookie settings. Google can then use ad-click cookies such as _gcl_aw to associate a visit with a purchase. This is not granted by a Meta or Analytics choice. After a recent live subscription purchase, a separate confirmation page checks the initial Stripe invoice and payment before sending its value excluding tax, currency and an opaque transaction identifier to the Google Ads purchase action. We do not send name, email, payment-card or account details through this event. Personalized advertising remains off. No Google advertising script is installed in the account portal or embedded checkout. The confirmation page loads the measurement script only after a verified purchase and Google Ads consent. Refusing or withdrawing measurement does not affect the subscription. Use Cookie settings or the confirmation page to change your choice; accessible Google click cookies are cleared on rejection. Choices are stored locally for up to 180 days. Portal, sign-in and checkout pages are excluded. Use Cookie settings to reject analytics or withdraw it; accessible Google Analytics cookies are then cleared. Your analytics choice is stored locally for up to 180 days. Google processes data under its Privacy Policy. Server logs may still record requests.
The customer portal uses an HttpOnly, Secure, SameSite authentication cookie named aip, valid for up to thirty days. Sign-in links expire after fifteen minutes and can be used only once. Email addresses are processed by Resend to deliver the links.
Retention and security
Customer data is kept while needed to provide the service, meet legal obligations and maintain security. The configured optimization history periods are three months for Start, twelve for Pro, twenty-four for Business and thirty-six for Enterprise. Other records, including backups, may have different retention requirements. Contact us for account closure or deletion requests.
We use encrypted transport and restrict access to customer information. Website scans and reports are associated with the customer profile that owns them. Customer sign-in links are stored as hashes; server-side sessions identify the authenticated account.
International processing
External providers may process information outside the European Economic Area. Where required, applicable transfer safeguards must support that processing. Contact us for information about providers relevant to your service.
Your rights
You may request access, correction, deletion, restriction or portability of your personal data, and object to processing where applicable. You may withdraw consent for optional processing. Write to [email protected]; we respond within one month, subject to applicable legal exceptions.
You can complain to the Swedish Authority for Privacy Protection, Integritetsskyddsmyndigheten (IMY), or your local supervisory authority.
Changes and contact
This page is updated when data processing changes. Material changes affecting customers will be communicated. Contact: [email protected].
Self-service keyword packages
We store the product details, country and language you submit with your order and the resulting keyword suggestions in your customer account. After confirmed payment, those details are sent through OpenRouter to the configured model provider for automatic generation. Your email address and card details are not included in the generation request. Avoid entering personal or confidential information in product details. Order and payment references are retained for delivery, payment reconciliation, support and applicable legal obligations.
Affiliate referral measurement
With your separate permission, TradeDoubler (Grow) uses a first-party referral identifier and public-page/browser information to attribute referrals. A hashed referral identifier can be associated with your Stripe customer before checkout to preserve attribution. After a verified initial subscription payment, it can receive an opaque order reference, the purchase value and currency, and referral information. We do not send your name, email, card details or Stripe identifiers in this conversion. Rewardful-associated purchases are excluded from TradeDoubler conversion issuance. Purchases do not depend on allowing referral measurement. You can withdraw this permission through Cookie settings. Conversion issuance records are retained with payment-related audit records; an issued tracking event does not establish provider acceptance. See TradeDoubler’s privacy policy.
With your separate permission, Rewardful uses a first-party referral cookie and public-page/browser information to identify affiliate referrals. During checkout, a referral identifier can be associated with your Stripe customer. Rewardful can receive the relevant purchase and subscription information through the Stripe account connection to attribute sales and calculate commissions under our program.
You can allow or reject referral measurement through Privacy settings. Rejecting it does not prevent a purchase. Withdrawing permission stops new browser referral tracking and forwarding; it does not automatically erase records already needed for billing or an attributed transaction. The referral cookie follows the expiry configured by the referral service. See Rewardful’s privacy policy for its processing information and contact us using the details on this page about your data rights.