PRIVACY POLICY
Last updated October 26, 2026



This Privacy Notice for VSL STORES E E ( "we," " us," or "our" ), describes how and why we might access, collect, store, use, and/or share (" process" ) your personal information when you use our services ( "Services" ), including when you:
  • Visit our website at https://aiola.app/ or any website of ours that links to this Privacy Notice
  • Download or use the Aiola mobile companion app (iOS or Android), which connects to the Aiola desktop app on your Mac or PC over your local network or Tailscale

MOBILE APP
The free Aiola mobile app is a companion to the Aiola desktop application. It uses the same account as the desktop app and lets you control AI coding agents, git, and the terminal over LAN or Tailscale. Data processed specifically by the mobile app includes:
  • Account & authentication. Email address and user ID via Supabase Auth (email one-time codes). Google OAuth may provide profile information such as name and email from the identity provider. Continue with Apple is also available on desktop. If you use Sign in with Apple and choose to hide your email, we only ever receive Apple’s private relay address, never your real one.
  • Camera & photos. Camera access to scan a connection QR code and to attach photos to a chat. Photo library access to attach images from your device to a chat. Images you attach are sent to your Aiola desktop server for the chat/agent session you initiate.
  • Microphone (voice dictation). With permission, the mobile composer uses the device's speech recognizer, preferring on-device recognition where available and allowing a network recognizer fallback under the platform's handling. If the native recognizer is unavailable, the app can upload recorded audio directly to your paired desktop for local transcription. The resulting text is used for the message you choose to send.
  • Local network & connection data. Local network IP addresses, Tailscale hostnames, and connection URLs you enter or scan are stored on your device so the app can reconnect to your desktop server. This connection data stays on-device and is used only to reach your own Aiola instance. Chat, attachments, diffs, terminal operations, and other phone-to-desktop session traffic travel directly to the reachable desktop over LAN or Tailscale, without an Aiola relay. A running desktop server and configured network access are required. Plain LAN HTTP is not encrypted; Tailscale provides an encrypted route. Account sign-in, diagnostics, and optional push delivery use the separate services described in this notice.
  • Push notifications & Live Activities. To deliver notifications when an agent finishes, needs approval, asks a question, or fails, the app sends a random install identifier (an install UUID) generated and stored on your device and an Expo push token to your own paired Aiola desktop server. The server stores these with your Aiola account ID, device name, platform, and notification preferences. These notification registrations are used only to deliver the notifications you enable, not for advertising or tracking. Alerts are delivered through Expo’s push service and Apple Push Notification service (APNs) on iOS or Firebase Cloud Messaging (FCM) on Android. Your desktop sends the push token and notification content to these delivery providers; content can include thread titles, agent reply previews, approval details, and questions. On supported iPhones, the app also sends APNs Live Activity tokens to your desktop for delivery directly through APNs. On sign-out and account deletion, the app sends authenticated removal requests for its notification registrations to your paired desktop servers before clearing the local session. Registrations are removed when those requests succeed. Removal requires a reachable server and a valid session; a failed cleanup does not prevent sign-out or account deletion. The install identifier itself remains in local device storage for future registrations. Demo mode uses local notifications and does not register with a desktop or the remote push services.
  • Crash & performance diagnostics. Crash and performance diagnostic reporting is always on across every plan, including lifetime licenses. Crashes, unhandled errors, unexpected exits, memory warnings, and the worst UI stall per session are reported automatically, with sanitized error text, screen, device model, OS version, and app version so we can diagnose and fix defects. The report schema contains no email, account user ID, messages, prompts, code, or file contents. Diagnostic strings are sanitized, but redaction cannot guarantee that arbitrary error text never contains personal information. Reports are used to diagnose and fix defects. The uploader sanitizes diagnostic text and does not include account identity fields or workspace content fields. The connection IP may be used to derive approximate location, like other hosted logs; the desktop anonymous-client suppression described below should not be assumed for mobile reports. There is no in-app switch to turn this off, and the former Share diagnostics setting was removed. Users who object can contact aiolahq@gmail.com or stop using the app / delete their account.
The mobile app does not show ads and does not include third-party advertising or analytics SDKs for tracking across other apps or websites. Crash and performance diagnostics are collected by our own first-party reporting service, not by a third-party SDK. Session tokens and connection preferences are stored locally on the device (for example via on-device storage) to keep you signed in and connected.
  • Engage with us in other related ways, including any marketing or events
Questions or concerns? This Privacy Notice explains your rights and choices. Aiola is the controller for its own account, billing, support, and service-diagnostic processing. For end-user telemetry collected from a customer's product, that customer is the controller and Aiola processes the data on its behalf to provide the hosted service. Contact aiolahq@gmail.com with privacy questions.


