Chapter I — General provisions
This Privacy Policy governs the processing of personal data in connection with AI Scan, a service operated by UAB "Taikomasis dirbtinis intelektas" (company code 304845429, registered office in the Republic of Lithuania, address Architektų g. 9, Lazdijų k., Lazdijų r.) ("AAI Labs," "we"). It supplements the AAI Labs company Privacy Policy available at www.aai-labs.com/en/privacy-policy; for matters specific to AI Scan, this policy governs. We process personal data in accordance with Regulation (EU) 2016/679 (the "GDPR") and applicable Lithuanian law.
The service, in brief: a company (the "Client") commissions a scan of its operations. An AI agent conducts short conversational interviews with the Client's employees, by text or voice note. The resulting analysis is delivered to the Client as a report on a web platform.
Chapter II — Controller and processor roles
AI Scan involves distinct categories of data subject whose data is governed by different roles. Identifying which applies to you determines how your rights are exercised.
- Clients (the purchasing company and the individuals using the platform on its behalf): AAI Labs is controller of account, contact, billing and platform-usage data.
- Employees of a Client whose data is processed through the interviews: the Client is the controller and AAI Labs acts as processor on the Client's documented instructions, under a written data processing agreement ("DPA") concluded before any such processing begins. The Client determines that the scan occurs, its purpose, and the lawful basis for processing its workforce's data; AAI Labs executes the scan on the Client's behalf.
This allocation is definitive for the purposes of this policy and is mirrored in the DPA between AAI Labs and each Client, accepted on the AI Scan platform before scan setup. Where the two documents address the same matter, they are drafted to be consistent.
Chapter III — Interview data
What is processed. The content of conversations between the employee and the AI Scan agent, including voice notes, together with the participant's role and department.
Role and basis. The Client is controller and determines the purpose and lawful basis; AAI Labs processes only on the Client's documented instructions.
Identifiers. Participants interviewed in Slack or Microsoft Teams are identified by their platform user ID. Their names are not stored; they appear only in the Client's view, fetched from the Client's own workspace. For participants interviewed in our web app, we store their email address to send invitations and give access.
What your employer sees. Your employer can see whether you took part, completed the interview or opted out, and when. It cannot see what you said.
Pseudonymisation. Answers are stored against a participant identifier and role or department, not a name. The AI processes answers as written, so any name a participant types, their own or someone else's, is part of the text it receives. Names are removed from quotations used in the report. We do not represent that anonymity is absolute: within a small team a particular example may remain recognisable.
Summaries. To prepare the report, the AI summarises each person's interview. These summaries are not shown to your employer and are not used to evaluate you.
Voice notes. Where a participant sends a voice note, it is transcribed by a sub-processor (Chapter V) and the transcript is handled as interview data. The audio is not kept. Only the transcript is stored.
Opting out. If you opt out, the agent stops contacting you. What you have already said may still be used, combined with other people's answers, in the report.
Retention and storage. Interview data is stored in the EU and kept until the Client asks us to delete it. When the Client asks us to, or when it stops using the service, we delete or return its data, as the Client chooses; remaining copies are deleted except where law requires otherwise.
Incidental special-category data. The conversational format means a participant may volunteer information falling within Article 9 GDPR. The agent asks only about participants' work and does not ask for such information; responsibility for the lawful basis of any incidental processing rests with the Client as controller.
Chapter IV — Client, account and billing data
Name, work email, company, role and platform-usage data of platform users are processed to provide and secure the service, under Article 6(1)(b) and 6(1)(f) GDPR. Where payment is taken, transaction data is processed under Article 6(1)(b) and 6(1)(c). Online purchases are handled by our merchant of record, Paddle (Paddle.com Market Limited and its affiliates), which acts as an independent controller of the payment data it collects; Paddle processes your card details and we do not receive or store them. Details you send us to request an invoice (such as company name, billing address, VAT number and purchase order number) are processed to prepare and issue that invoice through Paddle, under Article 6(1)(b) GDPR. Retention follows the periods in our company policy for service and accounting records.
Chapter V — AI models and sub-processors
AI Scan uses third-party providers as sub-processors to deliver the service: AI services to conduct interviews and analyse data, transcription for voice notes, hosting, and email delivery. Each acts under a data processing agreement and only on our instructions. The AI providers we use do not keep Client data after processing it and do not use it to train AI models. Neither does AAI Labs.
A current list of sub-processors is available to Clients on request. We give notice of new or replacement sub-processors as set out in the DPA.
Chapter VI — Transfers outside the EU
Some of our sub-processors are based outside the European Union, including in the United States. For these transfers we meet Articles 44–49 GDPR, relying on an adequacy decision or standard contractual clauses with appropriate supplementary measures as required.
Chapter VII — Security
Connections to AI Scan, and from AI Scan to the providers it uses, are encrypted in transit (HTTPS/TLS). The service runs on servers in the EU (Germany); transfers to sub-processors outside the EU are described in Chapter VI. Production systems can be reached only through a restricted access point, and only authorised AAI Labs staff are given access. Each Client's data is accessible only to that Client and to the AAI Labs staff who operate the service.
Chapter VIII — Third-party disclosure
Personal data may be provided to: sub-processors delivering the service (described in Chapter V, each under a DPA, only as necessary); our merchant of record, Paddle, in connection with the sale, payment processing, and tax compliance and invoicing for online purchases, together with the purchase attribution record described in Chapter IX; our analytics provider, PostHog (hosted in the EU), only where you have accepted analytics; our hosting and security provider, Cloudflare; the Client, in respect of the analysis it commissions as controller; and competent authorities, courts or law enforcement where required by law.
Chapter IX — Cookies, analytics and checkout scripts
Cookies are small text files stored on your device when you visit a website. Similar technologies, such as browser local storage, work the same way. They let a site function, stay secure, and help us understand how visitors use it. This chapter describes the cookies, similar technologies and third-party scripts used on scan.aai-labs.com.
Categories we use:
- Strictly necessary. Required for the site to load, stay secure, and remember your cookie choice. They do not require consent and cannot be switched off, but we disclose them here.
- Analytics (statistics). Help us understand how visitors use the site so we can improve it. Used only after you accept through our cookie banner. If you reject, or do not make a choice, no analytics data is collected and nothing is stored on your device apart from the record of your choice. You can change or withdraw your consent at any time through Cookie settings in the footer of every page. Withdrawing stops further collection and removes the analytics cookie and local storage from your browser.
We do not use advertising or marketing cookies, and we do not sell personal data.
Strictly necessary:
| Name | Purpose | Provider | Type | Duration |
|---|---|---|---|---|
__cf_bm | Bot management and bot detection to protect the site. | Cloudflare, our hosting and security provider | Cookie | ~30 minutes |
cf_clearance | Records that a visitor passed a security challenge. Set only if a visitor is challenged. | Cloudflare | Cookie | Up to 24 hours (session) |
__cf_bm (on paddle.com) | Bot protection for Paddle's checkout script, which the home page loads to show prices (see "Checkout and pricing scripts" below). | Paddle, via Cloudflare | Cookie | ~30 minutes |
aisn_consent | Remembers whether you accepted or rejected analytics, so the banner is not shown again. | AI Scan | Local storage | Until browser storage is cleared |
__ph_opt_in_out_phc_... | PostHog's record of the same choice, written when you accept or reject. | PostHog | Local storage | Until browser storage is cleared |
Analytics (only after you accept, via PostHog):
| Name | Purpose | Provider | Type | Duration |
|---|---|---|---|---|
ph_phc_..._posthog | Stores an anonymous device/user ID (distinct_id), session ID, and feature-flag state. | PostHog | Cookie | ~12 months |
ph_phc_..._posthog | Same values as above, held in browser storage. | PostHog | Local storage | Until browser storage is cleared |
What analytics records. We use PostHog (hosted in the EU) to understand how visitors use the site. After you accept, PostHog records:
- page views and page exits, and which sections of the home page you scroll to;
- clicks and interactions with buttons, links and forms, including our main calls to action (for example, booking a scan, requesting an invoice, requesting pricing, logging in, and contacting us);
- page performance measurements;
- the steps of a purchase: opening the checkout, entering your details, the type of payment method chosen (for example, card or PayPal), and whether the payment was attempted, failed or completed, together with the package, currency and price, the country of your billing address, and whether a business or VAT number was entered. Card details, your name, email address and billing address are never sent to our analytics;
- technical properties collected automatically, including approximate location derived from your IP address (country, region, city), browser, operating system, device type, referring page, page address, and any campaign tags in the link you arrived through.
If you have accepted analytics and submit our contact form, we associate the information you provide, including your email address, name and company, with your analytics record, so we can connect an enquiry to the visit it came from. Your email address is used as the identifier for this record. If you have not accepted analytics, we do not do this.
The legal basis for analytics is your consent under Article 6(1)(a) GDPR. You can withdraw it at any time through Cookie settings.
Attributing purchases to marketing channels. When you open the checkout, we send Paddle, together with your order, a short record of how you arrived: the campaign tags in the link you arrived through (such as utm_source and utm_campaign), the domain of the website that referred you, the page you first landed on, and your analytics choice. If you accepted analytics, we also send your analytics ID, so the purchase can be connected to your visit. Paddle stores this with the transaction and returns it to us, which lets us see which marketing channels lead to purchases. If you have not accepted analytics, the record does not contain your analytics ID and is not connected to your browsing. Nothing is stored on your device for this. The legal basis is our legitimate interest in knowing which channels bring customers (Article 6(1)(f) GDPR). You can object at any time by contacting us (Chapter XI).
We may also record completed purchases and invoice payments in our analytics from our own systems. Such a record is connected to your analytics ID only if you accepted analytics. Otherwise it carries no identifier other than the transaction reference.
Checkout and pricing scripts. To show prices in your local currency, the home page loads Paddle's checkout script (Paddle.js) from Paddle's servers when it opens, before you make any cookie choice. To work out your country and currency, it sends your IP address to Paddle. Paddle.js also loads a Paddle script from profitwell.com (part of Paddle's Retain service, which we do not use), and Paddle's hosting sets the bot-protection cookie listed above. Paddle operates these under its own Privacy Notice.
Site performance. Our hosting provider, Cloudflare, measures page-load performance and visit counts in aggregate (Cloudflare Web Analytics). It does not set cookies.
Booking a call takes you to OnceHub, a separate scheduling website. We do not connect bookings made there to our analytics.
For how we handle the personal data you submit through forms or by email once we receive it, see Chapter IV.
Chapter X — Rights of data subjects
You hold the GDPR rights to be informed, of access, rectification, erasure, restriction, objection, portability, and not to be subject to solely automated decisions with legal or similarly significant effect.
Exercising them depends on role. Clients exercise their rights with us directly. Employees whose interview data is processed should direct requests concerning that data to their employer as controller; AAI Labs, as processor, will assist the employer in responding, and will route any request received directly to the appropriate controller. Requests concerning data for which AAI Labs is controller may be made to us directly.
We respond within one month, extendable by two further months for complex or numerous requests. You may complain to the State Data Protection Inspectorate of the Republic of Lithuania, your local supervisory authority, or a court.
Chapter XI — Contact
Questions or requests concerning personal data in connection with AI Scan may be addressed to our data protection officer at [email protected]. Email requests should be electronically signed for identification. Employees with questions about why a scan was authorised should contact their employer.
