Privacy Policy
Last updated: 29 October 2026
This Privacy Policy explains what personal data Nolatech Ltd (“we”, “us”) collects through the SpanDock website at https://spandock.com, your account, and the license checks made by the SpanDock software, and how we use it.
The SpanDock software is self-hosted: the telemetry it processes stays on your machines, and we never receive that telemetry, your prompts, your code, or tool output.
Controller: Nolatech Ltd, Cyprus
Privacy contact: privacy@spandock.com
Data protection officer: A data protection officer has not been appointed.
1. What we collect and why
1.1 Account data
When you sign up, we collect your email address and, if you give it, your name. We record your sign-in method (email one-time code, passkey, optional password, or third-party sign-in such as Google or GitHub). If you sign in with a third party, we receive basic profile data they provide (typically name, email, and profile picture).
- Purpose / legal basis: create and run your account and provide your license (performance of a contract).
1.2 Billing data
Purchases are processed by Stripe, which processes payments for Nolatech Ltd. Stripe handles payment card details and related payment data. We receive details needed to manage your subscription: plan, billing country, invoices, payment status, and business name / tax ID if you give them. We do not receive or store full card numbers.
- Purpose / legal basis: provide and bill your subscription (contract); keep financial records (legal obligation).
1.3 License check metadata
The SpanDock software checks its license with our servers daily, on license changes, and after updates. Each check may send:
- a random installation ID;
- the software’s role, version, operating system, and architecture;
- the reason for the check;
- counts of active clients, servers, and satellites for the billing period;
- license identifiers needed to validate the license.
We also see the IP address the check comes from, for rate limiting, security, and abuse prevention.
Enterprise offline licenses do not perform these checks against spandock.com after the license file is imported.
- Purpose / legal basis: validate your license, bill usage-based plans, and protect the service (contract and legitimate interests in preventing abuse).
1.4 Contact and support messages
When you email us, use the contact form, or chat via the on-site Spander chat (first-party support UI on spandock.com), we keep your name (if given), email address, and message so we can answer and follow up.
- Support channels: support@spandock.com and on-site Spander chat.
- Purpose / legal basis: respond to you (legitimate interests, or steps prior to a contract).
1.5 Academy waitlist
If you ask to be told when a SpanDock Academy course opens, we keep your email address, the courses you chose and when you signed up, only to email you about the Academy. Every email has an unsubscribe link; unsubscribing deletes your address from the list. We don't share the list with anyone.
- Purpose / legal basis: tell you when Academy courses open (consent, which you can withdraw at any time by unsubscribing).
1.6 Data room
If Nolatech Ltd shares documents with you in its data room, we use your name and email address to give you access and email you a sign-in PIN, and we record each sign-in, view and download with the time, the document, your IP address and your browser's user agent. Every document you open carries your name, your email address and the time, visibly and in a hidden mark, so that a copy can be traced to the access it came from.
- Purpose / legal basis: controlling and recording access to confidential company documents and protecting them from unauthorised disclosure (legitimate interests).
1.7 Job applicants
When you apply for a job, we process the details you send (your name, email address, profile and portfolio links, your note and, for engineering roles, your challenge answers, code, the commands you typed and how long you took) to assess your application and communicate with you about it.
- Purpose / legal basis: recruitment (steps at your request before entering into a contract, and our legitimate interest in hiring). Write to privacy@spandock.com to access or delete your application.
1.8 Mobile app and push notifications
The SpanDock mobile app connects to your own servers over an encrypted tunnel; what it shows comes from them, not from us. If you turn on notifications on your phone, your server registers the phone with us so we can deliver its alerts: we receive the phone's push token (an identifier for the app on that phone, issued by the phone's push service), its operating system, the phone's name if your server sends it, and which server and license it belongs to. When your server raises an alert, we receive its notification: the server's name, a title and short text (names and counts, never telemetry), its severity and type. We pass the token and the notification to Google Firebase Cloud Messaging, which delivers it to the phone.
- Purpose / legal basis: delivering the notifications you turned on (performance of a contract). Turning notifications off on the phone, or removing the phone from your server, stops them; your server then removes the phone from our list.
1.9 Product / website analytics
We use PostHog and Vercel Analytics and/or Vercel Speed Insights to understand how the website and account dashboard are used (for example which pages are visited and performance metrics). These tools are non-essential: where consent is required, we load them only after you opt in via the cookie banner. See the Cookie Policy.
Campaign details. When you arrive from an advertisement, a newsletter or a partner's link, the link may carry campaign details: the campaign's name and source (UTM parameters), an identifier of the partner or traffic source that sent you, and a click identifier added by the ad platform (for example Google's gclid or Microsoft's msclkid). If you have accepted analytics, PostHog records these with your visits so we can tell which campaigns work, and when you sign in we link them to your account's internal ID (never your email address or name). Without your consent they are not recorded. We do not currently send this information back to advertising platforms or partners.
- Purpose / legal basis: improve the website and understand which campaigns work (consent where required; otherwise legitimate interests where consent is not required).
1.10 Cookies
- Session / authentication cookies: keep you signed in; strictly necessary; no consent required.
- Analytics / non-essential cookies: PostHog and Vercel Analytics / Speed Insights — set only if you consent where required.
Details: Cookie Policy.
1.11 Demo requests
When you ask for a demo, we process the details you give (your name, work email, company, how many people use AI tools, the tools you use, what matters most to you, the time you chose and your time zone), whether your email's domain receives mail, and a one-way hash of your IP address for rate limiting. A person at Nolatech Ltd reviews every request. If we approve it, we email you a calendar invite and a personal call link, and set up a demo server with made-up data under your company's name for a few hours.
- Purpose / legal basis: arranging the demo you asked for and following up on it (steps at your request before entering into a contract, and our legitimate interest in selling our product). Write to privacy@spandock.com to access or delete your request.
1.12 Demo calls, recordings, transcripts and photos
A demo call takes place on our call page. Your guide is either a person from Nolatech Ltd or Nola, an AI guide: Nola is software, not a person: the call page labels her as an AI guide, and she says so if you ask. To run the call, your camera and microphone stream to our call service while the call lasts. When Nola is on the call, what you say is turned into text and answered by an AI model as you speak, and her answers are read out by a text-to-speech service; this live processing is needed for the call to work.
- Recording and transcript: demo calls are recorded. Before you join, the call page says so and asks you to confirm it; if you'd rather not be recorded, you don't have to have the call: reply to your booking email and we'll arrange the demo another way. We keep the video and audio of the call, a written transcript of what was said, three photos taken from your camera during the call (at the start, the middle and the end, so we remember who we spoke with), and a short summary written by an AI model (the questions you asked, which ones we still owe you an answer to, the plan that seems to fit, and how interested you seemed) so the SpanDock team can follow up. The summary helps a person at Nolatech Ltd follow up; no decision with legal or similarly significant effects is made from it automatically.
- Photos: the three photos are part of the recording, and taken only on a recorded call. They are never used for face recognition or any other biometric identification.
- Purpose / legal basis: the call itself, as part of the demo you asked for (steps at your request before entering into a contract, and our legitimate interest in selling our product); the recording, transcript, summary and photos, our legitimate interest in following up the demo you asked for accurately, which you confirm before joining (you can choose not to have a recorded call). You can object, or ask us to delete them, at any time by writing to privacy@spandock.com; we then delete them.
- Who processes it: the call service, the speech service and the AI model gateway listed on Subprocessors, on our instructions only; the gateway passes the text to the AI model provider that answers. We ask the gateway to use only model providers that don't keep it to train their models.
1.13 Emails about SpanDock
Besides the emails your account needs (sign-in codes, invoices, account and security notices), we send the account's owner a few emails about using SpanDock: getting-started tips, reminders before a trial ends, a thank-you when a plan starts, and occasional product news. Which ones you get depends on what happens in your account, for example whether a server has been activated or a trial is ending.
- Link clicks: links in these emails pass through https://spandock.com first, so we can count which links were clicked and when. We record only the email, the link and the time: not your IP address or device. If you have accepted analytics, the page you land on also records the campaign's name, as described under Campaign details in 1.9. We don't track whether you open an email.
- Your choice: every one of these emails has an unsubscribe link, and you can switch them off (and on again) in your dashboard under Account. Unsubscribing never stops the emails your account needs.
- Purpose / legal basis: helping customers use the product they signed up for and telling them about it (legitimate interest, with the right to object at any time by unsubscribing). We send them only to people with a SpanDock account, and we don't share the list with anyone.
2. What we never receive
The SpanDock software runs on your machines. We never receive:
- the telemetry it collects;
- your prompts, code, or tool output;
- the contents of its local database;
- Work insights summaries or captured prompts (those stay on your organisation’s server when that feature is enabled).
That data goes only to destinations you configure. The same holds for the SpanDock for AI Chats browser extension, which sends what it reads only to SpanDock on your own computer: see its Browser Extension Privacy Policy. Your organisation is responsible for lawful monitoring of staff AI-tool use. See also the Acceptable Use Policy and Privacy and security.
3. Who we share data with
We use service providers (processors) to run the website and control plane. They process data on our instructions only. The current list is at Subprocessors.
Current material providers include Vercel (hosting), Stripe (payments), Resend (transactional email), PostHog (product analytics, with consent where required), Vercel Analytics / Speed Insights (performance analytics, with consent where required), Neon (database), Cloudflare (bot protection, DNS, and the edge service that SpanDock servers and relays call), Google Cloud (relay hosting, and the AI guide on demo calls), Google Firebase Cloud Messaging (push notifications to the mobile app), Documenso (electronic signing of NDAs and contracts), and for demo calls LiveKit (the call service and its recordings), Deepgram (speech-to-text and Nola's voice) and OpenRouter (which routes Nola's answers and the call summaries to the AI model provider it selects).
We may also disclose data when required by law, to protect our rights, or as part of a merger or acquisition (in which case we will inform you as required).
We do not sell your personal data.
4. How long we keep data
| Category | Retention |
|---|---|
| Account data | While the account exists; after deletion, delete or anonymise within 30 days, except records we must keep |
| Billing records | As long as tax and accounting law requires (typically 6–7 years) |
| License check records | Life of the license plus 24 months |
| IP addresses for rate limiting | Up to 90 days |
| Contact and support messages | Up to 24 months after the conversation ends |
| Academy waitlist | Until you unsubscribe |
| Product emails sent and link clicks | 24 months |
| Unsubscribe choices | As long as needed to honour them |
| Data room access records | Up to 3 years after your access ends |
| Job applications | 12 months after we last acted on your application, unless you ask us to delete it sooner |
| Demo requests | 12 months; a request we declined, 90 days after we declined it |
| Demo call recordings, transcripts, summaries and photos | 90 days after the call, or sooner if you ask us to delete them |
| Challenge results not attached to an application | 30 days |
| Analytics data (PostHog / Vercel Analytics) | Up to 12 months, subject to your consent choices |
| Phone push registrations | While the phone is registered with your server; deleted when your server stops listing it, or when the push service reports it invalid |
| Server notifications | 90 days |
5. Your rights
If the GDPR or a similar law applies to you, you may have the right to access, correct, delete, restrict or object to processing, receive data in a portable format, and withdraw consent.
- Delete your account from your dashboard where available.
- Other requests: privacy@spandock.com. We answer within one month.
- You may complain to a supervisory authority where you live or work. Lead supervisory authority: Office of the Commissioner for Personal Data Protection (Cyprus).
6. International transfers
Some providers may process data outside the European Economic Area (for example US-based infrastructure used by Vercel, Stripe, Resend, or PostHog). Where they do, we rely on adequacy decisions or standard contractual clauses (or other lawful Chapter V tools) as set out in those providers’ terms and DPAs. See Subprocessors.
7. Security
We protect personal data with encryption in transit, access controls, and by storing sign-in codes and secrets only in hashed or encrypted form. No system is perfectly secure. If a breach affects you, we will notify you as the law requires. See also /trust.
8. Children
The website and service are not directed at children. We do not knowingly collect children’s data.
9. Changes
We may update this policy. For material changes, we will tell you by email or in your dashboard before they take effect.
10. Contact
Nolatech Ltd, Cyprus
Email: privacy@spandock.com
Support: support@spandock.com · on-site Spander chat