SUMMARY OF KEY POINTS
This summary provides key points from our Privacy Notice, but you can find out more details about any of these topics by clicking the link following each key point or by using our  table of contents  below to find the section you are looking for.

What personal information do we process? When you visit, use, or navigate our Services, we may process personal information depending on how you interact with us and the Services, the choices you make, and the products and features you use. Learn more about  personal information you disclose to us .

Do we process sensitive personal information? We do not request it for account registration. Customer-controlled submissions can contain personal information; see the customer product-data disclosures below.

Do we collect any information from third parties? Yes. We receive account information from sign-in providers, billing information from Stripe, data from integrations you connect, and telemetry or feedback from your end users when you install our tracker, SDK, or widget.

How do we process your information? We process your information to provide, improve, and administer our Services, communicate with you, for security and fraud prevention, and to comply with law. We may also process your information for other purposes with your consent. We process your information only when we have a valid legal reason to do so. Learn more about  how we process your information .

In what situations and with which types of parties do we share personal information? We may share information in specific situations and with specific categories of third parties. Learn more about  when and with whom we share your personal information .

How do we keep your information safe? We have adequate organizational and technical processes and procedures in place to protect your personal information. However, no electronic transmission over the internet or information storage technology can be guaranteed to be 100% secure, so we cannot promise or guarantee that hackers, cybercriminals, or other unauthorized third parties will not be able to defeat our security and improperly collect, access, steal, or modify your information. Learn more about  how we keep your information safe .

What are your rights? Depending on where you are located geographically, the applicable privacy law may mean you have certain rights regarding your personal information. Learn more about  your privacy rights .

How do you exercise your rights? The easiest way to exercise your rights is by submitting a  data subject access request , or by contacting us. We will consider and act upon any request in accordance with applicable data protection laws.

Want to learn more about what we do with any information we collect?  Review the Privacy Notice in full .


TABLE OF CONTENTS


1. WHAT INFORMATION DO WE COLLECT?

Personal information you disclose to us

 In Short:   We collect personal information that you provide to us.

We collect personal information that you voluntarily provide to us when you register on the Services,  express an interest in obtaining information about us or our products and Services, when you participate in activities on the Services, or otherwise when you contact us.

Personal Information Provided by You. The personal information that we collect depends on the context of your interactions with us and the Services, the choices you make, and the products and features you use. The personal information we collect may include the following:
  • email addresses
Sensitive Information. Aiola does not request sensitive personal information for account registration. Customer-supplied logs, event properties, feedback text, and attachments can contain personal information; customers must configure collection appropriately and avoid sending unnecessary sensitive data.

Payment Data. Stripe handles checkout and payment card details. Aiola does not store full card numbers or card security codes. We process account-linked Stripe customer and subscription identifiers, plan and trial status, and billing transaction information to manage access and purchases. See Stripe's Privacy Policy.

Account and sign-in data. Supabase Auth processes your email address, account identifier, and authentication sessions. You can use email one-time codes or Google OAuth; desktop also offers Continue with Apple. These providers may supply name, email, and profile information. If you select Apple's Hide My Email, we receive its relay address. Account profile and onboarding information includes the answers you provide about how you found Aiola and what describes you. See HOW DO WE HANDLE YOUR SOCIAL LOGINS?.

All personal information that you provide to us must be true, complete, and accurate, and you must notify us of any changes to such personal information.

Information automatically collected

 In Short:   Some information — such as your Internet Protocol (IP) address and/or browser and device characteristics — is collected automatically when you visit our Services.

Our public website uses Aiola's Analytics tracker and App Logs reporting to understand visits and diagnose site errors. Depending on the feature and settings, hosted requests include connection IP, browser/device and language information, page paths, referrers, timestamps, events, and diagnostic context. These records can contain identifiers and personal information; they are not all anonymous. Desktop workspace files and chat history are not uploaded for general usage analytics. Desktop and mobile diagnostics and customer-installed trackers have the separate collection rules below.

The information we collect includes:
  • Log and Usage Data. Website and hosted-feature requests may include timestamps, page paths, referrers, event properties, connection IP, error reports, and request context. The categories differ between website monitoring, desktop diagnostics, mobile diagnostics, and telemetry a customer sends from its own product; the disclosures below explain those differences.
  • Device Data. Browser/device characteristics, operating system, app/build version, and available diagnostic measurements are processed where included by the relevant tracker, SDK, or diagnostic uploader. Paired-device names, platform, connection address, presence, and credential metadata are also used by your desktop server to manage phone access. Pairing credentials and single-use connection tickets are stored as hashes by that server and can be revoked in Connections.
  • Location Data. Connection IP addresses may be used for approximate country, region, or city information in hosted analytics and logs, depending on the collection path and settings. We do not use GPS to collect precise device location. For App Logs sent with anonymous_client: true, stored user IP and geography fields are blank; this does not remove the technical need to handle an IP address during network delivery or rate limiting.

