Privacy Policy

This Privacy Policy explains how Nimblet collects, processes, and protects personal data. Nimblet is a B2B SaaS analytics platform for ad creative teams. We follow the EU General Data Protection Regulation (GDPR).

Controller

YOYABA GmbH
Barmbekerstraße 6a, 22303 Hamburg, Germany
Email: help@nimblet.io

Data Protection Officer

Mauß Datenschutz GmbH
Neuer Wall 10, 20354 Hamburg, Germany
Email: info@datenschutzbeauftragter-hamburg.de
Phone: +49 40 999 99 52-0

Data we collect

We process the following categories of personal and operational data to deliver the service:

CategoryDataSourcePurposeLegal basis
AccountName, email, profile pictureGoogle OAuthAuthenticationArt. 6(1)(b)
Ad accountCampaigns, ads, creatives, performance metricsLinkedIn / Meta APICore productArt. 6(1)(b)
Media assetsAd images and videosLinkedIn / Meta API → GCSDisplay in libraryArt. 6(1)(b)
AI analysisAd creative image URLs, copy and prompts sent to our AI model provider (via OpenRouter)User-triggeredCreative scoringArt. 6(1)(b)
Sessionnimblet_session cookieBrowserLogin persistenceArt. 6(1)(b)
InvitationsInvitee emailUser inputTeam accessArt. 6(1)(b)
BillingBilling contact (name, email), subscription status, invoice metadataUser input / StripePaid-plan billingArt. 6(1)(b), (c)
ChatsYour questions and attachments in the Nimblet chat, the answers, the tools the assistant called with their results, and their costYour use of the chatAnswer your questions; support, error analysis and product improvement by authorized staff, each time staff open a chat is loggedArt. 6(1)(b); as processor under the DPA
WaitlistWork email, company website, the ad campaign you came from (UTM labels) and the ad click ID (Meta ad click ID always; Google ad click ID only with marketing consent)Waitlist form, our cookiesPre-launch waitlist and giveaway: emails about the launch and the draw; which ads bring sign-upsArt. 6(1)(b); campaign Art. 6(1)(f); Meta click ID Art. 6(1)(f); Google click ID Art. 6(1)(a)

Data we do NOT collect

  • No analytics or tracking inside the Nimblet app, apart from the sign-up and onboarding reports with your consent. On our website, the Meta Pixel and the LinkedIn Insight Tag run only after you consent (see Marketing tags on our website).
  • No full payment card data. Payments for paid plans are processed by Stripe; your card details go directly to Stripe and never touch our servers. We store only the billing contact, subscription status, and invoice metadata.
  • No lead-level advertising data. Conversion and pixel data is processed in aggregate only (per-ad, per-day counts and values); we do not ingest names, emails, or other identifiers of ad audiences.
  • AI analysis is optional and bring-your-own-key: it runs only when your workspace supplies its own model-provider API key.

Sub-processors

We engage a small set of third-party processors to operate the service (EU cloud hosting, ad-platform APIs, AI model routing, competitor web scraping, payment processing, transactional email). The current list - with each processor’s purpose, the data involved, its location, and the transfer safeguard - is published at /subprocessors. For processing on behalf of business customers, see our Data Processing Agreement.

Data retention

  • Account data (name, email, profile picture): deleted within 30 days of account deletion. Legal basis Art. 6(1)(b); statutory retention obligations remain reserved.
  • Ad-account data, creative media, and derived analysis: deleted within 90 days of disconnecting the source ad account or deleting the workspace.
  • After a paid subscription ends, organization data is kept read-only for 90 days (so you can rejoin without data loss), then deleted with prior notice. Earlier deletion on request.
  • Billing and invoice records: retained for the statutory commercial and tax retention periods under German law (up to 10 years, Art. 6(1)(c)).
  • OAuth access/refresh tokens: deleted on disconnect.
  • AI usage and generation logs: retained up to 12 months for billing and audit, then deleted.
  • Waitlist data (email, website, ad campaign): deleted within 12 months if no account is created.
  • Session cookie: 7 days.
  • Backups: overwritten on a rolling cycle (within ~35 days).

You can request earlier deletion at any time (see User rights).

User rights (GDPR Art. 15–22)

You have the right to access, deletion, portability, correction, restriction, and objection regarding your personal data. To exercise any of these rights, contact help@nimblet.io. We respond within 30 days.

Right to lodge a complaint

You have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). Our competent authority is:
Der Hamburgische Beauftragte für Datenschutz und Informationsfreiheit (HmbBfDI)
Ludwig-Erhard-Straße 22, 20459 Hamburg, Germany
datenschutz-hamburg.de

Cookies

The Nimblet app uses strictly necessary cookies. When you arrive from one of our ads, the website and the app also remember the campaign you came from (nimblet_utm). Our website (nimblet.io) uses marketing cookies and statistics only after you accept them in the cookie banner. You can change your choice at any time with the cookie settings button below. Meta and LinkedIn also set cookies on their own domains (facebook.com, linkedin.com) under their own policies.

