How Amsterdam Technologies B.V. handles personal data.
Last updated: 16 November 2026
Controller
Amsterdam Technologies B.V. is the controller for the processing described here.
- Company: Amsterdam Technologies B.V.
- Address: Overtoom 456-1, 1054JW Amsterdam, Netherlands
- VAT-ID: NL868682378B01
- KVK: 98875728
- Email: support@amsterdam-technologies.com
We have not appointed a data protection officer. Contact the address above for privacy questions. We do not make decisions based solely on automated processing that produce legal or similarly significant effects on you (Art. 22 GDPR).
This policy covers amsterdam-technologies.com and the product websites we operate, including netcap.io, fastserve.nl, fasttap.nl, time-master.app and artist-connect.pro. It also covers our NETCAP documentation at docs.netcap.io, which is hosted by GitBook as described below. Our products' hosted applications process data on behalf of the customers who use them; where we act as a processor rather than a controller, the relevant agreement with that customer governs, not this policy.
Server log files
Our reverse proxy records failed HTTP requests (status codes 400–599) for security and fault diagnosis. These logs can include the following information transmitted with the request:
- IP address
- Browser type and version
- Operating system
- Referrer URL
- Time of the request
- Requested URL and response status
An IP address is personal data, and in combination with the other fields above a request can in principle be linked to an individual. We process these logs on the basis of our legitimate interest (Art. 6(1)(f) GDPR) in operating the service securely and diagnosing faults. They are not used for advertising or profiling and are not combined with other data sources for that purpose.
Retention: server and reverse-proxy logs are retained for 30 days and then deleted.
Newsletter and product updates
If you subscribe to product updates, we process your email address, and any name you choose to give, to send you those updates.
Legal basis: your consent (Art. 6(1)(a) GDPR). You give it by ticking a checkbox that is never pre-ticked, covering marketing email only. It is not bundled with any terms or with access to downloads.
Double opt-in. After you submit the form we send one email asking you to confirm. Your address stays unconfirmed and receives nothing else until you click that link. If you do not confirm, no subscription is created.
What we store. Your email address, any name given, the product the signup came from, which form was used, the page you signed up on, and the time and wording version of your consent. We keep the consent record as evidence that consent was given, as Art. 7(1) requires.
Withdrawing consent. Every marketing email contains a working unsubscribe link. Unsubscribing takes effect immediately and costs nothing. You can also email support@amsterdam-technologies.com.
Subscriber data is held in our own mail system on our servers in Germany. It is not sold, rented or shared with advertisers.
We also use aggregate confirmation counts to monitor the signup process, based on our legitimate interest in operating it reliably (Art. 6(1)(f) GDPR).
Whitepaper downloads
Whitepapers are downloadable without giving us any personal data. We do not require an email address to access them, and the optional newsletter signup next to them is genuinely optional.
Contact forms
If you contact us through a form or by email, we process the details you send in order to answer you and to handle any follow-up. The legal basis is our legitimate interest in responding to enquiries (Art. 6(1)(f) GDPR), or the steps taken at your request prior to entering a contract (Art. 6(1)(b) GDPR) where that applies. Ordinary enquiries are deleted 12 months after closure. Staff classify closed enquiries for expiry; ongoing matters, records needed for a contract or statutory retention, and documented disputes are excluded for as long as that separate purpose requires. Existing unclassified correspondence is reviewed before deletion. You do not have to contact us or provide a name; an email address and enough information about your request are needed to reply. The main site's contact form opens your email app; nothing is delivered until you send that email.
Booking a demo
If you book a demo through our booking page (https://amsterdam-technologies.com/book), we process your email address and — when you pick a time — any name you give and the product you say you are interested in.
We use this only to arrange the meeting. Your address is not added to any newsletter or marketing list — booking a demo does not sign you up for anything, and we will not send you marketing because you booked one.
How it works. You enter your email and we send you a one-time link to confirm the address is yours. If you never click it, no booking exists and nothing further happens. Once confirmed you choose a time, and we create a calendar entry with a video-meeting link and send you a confirmation. About an hour before the meeting we send you one reminder with the same joining link. No booking account is created. The calendar entry and emails record the meeting details; website-action measurement is described under Analytics.
Legal basis: steps taken at your request prior to entering into a contract (Art. 6(1)(b) GDPR), and our legitimate interest in responding to a demo request (Art. 6(1)(f) GDPR) where that does not apply.
Who receives it. The meeting is held in Google Workspace: Google receives your email address, any name you gave and the time of the meeting in order to send you the calendar invitation and host the video call (see "Recipients and processors" below). We also notify our own support inbox that a demo has been requested, so someone can prepare for it.
Ordinary demo records and related correspondence are deleted 12 months after the meeting or closure, once classified for expiry. Verification-email copies in our own mailbox are deleted after 30 days. Ongoing contractual matters, statutory records and documented disputes are held separately; unclassified historical records are reviewed before deletion. Deletion covers our mailbox and host calendar, not copies in your mailbox or calendar. You can ask us to cancel a booking or delete the record by emailing support@amsterdam-technologies.com.
Email is required to verify your address and arrange the meeting; name and product selection are optional. Without an email address, this booking flow cannot be used. The signed verification link carries its credentials in a URL fragment, which is not sent in the HTTP request. The browser moves them into tab-local session storage to allow reloading the slot picker, removes them from the address bar, and clears them after successful booking. Closing the tab clears that storage. These credentials are used to arrange the meeting, not for analytics.
Bot protection
Newsletter and demo-request forms use Cloudflare Turnstile to prevent automated abuse. On amsterdam-technologies.com its script loads when you start interacting with the protected form; product sites may load it when the form page opens. Cloudflare receives technical information such as your IP address, browser/device information and challenge interactions; our server verifies the result with Cloudflare. We do not send the form's name, email or message to Turnstile. The legal basis is our legitimate interest in protecting our services and preventing unwanted email (Art. 6(1)(f) GDPR). Automated bot checks do not make Art. 22 decisions about you. If verification cannot complete, contact us by email.
Cloudflare, Inc. operates globally, including in the US. Its data processing addendum includes standard contractual clauses; the EU–US Data Privacy Framework applies where covered by its certification. See Cloudflare's privacy policy and Turnstile privacy information.
Job applications
Send applications to jobs@amsterdam-technologies.com with the subject “Speculative Application”.
If you apply to us — including speculatively, through the address given on our jobs page (https://amsterdam-technologies.com/jobs) — we process what you send: your name and contact details, your CV, your work history and qualifications, any links or portfolio you include, and the content of our correspondence with you. We ask for nothing beyond that, and you should not send us special categories of data (Art. 9 GDPR) such as health, religion or ethnicity. There is no application form, no account, and no automated screening or profiling.
Legal basis: steps taken at your request before entering into a contract (Art. 6(1)(b) GDPR), and our legitimate interest (Art. 6(1)(f) GDPR) in assessing whether there is a fit and in keeping a record of the process.
Retention: we delete an application no later than 4 weeks after we finish considering it, in line with Dutch Data Protection Authority guidance. If we would like to keep it on file for a future opening, we will ask you, and only keep it — for up to 1 year — if you agree. You can withdraw that agreement at any time and we will delete it.
Applications arrive by email and are stored in our self-hosted mail service (see "Recipients and processors" below). They are not added to any newsletter or marketing list, and are read only by the people involved in hiring.
Consultant database
Ask to join by emailing jobs@amsterdam-technologies.com with the subject “Consultant Database”. Applying for a job does not also enrol you in this database.
Separately from hiring, we keep a database of independent consultants and contractors we can approach for client work of the kind described on our consulting page (https://amsterdam-technologies.com/consulting). If you ask to be added — through the address on our jobs page (https://amsterdam-technologies.com/jobs) — we keep what you send: your name and contact details, your CV, the skills and tools you work with, your rate and how you invoice, and your availability.
Legal basis: your consent (Art. 6(1)(a) GDPR). You ask to be added; we do not add anyone who has not asked. Applying for a job does not put you in the database, and being in the database is not an application.
Retention: we keep your entry for 1 year. Before that runs out we will ask whether you want to stay in; if you do not reply, we delete it. You can ask to be removed at any time — one email is enough — and withdrawing does not affect anything we did beforehand (Art. 7(3); see "Your rights" below).
We use the database for one thing: contacting you when a project matches what you do. It is not a newsletter and not a marketing list, and there is no automated scoring or profiling behind it. If an engagement means showing your profile to a client, we ask you first.
Analytics
We use self-hosted analytics in the EU to measure website performance, usage and the effectiveness of our pages and offers. Our analytics does not send visitor records to advertising networks.
Our default measurement records daily counts of pageviews and approved actions, using public page groups and bounded product, plan, platform or placement codes. Actions include download and offer clicks, checkout handoffs, accepted enquiries and reported booking confirmations. Repeated actions count separately; these are not counts of unique people or proof of completed purchases or installations.
The analytics store has no visitor/session identifiers, IP-derived identities, individual browsing histories, raw URLs, query strings or advertising click IDs. We do not collect country, city, browser-version, language or precise screen breakdowns for this measurement. IP addresses and User-Agent headers necessarily arrive with network requests; User-Agent is checked transiently to filter bots, without deriving an analytics identity. Security logs have their separate purpose and retention described above. Small aggregate cells can still permit inferences, so we restrict access rather than treating every aggregate as anonymous.
Optional field performance (LCP, INP, CLS, FCP and TTFB) is off by default and requires your choice in Privacy & measurement. Samples are combined into daily page-group histograms, without visitor timelines or performance-to-purchase joins. You can withdraw performance permission there at any time. Session recording and advertising conversion sends are disabled.
Retention: reviewed daily counters and histograms expire after 13 months, with daily expiry checks. Encrypted recovery backups expire after seven days; restores remove retired visitor-linked records and reapply expiry before reuse.
Legal basis: we rely on our legitimate interest (Art. 6(1)(f) GDPR) in
improving website performance and evaluating the use and effectiveness of our
services. Optional field-performance collection uses your consent (Art. 6(1)(a)).
The Privacy & measurement control stops optional browser
collection and optional server-event helpers without a login or email. Its
host-only measurement=off preference lasts six months and contains no random
identifier; it applies to this browser on this website, not automatically to other
sites or devices. We also honour browser-exposed Do Not Track and Global Privacy
Control signals for browser measurement. Necessary service records, including
billing and newsletter consent records, remain separate. You can also object
under Art. 21 at support@amsterdam-technologies.com. See Your rights.
Purchases, licences and invoices
Direct checkout collects your billing name/address/country, optional business and VAT details, and the product, price, tax-treatment status, Terms version and affirmative choices presented to you. We use these to prepare and administer the contract and meet applicable accounting obligations. Unaccepted quotes expire after 15 minutes; abandoned acceptance records expire after 30 days. Once payment is confirmed, the accepted contractual snapshot is retained with the purchase administration for seven years. Unconfirmed tax treatment is not represented as a validated VAT exemption or reverse-charge entitlement.
Withdrawal and cancellation declarations record your email, contract reference, declaration, receipt time and email-verification/fulfilment state. They are used to honour your contractual/statutory rights, preserve deadline evidence and reconcile refunds, accounting corrections and access. A declaration is recorded before ownership or eligibility review; verifying it does not restart its original receipt time. Pending disputes or requests are not automatically erased while unresolved. Purchase/accounting evidence follows the applicable seven-year schedule; unnecessary unrelated correspondence follows the enquiry schedule.
The checkout may keep billing details in tab-local session storage so they survive navigation during checkout. This is functional storage, not an analytics identity.
If you buy a product or licence, our payments platform processes the data needed to complete the order: your billing details, the items purchased, and payment status. You pay through either Stripe or PayPal, whichever you pick at checkout. Card and account details are entered with them directly; we do not receive or store full card numbers.
Legal basis: performance of the contract (Art. 6(1)(b) GDPR) and, for invoices, our legal obligation (Art. 6(1)(c) GDPR).
We also use aggregate payment, subscription and licence-issuance figures for operational reporting, based on our legitimate interest in administering and improving our services (Art. 6(1)(f) GDPR). These reports do not link customer identities to website visitors.
Retention: Dutch tax law requires invoices and the underlying administration to be kept for 7 years. This is also why we cannot delete an invoice on request, even though you may ask us to erase other data.
Desktop apps: licences, trials and device activation
The direct-download editions of our desktop applications — Noted, ImageSieve, VidMaker, AudioVault, WiFiSpoof, WiFi Analyzer, Bluetooth Analyzer and Timemaster — check their licence with our licensing server. This happens when a trial or licence is first activated, and then periodically while the app is running.
This applies to editions downloaded directly from us. Mac App Store editions use Apple's purchase receipt instead: they do not start our trial, create a device fingerprint or contact our licensing server.
What is sent. A device fingerprint, the platform, and the product. The fingerprint is a one-way SHA-256 hash of a hardware identifier; we never receive the underlying hardware ID, and the hash cannot be reversed into one. The platform is a device class such as "Mac" or "Windows PC".
What is not sent. We do not send or store the name of your computer. Earlier versions of these apps sent the machine's hostname, which on a personal computer is often the owner's name. That was removed in August 2026, and the values already recorded were deleted from our systems at the same time.
When it happens. Most of these apps start a free trial automatically the first time you open them, which means the activation request above is sent on first launch.
Legal basis: performance of the contract (Art. 6(1)(b) GDPR) — the licence is what entitles you to run the software, and it can only be checked against something. We also have a legitimate interest (Art. 6(1)(f) GDPR) in enforcing the number of devices a licence covers.
Retention: an activation record is deleted after 18 months without the device being seen.
The apps themselves work on your own machine. What you do inside them — the recordings and transcripts in Noted, the photos in ImageSieve, the captures in the network tools — stays on your device and is not sent to us. Where an app can optionally use a third-party AI service, it says so at the point you enable it and you supply your own key for that service.
ImageSieve App Store editions
The Mac App Store and iOS editions of ImageSieve do not contact our licensing server, send a device fingerprint, activate a trial, or include an external updater. Their features are included in the App Store purchase. Photos, embeddings, search queries and EXIF metadata are processed on your device and are not sent to us.
When you choose to download a vision model, the app requests a fixed model archive from imagesieve.amsterdam-technologies.com. The request necessarily transmits your IP address and a standard HTTP User-Agent. Successful downloads are not recorded in our reverse-proxy access log; failed requests (HTTP 400–599) are retained in security and diagnostic logs as described in Server log files above. These records are used for service security and fault diagnosis, not tracking, advertising or profiling. The app contains no analytics or telemetry SDK. Apple services such as MapKit and Photos are governed by Apple's privacy practices.
Cookies
The CMS marketing site stores a functional locale cookie to remember its
language for up to one year. Its development tools may store
cms_dev_overlay_open locally as a display preference. These preferences are
separate from website analytics.
Our self-hosted marketing sites use no advertising or tracking cookies. GitBook documentation hosting is described separately below. The booking flow uses tab-local session storage as described above. Where a cookie is strictly necessary — for example to keep you signed in to an application — it is set only for that purpose. If we ever introduce cookies that require consent, we will ask for it before setting them and update this policy.
The host-only measurement preferences remember choices you request:
measurement=off stops optional measurement, and measurement_performance=v1
remembers an explicit field-performance permission. Each lasts up to six months,
contains no random identifier and is not synchronised across domains. The
settings page works without JavaScript and lets you withdraw either choice.
One exception is worth naming: the FastTap ordering page loads Stripe's payment library when you reach checkout, and Stripe sets its own cookies at that point to process the payment and detect fraud. These are set by Stripe, not by us, and only on the checkout step.
NETCAP documentation hosting
GitBook Inc. hosts docs.netcap.io on our behalf. Requests to the documentation transmit your IP address, requested URL, browser information and any referrer to GitBook and its hosting infrastructure to deliver and secure the service. Our legal basis is our legitimate interest in providing accessible, secure product documentation (Art. 6(1)(f) GDPR).
We have disabled GitBook's visitor-identification analytics cookie and have no
third-party analytics integrations or injected integration scripts configured
on this documentation site. A browser check on 9 November 2026 nevertheless
found that GitBook stores __gitbook_session in localStorage and sends page-view
events with session and visitor identifiers to /~gitbook/__evt. Its delivered
session code uses a 30-minute inactivity window. The event endpoint also set a
GAESA cookie expiring approximately 30 days later. Disabling the setting has
therefore not eliminated browser storage or page-view measurement. These
remaining activities are separate from documentation delivery and remain unresolved.
The self-hosted analytics and 30-day
reverse-proxy log retention described above concern our own infrastructure;
they do not describe GitBook's infrastructure or retention.
GitBook acts as a processor for personal data processed on our behalf under its Data Processing Addendum, incorporated into its Terms of Service. The addendum includes the European Commission's standard contractual clauses for international transfers. GitBook's published security information states that customer data is stored in the United States, with documentation and assets also cached by its CDN in other locations. See GitBook's privacy statement and subprocessor list. You can exercise your rights concerning our documentation through support@amsterdam-technologies.com.
Processing-agreement acceptance
Customers who explicitly accept a processing agreement through the payments service receive a downloadable receipt. We retain the authenticated customer reference, selected service, controller legal name, authority/acceptance affirmations, acceptance time and accepted document/hash as contract and accountability evidence (Art. 6(1)(b)/(f)), for up to seven years from acceptance. This does not authorise seven-year retention of their imported content or apply the fiscal retention rule to it. Contact support to correct a receipt or discuss an applicable erasure request or continuing-contract evidence requirement.
Continuum CRM and WhatsApp conversations
Continuum, also called Circles CRM or CRM, holds customer-selected contact and relationship details, notes, tasks, photos, messages and proposed profile facts. WhatsApp linked-device synchronisation decrypts message content in the hosted workspace. Selected AI features can send messages, contact/profile context and supporting excerpts to the configured OpenAI, Anthropic, Google or OpenRouter provider, including for embeddings/search where enabled. Optional mobile push reminders use Expo and the device platform's push service. Hosting is at Hetzner in Germany; international AI/push processing requires the applicable provider and transfer arrangements. Customer credentials do not themselves supply them.
We are controller for account, billing and proportionate security processing, on contract, statutory obligation and legitimate-interest bases respectively. For business content we act on customer-controller instructions under the applicable processing agreement. The customer's lawful basis, information to non-user participants, special-category condition and DPIA assessment must be established separately. A user's household exemption does not automatically exempt us; contact support before using an unresolved processing mode.
The initial 30-day analysis window is not the storage lifetime: raw synchronized messages expire 365 days after their message timestamp, outreach previews after seven days, and conversation-memory uploads after 24 hours. Approved copied sources have independently selected retention; accepted facts, contacts, tasks and photos remain separately until removed or the workspace is closed. Source expiry does not delete separately accepted profile facts. See the CRM privacy notice for details. Non-users can request access, correction, objection or erasure through support@amsterdam-technologies.com without creating an account. We verify identity/authority proportionately and coordinate with the relevant controller.
Recipients and processors
We keep the number of parties who touch your data small. The current recipients are:
| Recipient | Purpose | Location |
|---|---|---|
| Hetzner Online GmbH | Server hosting and backups | Germany (EU) |
| GitBook Inc. | Hosting and securing docs.netcap.io; technical request data | US / global CDN |
| Cloudflare, Inc. | Authoritative DNS and Turnstile bot protection on protected forms | EU / US |
| Amsterdam Technologies mail service (self-hosted) | Sending and storing email, newsletter lists | Germany (EU) |
| Google Ireland Limited (Google Workspace) | Calendar invitation and video-meeting link for a booked demo | EU / US |
| Stripe | Card and wallet payments, subscriptions and licence billing | EU |
| PayPal | PayPal payments and subscriptions | EU |
We do not sell personal data. Our self-hosted services and mail run on our own infrastructure inside the EU; GitBook documentation hosting is described above. Cloudflare, Google, Stripe and PayPal belong to groups headquartered in the United States: Cloudflare provides authoritative DNS (this site's web traffic is not proxied through its CDN), and Turnstile processes the technical information described under Bot protection; Google contracts with us through its Irish entity under a data processing agreement, and processes demo bookings on its global infrastructure; Stripe and PayPal bill us through their European entities and may transfer payment data to the US. These transfers are made under the European Commission's standard contractual clauses and, for recipients certified under it, the EU–US Data Privacy Framework.
Additional processors used by individual applications
The table above covers this website and the processing we carry out for ourselves. Some of our hosted applications also send data to a third party in order to provide a feature, and those are listed separately here so it is clear which product involves which recipient. These features can process information about non-users too: for example a prospect researched by a LeadGen customer or a participant in a conversation imported into CRM. Not having an account does not mean that none of your information can be processed. Contact the relevant customer controller or support@amsterdam-technologies.com to exercise your rights.
| Application | Recipient / service | What it receives | Location |
|---|---|---|---|
| Guardian | Anthropic, OpenAI, Google or OpenRouter — whichever the customer configures | Source code, dependency and finding data submitted for AI review | US |
| Guardian | NVD, Zonecruncher | Package names and domains being checked | US |
| LeadGen | Anthropic, OpenAI or Google (Gemini), according to the configured API/subscription mode | Selected prospect research, conversation context and drafted message content | US |
| LeadGen | Hunter.io, Foursquare, OpenCorporates, Companies House, GitHub | Search terms and prospect identifiers used to find and verify contacts | US / UK |
| LeadGen | Twilio | Phone number and message content, where SMS is used | US |
| LeadGen | Connected discovery/messaging platforms, including LinkedIn, Meta/WhatsApp/Instagram and Telegram where enabled | Customer-selected search terms, account/session data, recipient identifiers and messages | Various |
| SocialBot | Anthropic, OpenAI or Google (Gemini), according to the configured mode | Content being generated or analysed | US |
| SocialBot | The social platforms the customer connects | Whatever the customer instructs it to post or read | Various |
| PIM | Google (Gemini) | Product text and images submitted for enrichment | US |
| Intel | Anthropic, OpenAI or Google, according to configuration | Selected research and source context for AI processing | US |
| CRM / Continuum | OpenAI, Anthropic, Google or OpenRouter, according to the selected feature and connection | Selected messages, contact/profile context, task instructions and supporting excerpts; approved embedding/search inputs where enabled | US / Various |
| CRM mobile | Expo and device-platform push services, when enabled | Device routing token and reminder payload | Various |
| CMS, PIM, TimeMaster team AI demos | Anthropic, where the hosted demo AI feature is configured | Selected task/content context for the demo | US |
| VidMaker | Google (Gemini, Imagen and Veo) or Runway — whichever the customer configures | Provider credential, prompts, selected images, video or audio, generation settings, and provider usage or credit requests | US / Various |
| AudioVault | Anthropic, OpenAI or Google (Gemini) — whichever the customer configures | Provider credential, prompts, file and folder names, embedded media or MIDI metadata, and computed descriptors such as key, BPM and energy; audio files are not sent | US |
| AudioVault | ElevenLabs | Provider credential, text-to-speech text or sound-effect prompt, voice/model settings and generation usage | US |
| AudioVault | Google (YouTube Data API) | Provider credential and artist, title, album, year or filename-derived video ID used to find artwork | US |
| FastServe, FastTap | Stripe, PayPal | Order amount and payment details at checkout | EU / US |
AudioVault's YouTube integration is subject to the YouTube Terms of Service; Google's handling of data is described in the Google Privacy Policy. The application identifies this integration in its artwork settings before you provide a YouTube API key.
The applicable processing role, provider permission, retention and transfer safeguard depend on the service and mode actually selected. International transfers require applicable adequacy coverage or appropriate standard contractual clauses and any required assessment/supplementary measures. A customer-supplied credential or consumer subscription does not itself establish these arrangements. Provider modes whose permission or safeguards are unresolved must not receive personal data; contact support to establish the applicable deployment arrangement before enabling them. Connected platforms and payment providers may act as independent controllers rather than subprocessors.
Our desktop applications process their core workflows on your own machine. Optional provider features send only the content selected for that request. You supply your own provider key, the application identifies the transfer before the feature is enabled, and the provider's terms and retention policy apply.
Your rights
Under the GDPR you have the right to:
- access the personal data we hold about you (Art. 15);
- rectify inaccurate data (Art. 16);
- erase your data (Art. 17), subject to retention we are legally required to observe, such as the 7-year invoice rule above;
- restrict processing (Art. 18);
- data portability (Art. 20);
- object to processing based on legitimate interest (Art. 21), including our analytics and log processing;
- withdraw consent at any time where processing is based on consent (Art. 7(3)), without affecting processing carried out before withdrawal.
To exercise any of these, email support@amsterdam-technologies.com. We respond within one month.
You also have the right to lodge a complaint with the Dutch supervisory authority:
Autoriteit Persoonsgegevens Postbus 93374, 2509 AJ Den Haag, Netherlands https://autoriteitpersoonsgegevens.nl
Providing information
Newsletter subscription and consultant-database inclusion are voluntary; without your contact details we cannot provide those services. Job applicants need to provide contact and relevant experience information so we can consider an application. Purchase/billing and licence-activation details are required to perform the relevant contract; invoice details are also required by tax law. We identify optional fields at collection. Withholding required information means we cannot complete the corresponding request, purchase or activation. Statutory invoice retention does not apply to every enquiry or demo record.
Recovery copies
Deletion from live mail and calendars does not immediately remove existing recovery backups. Those copies remain access-restricted, expire under their backup schedule and are used only for recovery; expiry rules must be reapplied after a restore. Analytics recovery copies follow the separate seven-day encrypted schedule described above. Copies held independently by email recipients and meeting guests are outside our deletion control.
Privacy in het Nederlands
Sollicitaties en verzoeken om opname in de consultantendatabase kunt u sturen naar jobs@amsterdam-technologies.com, met als onderwerp respectievelijk “Speculative Application” of “Consultant Database”. Deze twee verzoeken worden apart behandeld.
Amsterdam Technologies B.V., Overtoom 456-1, 1054JW Amsterdam, KVK 98875728, is verantwoordelijk voor de hierboven beschreven verwerkingen. Vragen en privacyverzoeken: support@amsterdam-technologies.com. Er is geen functionaris gegevensbescherming aangesteld. Wij nemen geen uitsluitend geautomatiseerde besluiten met rechtsgevolgen of vergelijkbare aanzienlijke gevolgen (artikel 22 AVG).
| Doel | Gegevens en grondslag | Bewaartermijn |
|---|---|---|
| Beveiliging | Mislukte HTTP-verzoeken, inclusief IP-adres en technische verzoekgegevens; gerechtvaardigd belang | 30 dagen |
| Nieuwsbrief | E-mailadres, eventuele naam en bewijs van toestemming; toestemming via een niet vooraf aangevinkt vakje en bevestigingsmail | Tot afmelding; toestemmingsbewijs voor verantwoording |
| Vragen | Door u verstrekte contactgegevens en bericht; beantwoording op basis van gerechtvaardigd belang of stappen voor een overeenkomst | Gewone vragen: 12 maanden na afsluiting, na classificatie voor verwijdering |
| Demo | E-mailadres, optionele naam/productkeuze en afspraak; stappen voor een overeenkomst of gerechtvaardigd belang | Gewone demogegevens: 12 maanden na afspraak/afsluiting; eigen kopieën van verificatiemails: 30 dagen |
| Sollicitatie | Contactgegevens, cv en correspondentie; stappen voor een overeenkomst en gerechtvaardigd belang | 4 weken na afronding; maximaal 1 jaar met aparte toestemming |
| Consultantendatabase | Contactgegevens, ervaring, tarief en beschikbaarheid; toestemming | 1 jaar; verlenging alleen na bevestiging |
| Websiteanalyse | Dagtellingen van paginaweergaven en begrensde acties zonder bezoeker- of sessie-ID; gerechtvaardigd belang. Optionele prestatiehistogrammen na toestemming | 13 maanden met dagelijkse opschoning; versleutelde herstelkopieën: 7 dagen |
| Aankoop en licentie | Factuur-, betaal- en activatiegegevens; overeenkomst, fiscale verplichting en licentiehandhaving | Fiscale administratie: 7 jaar; activaties: 18 maanden zonder contact |
Lopende overeenkomsten, wettelijke bewaarplichten en gedocumenteerde geschillen kunnen afzonderlijke bewaring vereisen. Historische, nog niet geclassificeerde correspondentie wordt eerst beoordeeld. De verwijdering betreft onze mailbox en agendakopie, niet uw eigen kopieën. Herstelkopieën verlopen afzonderlijk en zijn uitsluitend voor herstel toegankelijk; na herstel worden verwijderregels opnieuw toegepast.
Het contactformulier opent uw e-mailprogramma: u moet het concept zelf versturen. Een demo of vraag schrijft u niet in voor de nieuwsbrief. Een e-mailadres is nodig om te antwoorden of een demo te boeken; naam en productkeuze bij een demo zijn optioneel. Nieuwsbrief en consultantendatabase zijn vrijwillig. Voor aankoop, facturatie en activatie zijn de bijbehorende vereiste gegevens nodig; zonder die gegevens kunnen wij de betreffende dienst niet leveren. Whitepapers zijn zonder e-mailadres beschikbaar.
Formulieren voor nieuwsbrieven en demo's gebruiken Cloudflare Turnstile tegen misbruik. Op amsterdam-technologies.com wordt dit geladen zodra u het formulier gebruikt; op productwebsites kan het laden bij het openen van de formulierpagina. Cloudflare ontvangt technische gegevens, waaronder IP-adres, browser/apparaat en challenge-interacties, niet de inhoud van uw bericht. Grondslag: gerechtvaardigd belang bij beveiliging. Onze site gebruikt Cloudflare voor DNS en Turnstile, niet als webproxy. Cloudflare verwerkt wereldwijd, inclusief de VS, met de toepasselijke contractuele waarborgen en waar gedekt het EU–VS Data Privacy Framework.
Onze marketinganalyse gebruikt dagtellingen en prestatiehistogrammen zonder
bezoeker- of sessie-ID, IP-afgeleide herkenning of individuele bezoekgeschiedenis.
Prestatiemeting staat standaard uit en vereist een keuze in
Privacy & measurement. Daar kunt u ook alle optionele
metingen stoppen, zonder account of e-mail. De hostgebonden voorkeurcookies
measurement=off en measurement_performance=v1 bevatten geen willekeurige
identificator en gelden maximaal zes maanden voor deze browser op deze website.
Browsersignalen Do Not Track en Global Privacy Control stoppen browsermetingen.
Kleine totalen zijn niet automatisch anoniem; toegang blijft beperkt. De Engelse
sectie Analytics beschrijft alle velden en doeleinden. U kunt ook bezwaar maken
via het bovenstaande e-mailadres. Demo-verificatie gebruikt uitsluitend
tabgebonden sessieopslag voor de ondertekende boekingslink, gewist na succesvolle
boeking of het sluiten van het tabblad. Eventuele noodzakelijke applicatie- of
betaalcookies dienen alleen hun betreffende functie; er zijn geen advertentie-
of trackingcookies op onze marketingsite.
Hosting en onze eigen mail staan in Duitsland bij Hetzner. Google Workspace ontvangt demogegevens voor agenda en videogesprek; Stripe of PayPal verwerkt de door u gekozen betaling. Optionele productfuncties kunnen geselecteerde gegevens naar AI-, spraak-, sociale of andere providers sturen. De tabel Recipients and processors hierboven noemt per product alle providers en gegevens, inclusief AudioVault; zonder die functie ontvangt zo'n provider niets van u. Internationale doorgiften gebruiken de toepasselijke standaardcontractbepalingen en voor gecertificeerde, gedekte ontvangers het EU–VS Data Privacy Framework. De meeste desktopverwerking blijft op uw apparaat; App Store-edities gebruiken Apple-aankoop- bewijzen in plaats van onze directe licentieactivatie.
De NETCAP-documentatie op docs.netcap.io wordt afzonderlijk gehost door GitBook
Inc. GitBook ontvangt technische verzoekgegevens, zoals IP-adres, pagina-URL,
browserinformatie en eventuele verwijzer, voor levering en beveiliging van de
documentatie; grondslag is gerechtvaardigd belang (artikel 6 lid 1 onder f AVG).
De instelling voor de analyticscookie voor bezoekersherkenning is uitgeschakeld
en er zijn geen analyticsintegraties of integratiescripts ingesteld. Een
browsercontrole op 9 november 2026 vond desondanks __gitbook_session in
localStorage, pagina-events met sessie- en bezoekersidentificatoren en een
GAESA-cookie met een looptijd van ongeveer 30 dagen. Deze resterende
activiteiten staan los van documentlevering en zijn nog niet opgelost. De bewaartermijnen en
zelfgehoste analyse hierboven beschrijven niet GitBooks infrastructuur. GitBook
verwerkt gegevens namens ons onder zijn verwerkersovereenkomst met
standaardcontractbepalingen; klantgegevens worden volgens zijn gepubliceerde
informatie in de VS opgeslagen en CDN-caches staan ook elders. De Engelse sectie
NETCAP documentation hosting bevat de links naar deze informatie en de
subverwerkers. Privacyverzoeken kunt u aan ons bovenstaande e-mailadres richten.
U heeft recht op inzage, correctie, verwijdering, beperking, overdraagbaarheid en bezwaar volgens de AVG, met de toepasselijke wettelijke voorwaarden. U kunt toestemming altijd intrekken zonder gevolgen voor eerdere rechtmatige verwerking; iedere marketingmail bevat een afmeldlink. Wij reageren binnen één maand. U kunt klagen bij de Autoriteit Persoonsgegevens, Postbus 93374, 2509 AJ Den Haag, https://autoriteitpersoonsgegevens.nl. Deze samenvatting hoort bij de volledige beleidsinformatie hierboven, met dezelfde wijzigingsdatum.
Changes to this policy
We update this policy when our processing changes. The date at the top shows when it was last revised. Where a change materially affects processing based on your consent, we will ask for consent again rather than rely on the old one.