Local workspace and model-provider boundaries

Repositories, code, threads, tasks, notes, and local automations are stored on your machine in SQLite and project files. When you run a coding agent, prompts, file context, and tool output go from your machine directly to your selected provider: Anthropic for Claude Code, OpenAI for Codex, Cursor, xAI for Grok CLI, Google for Antigravity, or the provider configured in OpenCode. This uses your own subscription or provider access. Aiola does not proxy, store, or resell that model traffic. Local thread history is separate from Aiola's hosted services. Optional cloud features and push delivery have the separate data flows described here.

Automatic desktop diagnostics

Diagnostic reporting in the desktop app is always on across every plan, including lifetime licenses; the former Diagnostics setting was removed, and there is no in-app switch to turn this off. Provider and local-server failures are reported automatically (redacted error message, provider, CLI version, model, error class, phase, elapsed time, app version, OS; thread/request IDs are salted hashes; workspace/home paths, URL query strings, recognised credentials and emails are redacted). These failure reports are designed to be anonymous and use the App Logs anonymous_client mode, which leaves stored user-IP and geography fields blank. Desktop interface errors (renderer errors, failed requests, console errors, breadcrumbs) are also reported and are linked to the signed-in account (account user ID and email) so support can follow up. Users who object can contact aiolahq@gmail.com or stop using the app / delete their account. Redaction reduces disclosure risk; avoid including secrets in error messages.

Hosted data from customers' products

Customers install Aiola's Analytics tracker, App Logs SDK, or Feedback widget in their own products. Aiola ingests and stores the resulting end-user data through its cloud services, including Supabase and Tinybird, with Cloudflare handling gateway traffic and source-map storage. The customer determines what to collect and is the controller; Aiola is the processor providing the hosted service. Customers are responsible for their end users' privacy notices, lawful basis, and required consents. If you are an end user of such a product, contact its operator about your data.
Analytics: pageviews, custom events and event properties, page paths and queries, hosts, titles, referrers, timestamps, language, screen/browser/device information, visitor and session identifiers, duration, and any identity or traits the customer explicitly supplies. Connected Stripe revenue and Google Search Console or Bing metrics can enrich the reports. Approximate geography depends on the gateway connection. The tracker uses aiola_visitor_id (365 days) and aiola_session_id (sliding 30 minutes), with a local-storage identity fallback. Customer server integrations can also send crawler request paths, host, user agent, country, and response status for crawler analytics. These request records are separate from the public crawler directory.
App Logs: errors, warnings, exception messages and stack frames, breadcrumbs, request URL/method/headers/query/body, tags, user context supplied by the customer (such as ID, email, username, or IP), device/browser/OS/runtime context, environment, release, and uploaded source maps. Sensitive authentication headers are stripped and payload size limits apply. The anonymous_client: true option blanks stored user IP and geography; it does not automatically anonymize arbitrary text, tags, or user identifiers supplied by the customer.
Feedback: issue or feature-request type, title, description, configured form answers, optional email/device/URL information, and image attachments. The default issue form requires email; customers can change the schema. The customer can view, triage, and delete submissions within its account.

Connected integrations and credentials

GitHub repository operations use the GitHub CLI and Git/SSH credential configuration on your machine. GitHub issues, pull requests, checks, and repository data are accessed for the repositories you connect. GitHub credentials remain with that local tooling; manage or revoke them through GitHub and the relevant local credential configuration. Search Console uses Google OAuth access and refresh tokens; Bing Webmaster Tools uses an API key. Stripe revenue tracking uses a per-project restricted API key and webhook signing secret. Those hosted integration secrets are stored encrypted in Supabase Vault, with ownership-checked access. Disconnect the relevant account or site in Workspace Settings → Integrations to remove the stored connection secrets; provider-side authorizations and keys can also be revoked with the provider. Disconnecting Stripe removes the stored key and webhook secret and stops revenue webhooks.

Hosted MCP authorization