CookiePurposeDurationType
nimblet_sessionAuthentication7 daysStrictly necessary
nimblet_oauth_stateOAuth CSRF protection10 minutesStrictly necessary
nimblet_consentStores your cookie choice12 months after accept, 6 months after rejectStrictly necessary
nimblet_internalMarks a browser of our own team, so no marketing tags run400 daysStrictly necessary
nimblet_utmRemembers the ad campaign you came from (UTM labels, no identifier), sent with a waitlist sign-up or account sign-up30 daysAd attribution
nimblet_clickKeeps the ad click ID of your visit for a waitlist sign-up or account sign-up. The Meta click ID (fbclid) is kept whatever you choose in the cookie banner and goes to Meta with that sign-up report (see Marketing tags on our website). The Google click ID (gclid) is kept only after you accept marketing cookies and is never sent to Google30 daysAd attribution; marketing (consent) for the Google click ID
_fbpMeta Pixel: recognizes your browser for ad measurement and audiences90 daysMarketing (consent)
_fbcMeta Pixel: links a click on our Meta ad to a visit90 daysMarketing (consent)
li_fat_idLinkedIn Insight Tag: links a click on our LinkedIn ad to a visit30 daysMarketing (consent)
d0_sessionDash0 website statistics: a random ID that groups the pages of one visit (browser storage, not a cookie). A visit ends after 3 hours without a page view, 6 hours at most; the next visit gets a new IDUntil you withdraw consent or clear your browser dataStatistics (consent)
d0_tabDash0 website statistics: a random ID for one browser tab (browser storage, not a cookie)Until you close the tabStatistics (consent)

Website statistics

If you accept statistics, our website (nimblet.io) loads the Dash0 Web SDK. It tells us which pages you open, which of our buttons you click, whether the waitlist form worked, how fast the pages load and which errors happen in your browser. We use it to find and fix what does not work. Nothing loads if you reject or do not choose.

Dash0 (Dash0 Inc., New York, USA) processes this data for us as a processor (Art. 28 GDPR) and stores it in the EU (Google Cloud, region europe-west4). It receives the page address (ad click IDs removed), the referring page, browser and device details, a random visit ID and a random tab ID. It shortens your IP address before it derives a rough location (city level) from it. It does not see what you type into the form. We do not use it to identify you or for ads. Legal basis: your consent, § 25(1) TDDDG and Art. 6(1)(a) GDPR. You can withdraw it at any time under “Cookie settings” in the website footer; the IDs are then deleted from your browser. Transfers to Dash0 Inc. are covered by EU Standard Contractual Clauses (Art. 46 GDPR). Dash0’s privacy policy.

Marketing tags on our website

If you accept marketing cookies, our website (nimblet.io) loads two tags. We use them to measure our ads and to show ads to people who visited our website. Nothing loads if you reject or do not choose. If you accepted them and then create an account, the app (app.nimblet.io) loads the same tags to report the sign-up, and again when you connect your first ad account. The tags then stay active until you reload the page and see the addresses and titles of the app pages you open in that time. They see no ad data or other content from your account.

Meta Pixel (Meta Platforms Ireland Ltd.) sends your IP address, browser details, the pages you visit, the referring page and the _fbp identifier to Meta, for ads on Facebook and Instagram. When you join the waitlist or create an account, our server also reports that sign-up to Meta through the Meta Conversions API, so Meta counts it even when your browser blocks the Pixel. It sends your email address as a SHA-256 hash, your IP address, browser details, the page, the _fbp and _fbc identifiers, when you have them, and the Meta ad click ID. This report goes out whether you accepted or rejected marketing cookies (legitimate interest, Art. 6(1)(f): measuring which ads bring sign-ups). The Pixel itself runs only after you accepted. Meta’s terms:Controller Addendum,privacy policy.

LinkedIn Insight Tag (LinkedIn Ireland Unlimited Company) sends your IP address, browser details, the pages you visit, the referring page and, after a click on our LinkedIn ad, theli_fat_id identifier to LinkedIn, for ads on LinkedIn. We see only aggregated reports, never who you are. LinkedIn’sprivacy policy.

For collecting and sending this data, we and each provider are joint controllers (Art. 26 GDPR). After that, each provider alone decides how it processes the data. Legal basis: your consent, § 25(1) TDDDG and Art. 6(1)(a) GDPR. You can withdraw it at any time under “Cookie settings” in the website footer; this does not affect processing before the withdrawal. Both providers may transfer data to the United States; Meta Platforms, Inc. and LinkedIn Corporation are certified under the EU-U.S. Data Privacy Framework (Art. 45 GDPR).

International transfers

Application data is hosted in the EU (Google Cloud region europe-west1). Some of our sub-processors are based in, or have parent entities in, the United States (Google, Meta, LinkedIn, OpenRouter, Firecrawl, Stripe, Resend, Dash0). Where personal data is transferred outside the EU/EEA, the transfer is governed by EU Standard Contractual Clauses or another mechanism recognized under Art. 46 GDPR. The safeguard applied to each processor is set out in our sub-processor list.

Last updated: 2026-11-12