The hosted MCP server uses Supabase OAuth 2.1 bearer tokens and browser sign-in/consent. Its advertised identity scopes are openid, email, and profile; the consent screen shows the requested permissions and client. An authorized client such as Claude, ChatGPT, or Cursor can read hosted analytics, logs, feedback, and search data for projects available to your account, and change App Log or Feedback statuses. It cannot use these tools to delete data or change your account. App-log request data and user email/IP are omitted by default, with additional nested redaction; a client requesting include_request_data: true can receive the stored event without that redaction. Only authorize clients you intend to receive that data. Their handling of returned data is subject to their own policies. This is a hosted product-data connection, separate from local coding-provider model traffic.

Public directory and discovery

Our public crawler directory publishes provider and crawler identities, user-agent strings, official IP-range information, and control guidance; it does not publish customer telemetry or personal data about individual visitors. Search engines and AI assistants may read, index, and use our public marketing and documentation content as permitted by robots.txt and its Content-Signal declarations, including search, answers, and training where allowed. Private account content is outside those permissions. Our IndexNow script submits public sitemap URLs to help search engines discover changed pages; it does not submit account records or customer telemetry.

2. HOW DO WE PROCESS YOUR INFORMATION?

 In Short:  We process your information to provide, improve, and administer our Services, communicate with you, for security and fraud prevention, and to comply with law. We process the personal information for the following purposes listed below. We may also process your information for other purposes only with your prior explicit consent.
We process account and entitlement data for sign-in, licenses, subscriptions, and trial access; billing data for Stripe checkout and purchase management; diagnostics for reliability and troubleshooting; integration credentials for the connections you enable; and device registrations and notification content for optional push delivery. For customer-controlled Analytics, App Logs, and Feedback, we process end-user data on the customer's behalf to deliver its configured hosted features. Connected MCP clients receive data when acting under your authorization.

We process your personal information for a variety of reasons, depending on how you interact with our Services, including:
  • To facilitate account creation and authentication and otherwise manage user accounts.  We may process your information so you can create and log in to your account, as well as keep your account in working order.

  • To request feedback.  We may process your information when necessary to request feedback and to contact you about your use of our Services.
  • To save or protect an individual's vital interest. We may process your information when necessary to save or protect an individual’s vital interest, such as to prevent harm.

3. WHAT LEGAL BASES DO WE RELY ON TO PROCESS YOUR PERSONAL INFORMATION?

In Short:  We only process your personal information when we believe it is necessary and we have a valid legal reason (i.e. , legal basis) to do so under applicable law, like with your consent, to comply with laws, to provide you with services to enter into or fulfill our contractual obligations, to protect your rights, or to fulfill our legitimate business interests.

If you are located in the EU or UK, this section applies to you.

The General Data Protection Regulation (GDPR) and UK GDPR require us to explain the valid legal bases we rely on in order to process your personal information. As such, we may rely on the following legal bases to process your personal information:
  • Consent.  We may process your information if you have given us permission (i.e. , consent) to use your personal information for a specific purpose. You can withdraw your consent at any time. Learn more about  withdrawing your consent .
  • Legitimate Interests. We may process your information when we believe it is reasonably necessary to achieve our legitimate business interests and those interests do not outweigh your interests and fundamental rights and freedoms. For example, we may process your personal information for some of the purposes described in order to:
  • Understand how our users use our products and services so we can improve user experience
  • Legal Obligations. We may process your information where we believe it is necessary for compliance with our legal obligations, such as to cooperate with a law enforcement body or regulatory agency, exercise or defend our legal rights, or disclose your information as evidence in litigation in which we are involved.
  • Vital Interests. We may process your information where we believe it is necessary to protect your vital interests or the vital interests of a third party, such as situations involving potential threats to the safety of any person.

If you are located in Canada, this section applies to you.

We may process your information if you have given us specific permission (i.e. , express consent) to use your personal information for a specific purpose, or in situations where your permission can be inferred (i.e. , implied consent). You can  withdraw your consent  at any time.

In some exceptional cases, we may be legally permitted under applicable law to process your information without your consent, including, for example:
  • If collection is clearly in the interests of an individual and consent cannot be obtained in a timely way
  • For investigations and fraud detection and prevention
  • For business transactions provided certain conditions are met
  • If it is contained in a witness statement and the collection is necessary to assess, process, or settle an insurance claim
  • For identifying injured, ill, or deceased persons and communicating with next of kin
  • If we have reasonable grounds to believe an individual has been, is, or may be victim of financial abuse
  • If it is reasonable to expect collection and use with consent would compromise the availability or the accuracy of the information and the collection is reasonable for purposes related to investigating a breach of an agreement or a contravention of the laws of Canada or a province
  • If disclosure is required to comply with a subpoena, warrant, court order, or rules of the court relating to the production of records
  • If it was produced by an individual in the course of their employment, business, or profession and the collection is consistent with the purposes for which the information was produced
  • If the collection is solely for journalistic, artistic, or literary purposes
  • If the information is publicly available and is specified by the regulations
  • We may disclose de-identified information for approved research or statistics projects, subject to ethics oversight and confidentiality commitments

4. WHEN AND WITH WHOM DO WE SHARE YOUR PERSONAL INFORMATION?

In Short:  We may share information in specific situations described in this section and/or with the following categories of third parties.
Providers used for service delivery include Supabase for authentication, account and hosted application data, OAuth and integration-secret storage; Tinybird for analytics and log-event storage and queries; Cloudflare for gateway processing and source-map storage; Stripe for checkout and billing; and Expo, APNs and FCM for enabled push delivery. Connected GitHub, Google Search Console, Bing and Stripe integrations exchange the information needed for the features you enable. Authorized MCP clients receive the hosted project data they request. Each provider receives the information needed for the functions described in this notice.

Vendors, Consultants, and Other Third-Party Service Providers. We may share your data with third-party vendors, service providers, contractors, or agents ( " third parties " ) who perform services for us or on our behalf and require access to such information to do that work.

The categories of third parties we may share personal information with are as follows:
  • Payment Processors
  • AI clients you authorize to access hosted project data

We also may need to share your personal information in the following situations:
  • Business Transfers. We may share or transfer your information in connection with, or during negotiations of, any merger, sale of company assets, financing, or acquisition of all or a portion of our business to another company.

5. DO WE OFFER ARTIFICIAL INTELLIGENCE-BASED PRODUCTS?

In Short:  We offer products, features, or tools powered by artificial intelligence, machine learning, or similar technologies.

As part of our Services, we offer products, features, or tools powered by artificial intelligence, machine learning, or similar technologies (collectively, " AI Products " ). These tools are designed to enhance your experience and provide you with innovative solutions. The terms in this Privacy Notice govern your use of the AI Products within our Services.

Use of AI Technologies

Aiola orchestrates locally installed Claude Code (Anthropic), Codex (OpenAI), Cursor, Grok CLI (xAI), OpenCode (your configured provider), and Antigravity (Google). You supply your own subscription or provider access. Prompts, file context, and tool output travel directly from your machine to that provider under its terms and privacy policy. Aiola does not proxy, store, or resell this model traffic and does not resell compute or add API-key markup. Local thread history remains on your machine. You must comply with your selected provider's terms.

Our AI Products

Our AI Products are designed for the following functions:
  • AI applications
  • AI development

How We Process Your Data Using AI

Your selected model provider controls its handling of the prompts and context it receives under its own policies. If you authorize a hosted MCP client or start an AI analysis of customer analytics, logs, or feedback, the requested project data becomes context for that client or your chosen provider. This is a deliberate product-data disclosure through the feature you use; it does not route local coding-provider inference traffic through Aiola. Review the data and permissions before sharing sensitive customer information.

6. HOW DO WE HANDLE YOUR SOCIAL LOGINS?

In Short:  If you choose to register or log in to our Services using a social media account, we may have access to certain information about you.

Supabase Auth supports email one-time codes and Google OAuth for Aiola accounts. Desktop also offers Continue with Apple. Depending on the provider and your choices, account information may include your name, email, and profile image. Apple Hide My Email supplies a relay address. Apple authorization credentials used for account-deletion revocation are handled as described in the retention section.

We will use the information we receive only for the purposes that are described in this Privacy Notice or that are otherwise made clear to you on the relevant Services. Please note that we do not control, and are not responsible for, other uses of your personal information by your third-party social media provider. We recommend that you review their privacy notice to understand how they collect, use, and share your personal information, and how you can set your privacy preferences on their sites and apps.

7. HOW LONG DO WE KEEP YOUR INFORMATION?

In Short:  We keep your information for as long as necessary to fulfill the purposes outlined in this Privacy Notice unless otherwise required by law.

We retain account and hosted feature data for providing the Services, subject to deletion controls and applicable legal requirements. Account deletion removes your login identity, profile/onboarding data, registered projects, analytics and log/crawler events, feedback and attachments, uploaded source maps, API keys, connected integrations, licenses, and Stripe customer record. A minimal deletion receipt (account ID, timestamps, and removal counts) is retained for 30 days, including an Apple credential only if needed to finish a pending authorization revocation; the receipt is then purged. Stripe retains invoices and payment records required for tax and accounting under its own rules. Local repository files are separate from hosted account records.

When we have no ongoing legitimate business need to process your personal information, we will either delete or anonymize such information, or, if this is not possible (for example, because your personal information has been stored in backup archives), then we will securely store your personal information and isolate it from any further processing until deletion is possible.

Customers can clear Analytics data, disable further collection while preserving existing data, delete Feedback and its attachments, and manage App Logs and source maps. The documented App Logs cleanup removes closed or ignored groups 30 days after their last event; open, in-progress, and human-review groups are not removed by that cleanup. Other hosted data is retained to provide the enabled service, subject to deletion controls and applicable legal requirements. See account deletion for removal of account-associated hosted data.

8. HOW DO WE KEEP YOUR INFORMATION SAFE?

In Short:  We aim to protect your personal information through a system of organizational and technical security measures.

We have implemented appropriate and reasonable technical and organizational security measures designed to protect the security of any personal information we process. However, despite our safeguards and efforts to secure your information, no electronic transmission over the Internet or information storage technology can be guaranteed to be 100% secure, so we cannot promise or guarantee that hackers, cybercriminals, or other unauthorized third parties will not be able to defeat our security and improperly collect, access, steal, or modify your information. Although we will do our best to protect your personal information, transmission of personal information to and from our Services is at your own risk. You should only access the Services within a secure environment.

9. DO WE COLLECT INFORMATION FROM MINORS?

In Short:  We do not knowingly collect data from or market to children under 18 years of age or the equivalent age as specified by law in your jurisdiction .

We do not knowingly collect, solicit data from, or market to children under 18 years of age or the equivalent age as specified by law in your jurisdiction , nor do we knowingly sell such personal information. By using the Services, you represent that you are at least 18 or the equivalent age as specified by law in your jurisdiction . If we learn that personal information from users less than 18 years of age or the equivalent age as specified by law in your jurisdiction has been collected, we will deactivate the account and take reasonable measures to promptly delete such data from our records. If you become aware of any data we may have collected from children under age 18 or the equivalent age as specified by law in your jurisdiction , please contact us at aiolahq@gmail.com .

10. WHAT ARE YOUR PRIVACY RIGHTS?

In Short:   Depending on your state of residence in the US or in some regions, such as the European Economic Area (EEA), United Kingdom (UK), Switzerland, and Canada , you have rights that allow you greater access to and control over your personal information.   You may review, change, or terminate your account at any time, depending on your country, province, or state of residence.

In some regions (like the EEA, UK, Switzerland, and Canada ), you have certain rights under applicable data protection laws. These may include the right (i) to request access and obtain a copy of your personal information, (ii) to request rectification or erasure; (iii) to restrict the processing of your personal information; (iv) if applicable, to data portability; and (v) not to be subject to decisions based solely on machine processing. If a decision that produces legal or similarly significant effects is made solely by machine processing, we will inform you, explain the main factors, and offer a simple way to request human review. In certain circumstances, you may also have the right to object to the processing of your personal information. You can make such a request by contacting us by using the contact details provided in the section " HOW CAN YOU CONTACT US ABOUT THIS NOTICE? " below.

We will consider and act upon any request in accordance with applicable data protection laws.
 
If you are located in the EEA or UK and you believe we are unlawfully processing your personal information, you also have the right to complain to your Member State data protection authority or  UK data protection authority .

If you are located in Switzerland, you may contact the Federal Data Protection and Information Commissioner .

Withdrawing your consent: If we are relying on your consent to process your personal information, which may be express and/or implied consent depending on the applicable law, you have the right to withdraw your consent at any time. You can withdraw your consent at any time by contacting us by using the contact details provided in the section " HOW CAN YOU CONTACT US ABOUT THIS NOTICE? " below .

However, please note that this will not affect the lawfulness of the processing before its withdrawal nor, when applicable law allows, will it affect the processing of your personal information conducted in reliance on lawful processing grounds other than consent.

Opting out of marketing and promotional communications:   You can unsubscribe from our marketing and promotional communications at any time by clicking on the unsubscribe link in the emails that we send, or by contacting us using the details provided in the section " HOW CAN YOU CONTACT US ABOUT THIS NOTICE? " below. You will then be removed from the marketing lists. However, we may still communicate with you — for example, to send you service-related messages that are necessary for the administration and use of your account, to respond to service requests, or for other non-marketing purposes.

Account Information

If you would at any time like to review or change the information in your account or terminate your account, you can:
  • Log in to your account settings and update your user account.
Use the account deletion instructions in mobile or desktop Settings, or email aiolahq@gmail.com from the account address if you cannot access the apps. Email requests are ownership-verified and completed within 30 days. Deletion and the limited retained receipt/payment records are described in Section 7 and on that page.

If you have questions or comments about your privacy rights, you may email us at aiolahq@gmail.com .

11. CONTROLS FOR DO-NOT-TRACK FEATURES

The Analytics tracker has a documented data-do-not-track="true" setting that honors a browser's Do-Not-Track preference when the site operator enables it. Its behavior depends on the operator's tracker configuration. Desktop diagnostic reporting is always on and is not controlled by Do-Not-Track or an in-app setting. For requests about account data, contact aiolahq@gmail.com.
Our own website tracker does not currently enable its optional Do-Not-Track setting. Customers installing the tracker on their own products can enable data-do-not-track="true" to honor browser DNT signals. Desktop and mobile diagnostic reporting is always on, is not controlled by Do-Not-Track or an in-app setting, and does not control website analytics.

12. DO UNITED STATES RESIDENTS HAVE SPECIFIC PRIVACY RIGHTS?

In Short:  If you are a resident of California, Colorado, Connecticut, Delaware, Florida, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah, or Virginia , you may have the right to request access to and receive details about the personal information we maintain about you and how we have processed it, correct inaccuracies, get a copy of, or delete your personal information. You may also have the right to withdraw your consent to our processing of your personal information. These rights may be limited in some circumstances by applicable law. More information is provided below.

Categories of Personal Information We Collect

The table describes categories that may be processed through the features in this notice. Its examples are illustrative, not a claim that every example is collected. Customer-configured content may contain additional categories, so customers must restrict what they send. See WHAT INFORMATION DO WE COLLECT? for the actual data flows.

Category Examples Collected
A. Identifiers
Contact details, such as real name, alias, postal address, telephone or mobile contact number, unique personal identifier, online identifier, Internet Protocol address, email address, and account name
YES — account identifiers, email and connection identifiers
B. Personal information as defined in the California Customer Records statute
Name, contact information, education, employment, employment history, and financial information
YES — account/contact and billing information described above
C . Protected classification characteristics under state or federal law
Gender, age, date of birth, race and ethnicity, national origin, marital status, and other demographic data
Not requested; may appear in customer-supplied content
D . Commercial information
Transaction information, purchase history, financial details, and payment information
YES — subscriptions, purchases and connected revenue data
E . Biometric information
Fingerprints and voiceprints
No biometric identification; voice dictation is described separately
F . Internet or other similar network activity
Browsing history, search history, online behavior , interest data, and interactions with our and other websites, applications, systems, and advertisements
YES — pageviews, events, logs and service usage described above
G . Geolocation data
Device location
YES — approximate IP-based geography where enabled; no GPS collection
H . Audio, electronic, sensory, or similar information
Images and audio, video or call recordings created in connection with our business activities
YES — optional images, attachments and dictation as described above
I . Professional or employment-related information
Business contact details in order to provide you our Services at a business level or job title, work history, and professional qualifications if you apply for a job with us
Not requested; may appear in customer-supplied content
J . Education Information
Student records and directory information
Not requested; may appear in customer-supplied content
K . Inferences drawn from collected personal information
Inferences drawn from any of the collected personal information listed above to create a profile or summary about, for example, an individual’s preferences and characteristics
Not requested; may appear in customer-supplied content
L . Sensitive personal Information Not requested; may appear in customer-supplied content

We may also collect other personal information outside of these categories through instances where you interact with us in person, online, or by phone or mail in the context of:
  • Receiving help through our customer support channels;
  • Participation in customer surveys or contests; and
  • Facilitation in the delivery of our Services and to respond to your inquiries.

Sources of Personal Information

Learn more about the sources of personal information we collect in " WHAT INFORMATION DO WE COLLECT? "

How We Use and Share Personal Information

Learn more about how we use your personal information in the section, " HOW DO WE PROCESS YOUR INFORMATION? "

Will your information be shared with anyone else?

We may disclose your personal information with our service providers pursuant to a written contract between us and each service provider. Learn more about how we disclose personal information to in the section, " WHEN AND WITH WHOM DO WE SHARE YOUR PERSONAL INFORMATION? "

We may use your personal information for our own business purposes, such as for undertaking internal research for technological development and demonstration. This is not considered to be "selling" of your personal information.

Disclosures for service delivery can include account identifiers, billing and subscription information, device and diagnostic information, and the customer content or telemetry required by the enabled feature, as described in Section 4.

The categories of third parties to whom we disclosed personal information for a business or commercial purpose can be found under " WHEN AND WITH WHOM DO WE SHARE YOUR PERSONAL INFORMATION? "

This notice describes disclosures for service delivery, customer-directed integrations, and clients you authorize. The categories and purposes are explained in Sections 1, 2 and 4.

Connected providers receive information needed to deliver the services you use, as described in Section 4.

Hosted processing providers and notification delivery services are identified in Section 4; model-provider traffic goes directly from your machine to your chosen provider.

Your Rights

You have rights under certain US state data protection laws. However, these rights are not absolute, and in certain cases, we may decline your request as permitted by law. These rights include:
  • Right to know whether or not we are processing your personal data
  • Right to access  your personal data
  • Right to correct  inaccuracies in your personal data
  • Right to request the deletion of your personal data
  • Right to obtain a copy  of the personal data you previously shared with us
  • Right to non-discrimination for exercising your rights
  • Right to opt out of the processing of your personal data if it is used for targeted advertising (or sharing as defined under California’s privacy law) , the sale of personal data, or profiling in furtherance of decisions that produce legal or similarly significant effects ( "profiling" )
Depending upon the state where you live, you may also have the following rights:
  • Right to access the categories of personal data being processed (as permitted by applicable law, including the privacy law in Minnesota)
  • Right to obtain a list of the categories of third parties to which we have disclosed personal data (as permitted by applicable law, including the privacy law in California, Delaware, and Maryland )
  • Right to obtain a list of specific third parties to which we have disclosed personal data (as permitted by applicable law, including the privacy law in Minnesota and Oregon )
  • Right to obtain a list of third parties to which we have sold personal data (as permitted by applicable law, including the privacy law in Connecticut)
  • Right to review, understand, question, and depending on where you live, correct how personal data has been profiled (as permitted by applicable law, including the privacy law in Connecticut and Minnesota )
  • Right to limit use and disclosure of sensitive personal data (as permitted by applicable law, including the privacy law in California)
  • Right to opt out of the collection of sensitive data and personal data collected through the operation of a voice or facial recognition feature (as permitted by applicable law, including the privacy law in Florida)

How to Exercise Your Rights

To exercise these rights, you can contact us by submitting a  data subject access request , by emailing us at aiolahq@gmail.com , or by referring to the contact details at the bottom of this document.

To exercise applicable privacy rights, contact aiolahq@gmail.com. Collection settings for customer trackers provide the controls described in this notice; desktop and mobile diagnostic reporting is always on and has no in-app preference setting.

Under certain US state data protection laws, you can designate an authorized agent to make a request on your behalf. We may deny a request from an authorized agent that does not submit proof that they have been validly authorized to act on your behalf in accordance with applicable laws.

Request Verification

Upon receiving your request, we will need to verify your identity to determine you are the same person about whom we have the information in our system. We will only use personal information provided in your request to verify your identity or authority to make the request. However, if we cannot verify your identity from the information already maintained by us, we may request that you provide additional information for the purposes of verifying your identity and for security or fraud-prevention purposes.

If you submit the request through an authorized agent, we may need to collect additional information to verify your identity before processing your request and the agent will need to provide a written and signed permission from you to submit such request on your behalf.

Appeals

Under certain US state data protection laws, if we decline to take action regarding your request, you may appeal our decision by emailing us at aiolahq@gmail.com . We will inform you in writing of any action taken or not taken in response to the appeal, including a written explanation of the reasons for the decisions. If your appeal is denied, you may submit a complaint to your state attorney general.

California "Shine The Light" Law

California Civil Code Section 1798.83, also known as the "Shine The Light" law, permits our users who are California residents to request and obtain from us, once a year and free of charge, information about categories of personal information (if any) we disclosed to third parties for direct marketing purposes and the names and addresses of all third parties with which we shared personal information in the immediately preceding calendar year. If you are a California resident and would like to make such a request, please submit your request in writing to us by using the contact details provided in the section " HOW CAN YOU CONTACT US ABOUT THIS NOTICE? "

13. DO WE MAKE UPDATES TO THIS NOTICE?

In Short:  Yes, we will update this notice as necessary to stay compliant with relevant laws.

We may update this Privacy Notice from time to time. The updated version will be indicated by an updated "Revised" date at the top of this Privacy Notice. If we make material changes to this Privacy Notice, we may notify you either by prominently posting a notice of such changes or by directly sending you a notification. We encourage you to review this Privacy Notice frequently to be informed of how we are protecting your information.

14. HOW CAN YOU CONTACT US ABOUT THIS NOTICE?

If you have questions or comments about this notice, you may contact us by post at:

VSL STORES E E
Attaleias 14
Patra 26334
Greece

15. HOW CAN YOU REVIEW, UPDATE, OR DELETE THE DATA WE COLLECT FROM YOU?

Depending on applicable law, you may have rights to access, correct, receive a copy of, or delete your personal information and to withdraw consent. Contact aiolahq@gmail.com to exercise these rights. Follow the account deletion instructions to delete your account. End users of a customer's product should contact that product's operator about customer-controlled telemetry.