LayerGlance

Privacy

LayerGlance works on your local network. Our apps and firmware do not show third-party advertising. New installations use a shared FiddlerCrab account for Free and paid licence registration; printer connections remain local. We do not track you across apps or websites, and we never receive your printers' access codes or your Bambu Lab account. This notice covers this website, our LayerGlance Facebook Page, purchases, the Glow Creator Programme, the LayerGlance app for iPhone, iPad and Apple Watch, the push relay, LayerGlance Bridge, and LayerGlance Touch and LayerGlance Glow. It explains what stays on your devices and the few cases in which personal data reaches us or our service providers.

Version of 4 November 2026.

FiddlerCrab accounts and licence registration

We use the shared FiddlerCrab identity service in our existing Supabase project in Frankfurt, Germany. Supabase is our processor. The same identity can be used by participating FiddlerCrab products, while each website has its own session. Email verification, Apple or Google sign-in provides an account ID and verified email address. Apple may substitute a private relay address. A provider may also supply a display name and profile-picture URL, which the shared identity service retains in your account profile. LayerGlance does not fetch that profile picture or upload your photo library for sign-in. Passwords and provider credentials are handled by the identity provider, not stored in our app or installer.

Your private licence register associates that identity with the product, controller Device ID or Bridge ID, or a random app installation ID, the registration terms/date, reported installation attempts and completions, download requests and verified purchase references/tier. For Apple purchases, signed transaction records are checked on our backend; we retain a hash of the original transaction reference. New purchases attach your FiddlerCrab account ID to Apple as an app-account token. A download is counted separately from an installation. We do not obtain all App Store download identities from Apple. Historical anonymous installs remain unknown.

We use these records to provide the requested account, Free and paid licence management, recovery and upgrades (Art. 6(1)(b) GDPR). Registration does not automatically subscribe you to marketing. Optional email consent is described below. We also use account-linked installation and purchase records to report installation-to-upgrade counts and maintain product statistics (Art. 6(1)(f) GDPR, our interest in understanding product adoption; you may object under the rights section). We do not use printer telemetry for these statistics. Session cookies are necessary for this service, Secure and HttpOnly on the public website. The iOS app stores its account session in its own keychain; login callbacks contain an expiring, single-use code rather than a session token. The encrypted native sign-in handoff is temporarily held in our Upstash EU database for at most five minutes and deleted on exchange or expiry. Bridge sign-in requests are encrypted in the same EU database for at most ten minutes. A Bridge stores a signed Free-registration receipt containing its Bridge ID, account ID and registration date/terms, rather than your email or OAuth session. It works offline; account deletion cannot remotely erase an offline receipt. Printer access codes, local printer addresses and photos are not added to this register.

Licence/contact records remain while needed to administer the account and licences, subject to erasure and legal retention duties. Detailed installation attempts are kept for 90 days (incomplete attempts for one day), download requests for 365 days. Aggregated completed-install counts remain with the licence. Delete your shared account from your account page, also linked inside the app. This affects participating FiddlerCrab products; it removes account/contact links while preserving device rights and required financial evidence separately. Cancel paid subscriptions with their payment provider. Apple and Google process sign-in under their own privacy policies; their international processing is separate from the Frankfurt licence database.

Optional LayerGlance marketing emails

You may separately opt in to LayerGlance product news, tips and offers from FiddlerCrab UG (haftungsbeschränkt). The checkbox is unticked by default. Consent is optional and does not affect account access, Free licences, purchases or essential service emails. We record an opt-in only after your account email is verified. Signing in without ticking the box does not withdraw an earlier opt-in.

A first-party, host-only HttpOnly cookie carries your choice and its sign-in binding for up to ten minutes so it can be saved after sign-in. It is not used for advertising tracking and is cleared when the choice is consumed or cancelled.

We store your account ID, verified email address and its verification date, the exact consent wording and version, the sign-up method or account-preference source, and server timestamps for grants and withdrawals in the same EU account database. We do not add your IP address or browser fingerprint to this consent record. The legal basis for marketing is Art. 6(1)(a) GDPR. You can withdraw at any time in your account's email preferencesor by emailing hello@fiddlercrab.eu. Each marketing email must also provide an unsubscribe option. Withdrawal does not affect earlier lawful processing.

Your current grant is retained as evidence while it applies. Replaced consent records are removed after three years; after final withdrawal, the remaining history is removed after three years. This limited evidence retention relies on Art. 6(1)(f) GDPR, our interest in showing consent and respecting withdrawal. Deleting your account removes these marketing records and excludes that identity from our current audience. Licence and legally required purchase records are handled separately.

1. Controller

FiddlerCrab UG (haftungsbeschränkt), Balbronner Straße 4, 14195 Berlin, Germany, represented by the managing director Dr. Clemens Dorian Chaskel. Email: hello@fiddlercrab.eu, telephone +49 30 69204740. We are not required to appoint a data protection officer; please send privacy requests to the email address above. See also the imprint.

2. This website

This website is hosted by Vercel Inc., 440 N Barranca Ave #4133, Covina, CA 91723, USA, as our processor. When you visit it, Vercel processes the data your browser sends with each request (IP address, date and time, requested address, referrer, browser and operating system) to deliver the site and keep it secure. The legal basis is our legitimate interest in a working and secure website (Art. 6(1)(f) GDPR). Under our current Observability Plus configuration, runtime request logs are retained for 30 days for operation and security. We do not forward them to another logging service or use them for advertising. Vercel may process data in the USA; the transfer is based on the EU-U.S. Data Privacy Framework and the EU Standard Contractual Clauses.

To see which pages are read and how the site performs, we use Vercel Web Analytics. It counts page views together with the page address, referrer, browser, operating system, device type and the country derived from the IP address. It sets no cookies, stores nothing on your device and does not store your IP address; visitors are told apart only by a hash of the request that is discarded after 24 hours, so you are not tracked across days or websites. We see aggregated figures only. The legal basis is our legitimate interest in improving the website (Art. 6(1)(f) GDPR). You can object at any time, for example by using a content blocker or by asking us by email. The site uses no advertising and no other third-party analytics. Account-linked licence and installation records are described in the accounts section; earlier optional reports are below. Checkout pages are excluded from these analytics. On other pages we remove fragments and query parameters, except for the fixed, non-personal campaign labels in our own Facebook launch links. Those labels identify the campaign and post, not an individual visitor. We do not embed Google Analytics, Meta Pixel or a Sentry error-reporting SDK on this website.

Earlier optional USB installation statistics

Earlier versions of our browser installer offered a separate "Share Device ID and installation statistics" checkbox. If you opted in, after a successful USB write it reported the controller's 12-character Device ID, Touch or Glow product, selected firmware version and fresh-install/update mode. Our server adds its receipt date and time in UTC. We retain each report privately and encrypted in our existing Upstash database for 365 days. We count repeat flashes separately from distinct controllers and compare the IDs with our paid device-licence records to understand installs and upgrades. The report contains no email, Wi-Fi or printer access codes, settings, licence token or printer activity. Normal hosting request logs remain as described above; IP addresses are not added to these installation records.

These earlier reports used optional consent (Art. 6(1)(a) GDPR), unchecked by default, for the open installer page only. They are separate from the account registration now required by our installer. In an older installer, untick the checkbox to stop subsequent reports, or close the page. You may withdraw consent and request deletion of earlier reports by emailing the controller contact with your Device ID; withdrawal does not affect earlier lawful processing. OTA updates and firmware usage do not send these reports. A browser report confirms a reported USB write, not a successful boot or ongoing use. People who decline sharing are absent from these statistics. Reporting failures never block a firmware installation.

3. Purchases and payments

Online withdrawal declarations

Our online withdrawal form works without an account. We record the name, acknowledgement email and contract reference you supply, your declaration, its server receipt date/time and a random request reference. The declaration and frozen acknowledgement are encrypted in our existing Frankfurt Upstash store. We send you a plain-text acknowledgement and notify our support mailbox through Resend (the providers and transfers are described below). Retries preserve the same declaration and receipt time; the request does not automatically change a payment or licence.

We process this information to fulfil withdrawal and confirmation duties and handle the contract (Art. 6(1)(c) and (b) GDPR). The online receipt and outbox expire at the start of the fourth calendar year after receipt. Relevant records may be retained separately where an unresolved dispute or a statutory accounting obligation requires it. For abuse prevention, we keep keyed hashes of the caller IP and acknowledgement email with request counters for ten minutes (Art. 6(1)(f)); they are not marketing consent or installation statistics. Ordinary hosting logs and email provider retention still apply. We exclude this form from web analytics. Please do not enter passwords, card details or licence codes.

App purchases are made through Apple's App Store. Apple processes your payment and account data; we receive no payment details and no contact details from Apple. The app keeps Apple-signed purchase records on your device to unlock Pro; for lock-screen updates it sends them to our push relay for a check (section 6). A Farm or Fleet subscription bought in the app also reaches us through your own LayerGlance Bridge, so that the bridge gets its plan licence (sections 4 and 7). If you choose in iOS to share analytics with app developers, Apple gives us aggregated usage figures and crash reports without identifying you.

Device licences, and Farm and Fleet plans for businesses, bought on this website are paid through Stripe (Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Dublin 2, Ireland). We send Stripe the product, the device ID or bridge ID the licence is for, for a plan also the company name and, if you give one, the VAT ID, and the confirmations you gave at checkout with their time and version. Stripe collects your contact, billing and payment details under its own privacy policy. We use the completed payment to issue a licence code bound to that ID, and record the order reference and the time we sent your confirmation in our Stripe account.

Wallets at Stripe checkout. Apple Pay, Google Pay or Link may be offered on Stripe's hosted payment page. If you use one, its provider processes wallet, device and transaction information under its own privacy notice and supplies Stripe with the payment credentials and contact or billing details needed for the payment. We receive the payment result and purchase details described in this section, not your full card number. Wallet availability checks and payment processing take place on the provider's checkout services; we do not embed a Google Pay SDK on our own website. Google may also process data for analytics under its own policy. For the providers' processing, retention and international transfers, see Apple Pay and Privacy, Google's privacy policy and Link's privacy notice.

Sold through Link. Where your selected payment terms name Link as the seller, the purchase uses Stripe Managed Payments with Link as merchant of record. Link processes checkout, billing location, applicable tax, payment receipts and invoices, and transaction support under its privacy notice. We additionally send your declared billing country and personal or business software use, and retain the verified country, tax amount and Stripe tax liability with the encrypted purchase archive. These details verify the purchase, tax coverage and exact licence recovery. See Link's privacy notice.

To choose the applicable payment terms and account for cross-border sales, we keep a company-wide FiddlerCrab tax record with our Upstash processor. It records the product, billing country, EUR amount, accounting year, payment reference and whether the amount is reserved for an open checkout or counted as paid. Company eligibility and aggregate sales determine whether a direct purchase is available. This record contains no names, email addresses, hardware IDs, card details or printer credentials. We use it for contract fulfilment and tax compliance, and retain it for applicable accounting obligations.

Farm and Fleet subscriptions. For a plan, Stripe keeps the subscription: the plan and its price, its status and current paid year, the bridge ID, the company name and VAT ID, a licence ID we derive from the subscription, and the confirmations above. Stripe charges the saved payment method each year and issues the invoice until the plan is cancelled. For every paid year we issue a new plan licence, email it to you (see below) and record on the invoice when we did so. Stripe's customer portal, linked in every licence email, lets you cancel at the end of the paid year and download invoices; Stripe processes what you enter there. Your bridge also asks us for its renewed licence near the end of the paid year (section 7).

For device purchases and website plans we also keep an encrypted archive of the selected product and price, device or bridge ID, company and VAT details for plans, checkout confirmations, the completed order or paid invoice, your email address, and the exact licence and confirmation email. We use it to deliver your purchase, retry interrupted deliveries and let you recover the same licence using the private link in your confirmation email. For plans we also keep an encrypted subscription record to check for paid renewals if a payment notification is missed. The archive is stored with Upstash (upstash.com) as our processor, alongside our plan licence records (section 7). We retain it for contract fulfilment and licence recovery, subject to required legal retention periods. It contains no card details or printer access credentials.

We email you the order confirmation, the licence code(s), for plans each year's new licence and the customer portal link, and the contract terms through Resend (resend.com, USA) as our processor, using the email address you gave Stripe. Resend processes the email address and the content of the email to deliver it. We use the Ireland sending region; Resend stores account data, including email metadata, logs and API records, in the USA regardless of the sending region. Its current standard data retention is 30 days. The transfer to the USA is based on the EU Standard Contractual Clauses.

For website purchases and App Store bridge-plan activations, we also send a separate safekeeping copy of each issued licence, its device or bridge ID, and the order, invoice or activation reference to an access-controlled company mailbox through Resend. This lets us restore the exact licence if the order archive is lost. The copy excludes your contact and billing details, printer credentials and private recovery link. We retain these copies while licence support or recovery remains necessary, subject to the retention rules below.

We use purchase records, including the device or bridge ID, your email address and, for plans, company details, to fulfil the contract, provide support, recover licences and handle licence transfers (Art. 6(1)(b) GDPR). Our legitimate interest in preventing fraud and protecting licence delivery is the basis for related security checks (Art. 6(1)(f) GDPR). We retain the records needed for these purposes while the licence or subscription needs support or recovery and while contractual claims remain relevant. Statutory tax and commercial records are retained for their applicable periods (Art. 6(1)(c) GDPR): generally eight years for accounting vouchers, six years for business correspondence and ten years for books and annual accounts, with extensions where legally required. Stripe may process data in the USA under the EU-U.S. Data Privacy Framework and the EU Standard Contractual Clauses.

4. The LayerGlance app for iPhone and iPad

What stays on your device. The app stores the printers you add (name, model, IP address or host name and serial number), your settings and the latest printer status (for example file names, temperatures, filament and error codes) on your iPhone or iPad, shared only with its own widgets. Printer access codes, the access token for your paired LayerGlance Bridge and the app's pairing key are kept in the iOS keychain on that device. Access codes, local network addresses, serial numbers, photos and print file names are not sent to us. If you use lock-screen updates, printer names and a reduced status pass through the push relay as described in section 6; subscription and account purchase records reach us as described below.

Local network. With your permission for local network access, the app connects directly to your printers over an encrypted MQTT connection on your network. To find printers it checks addresses in your own network for the printer port (8883), and it looks for LayerGlance Bridge using Bonjour. These connections stay on your local network. LayerGlance does not connect to Bambu Lab's cloud and does not ask for your Bambu Lab account.

Printer photos. If you add a photo of a printer, you choose one image with the system photo picker or from Files; the app gets access to that image only. It resizes the photo (to at most 1024 pixels) and stores it on your device. If you use LayerGlance Bridge, the app sends a small copy (at most 160 pixels, 30 KB) to your bridge so paired devices can show it, and the bridge stores it on your computer. Photos are never sent to our servers or to the push relay.

Printer identifiers. Printer serial numbers are used on your network to talk to the printers and to match them with your bridge; they are stored on your devices and your bridge only and are never sent to us or to the push relay. For lock-screen updates the app gives each printer a random ID that is not derived from the printer.

Farm and Fleet plans. If you subscribe to Farm or Fleet in the app and the app is paired with a LayerGlance Bridge, the app sends the subscription's Apple-signed transaction record to that bridge on your local network, each time it connects and when the subscription changes. The record contains the product, the transaction IDs, the purchase and expiry dates, the storefront country, the price and currency, whether it was bought or family-shared, and whether it comes from Apple's test environment. Your bridge sends it on to us to get a plan licence (section 7). The app sends nothing else for this, and nothing directly to us.

No analytics. The app contains no analytics, crash reporting, advertising or tracking code and no third-party SDKs. Links to the Bambu Lab troubleshooting wiki and to your Apple subscriptions open in your browser. Purchases go through Apple (section 3).

Widgets and lock screen. The app's widgets read the latest status from the app on your device and make no network connections. Lock-screen updates while your phone is locked (Live Activities) are described in section 6.

The legal basis for this processing is providing the app you use (Art. 6(1)(b) GDPR). You can delete the data at any time by removing printers or deleting the app.

5. The Apple Watch app and complications

If you pair LayerGlance Bridge with the iPhone app, the iPhone passes the bridge's address, name and access token to the LayerGlance app on your Apple Watch through Apple's connection between the two devices. The watch then fetches printer status directly from your bridge on your local network and keeps the bridge details and the latest status in its keychain. Printer access codes are never passed to the watch.

Watch complications can be refreshed by a push notification, but only through a bridge set up with its own Apple push key (section 7). With such a bridge, the watch sends it its complication push token (issued by Apple), which the bridge stores encrypted for as long as the pairing lasts. When a printer changes state, the bridge sends Apple a push that carries no printer data and only tells the complication to reload from the bridge. The push relay does not handle complication pushes. Pause and error alerts on the watch come from the lock-screen updates in section 6. Nothing from the watch is sent to us.

6. Lock-screen updates and the push relay

If you use LayerGlance Pro on iPhone or iPad (iOS 17 or later) with a paired LayerGlance Bridge, your bridge can keep a Live Activity on your lock screen, and on a paired Apple Watch, up to date. This is on by default and can be switched off in the app's settings ("Printers on the lock screen") or in iOS. Updates are delivered through Apple's push notification service (APNs). Because only we may use LayerGlance's Apple push key, customer bridges send updates through our push relay.

Status. The push relay is deployed at push.fiddlercrab.eu, hosted by Vercel Inc. (section 2) as our processor. It is undergoing final launch qualification; public customer release is pending. This section describes the processing when it is used.

From the app to the relay. When a Live Activity starts, the app sends the relay:

The relay checks these records against Apple's certificate. App Store installations need a current Pro purchase or Farm/Fleet plan. A bridge plan is checked against our production licence signing key, including its bridge ID and expiry. Installations from Apple's TestFlight beta service receive a grant without a purchase. The records are then discarded. The relay returns an encrypted, time-limited grant that only the relay can read. It contains the push token, the push environment, its issue and expiry time (at most eight hours and fifteen minutes later, limited by the accepted plan or subscription expiry) and a random grant ID. The app gives the grant to your bridge, which keeps it instead of the push token.

From your bridge to the relay. While the Live Activity runs, your bridge sends the grant with the lock-screen content, at most every 15 seconds and at least every minute: for each printer the name you gave it, its random ID from the app, its state, progress, remaining time and whether it has a warning or is preparing, plus totals and timestamps. When a printer pauses or reports an error, the update also carries an alert that lights up your phone and taps your watch. The alert contains the printer name and the pause or error message, for example "X1 Carbon paused – Paused at 42%" or "X1 Carbon needs attention – The printer reports an error". Updates never contain access codes, IP addresses, serial numbers, photos, file names or error codes. The relay forwards each update to Apple, which delivers it to your device under its own privacy policy.

What the relay keeps. The relay has no database. It does not store push tokens, purchase records, bridge licences, grants or printer content, and its logs record only the outcome of each request (for example "grant issued" or "update sent", with the push environment and priority), never tokens, grants, names or purchase records or bridge identifiers. To prevent abuse it counts requests per IP address and per grant in memory for up to ten minutes. Vercel's platform keeps runtime logs with request metadata, which may contain the IP address of your phone or bridge, the time, requested path and user agent, for 30 days for operation and security under our current Observability Plus configuration. We do not forward these logs to another logging service.

The legal basis is providing the feature you use (Art. 6(1)(b) GDPR), including checking that the installation and purchase are genuine. Vercel may process data in the USA (see section 2). You can stop the relay at any time by ending the Live Activity, switching lock-screen updates off in the app, or switching the relay off on your bridge.

7. LayerGlance Bridge

LayerGlance Bridge runs on your own computer or Raspberry Pi. It stores the printers' IP addresses, serial numbers and access codes (encrypted, with Windows DPAPI or AES-GCM on Linux), the latest printer status, printer photos you added in the app, the paired apps, screens and lights (public keys, token hashes and device IDs), a random bridge ID, and its settings. For lock-screen updates it also stores, encrypted and for at most about eight hours, which printers each Live Activity shows, their names, and the relay grant; and the complication push tokens of paired watches (section 5). Its setup page is only reachable from the same computer. Printer access codes, IP addresses, serial numbers, photos and print file names stay on your own devices and network. The lock-screen content described in section 6 and the licence requests below are the exceptions that reach our services.

The bridge connects to your printers and paired devices on your local network, to GitHub when you choose to fetch firmware updates for your lights (section 8), to our push relay for lock-screen updates (section 6), and to layerglance.com for Farm and Fleet plan licences (below). You can switch the relay off with the setting PRINTBRIDGE_PUSH_RELAY_URL=off. A bridge that is configured with its own Apple push key (the PRINTBRIDGE_APNS_ settings, used only for bridges we or developers operate) sends the same lock-screen content directly to Apple instead of through the relay; it then stores the Live Activity push tokens encrypted on the bridge for up to eight hours. The bridge sends us no telemetry.

If you move the bridge to another computer, it creates a transfer file encrypted with a passphrase you choose. Licences are checked offline on the bridge; only the plan requests below reach us.

Plans bought in the app. When a paired app passes on its Farm or Fleet subscription (section 4), the bridge sends that Apple-signed transaction record and its random bridge ID to layerglance.com, hosted by Vercel (section 2). We check the record against Apple's certificate and return a plan licence bound to the bridge ID and valid for up to 35 days, never beyond the subscription's expiry plus three days; paired apps renew it when they connect. Its licence ID is derived from the subscription's original transaction ID. So that one subscription unlocks one bridge, we store that licence ID with the bridge ID and the dates it was first used and last moved to another bridge, in a database run for us by Upstash, Inc. in the EU (Frankfurt), as our processor. We keep this entry until 90 days after the most recently issued bridge licence expires. We also keep an encrypted archive of each issued plan licence, its bridge and licence IDs, plan, subscription expiry and Apple purchase environment in the same EU database. We reuse the exact licence on reconnects within a monthly refresh window, unless the plan or paid period changes. A separate safekeeping copy is sent through Resend to our company mailbox, as described in section 3. These copies are retained while support or recovery is necessary, subject to the purchase-record retention rules in section 3. We do not store the transaction record or its original transaction ID in this archive; our logs record only the outcome and the plan.

Renewal check for plans bought on this website. A bridge with such a plan contacts layerglance.com at most once a day in the last ten days before its licence expires. It sends its bridge ID and licence ID and nothing else. We look up the matching subscription in our Stripe account (section 3) and, while it is paid, return the next licence.

For both requests, to prevent abuse, we count requests per IP address in memory for up to ten minutes; Vercel's request logs are described in section 2. The legal basis is providing the plan you bought (Art. 6(1)(b) GDPR). A bridge without a plan never makes these requests.

8. LayerGlance Touch and LayerGlance Glow

The screens and lights store their Wi-Fi name and password, your printers' IP addresses, serial numbers and access codes, an optional web password, settings, the current printer status and file names, and (on LayerGlance Touch) printer photos on the device itself. Customer firmware does not encrypt this storage, so that you can always recover a device over USB; erase the device before you pass it on. They talk to your printers and your bridge on your local network and send nothing to us. Licences are checked offline on the device against its device ID, which is derived from the device's network (MAC) address; the device ID reaches us only if you buy a licence (section 3) or send it to support.

When they check for updates, LayerGlance Touch and LayerGlance Glow download update information and firmware files from GitHub (raw.githubusercontent.com and github.com, operated by GitHub, Inc., USA). LayerGlance Bridge does the same when you choose to fetch the latest release on its setup page, and then passes updates on to the lights it manages. GitHub receives the IP address of the device and the time of the request, as with any download. We receive no data from these checks. The legal basis is providing the software you use (Art. 6(1)(b) GDPR).

9. Support and bug reports

If you write to us, we use your message, contact details and any information you include (for example device IDs, versions or logs) to answer you (Art. 6(1)(b) GDPR where it concerns a contract, otherwise our legitimate interest in answering, Art. 6(1)(f) GDPR). We delete them when your request is closed, unless the law requires us to keep them. Please do not send passwords or access codes.

Bug reports are sent voluntarily by email; the app, Bridge, Touch and Glow do not automatically upload crash reports to us or to Sentry. Apple may supply the opt-in crash reports described in section 3. Website and relay errors may appear in Vercel's operational logs described above. See the support pagefor the information useful in a report, and remove credentials, private printer names and other sensitive details from attachments.

9a. Glow Creator Programme

If you apply by email, we use your contact details, public creator/model name, model URL, submitted print files, prototype photos/video and correspondence to check the published criteria and administer the reward (Art. 6(1)(b) GDPR). We request the controller device ID privately after approval and use it to issue and recover your device-bound Glow Pro licence. Licence records and the administrative safekeeping copy follow section 3 above.

We keep the rewarded design, decision and licence reference to avoid duplicate grants (our legitimate interest in preventing misuse, Art. 6(1)(f) GDPR) and support accepted licences (Art. 6(1)(b) GDPR). We delete assessment evidence once it is no longer needed to resolve the submission, provide licence support or handle a related legal claim. Correspondence uses our existing email providers; the programme creates no public account, newsletter subscription or automatic marketing profile. Do not send passwords or printer access codes.

Participation does not give us permission to reuse your photos/video in ads. We ask separately before featuring your media and agreed public creator credit. Where that use identifies you, it relies on consent (Art. 6(1)(a) GDPR). You can withdraw consent for future use by contacting us without losing the approved reward or affecting the lawfulness of earlier consent-based use.

10. The LayerGlance Facebook Page

We operate the LayerGlance Facebook Page to explain the product and answer questions. Meta Platforms Ireland Limited, Serpentine Avenue, Block J, Dublin 4, Ireland operates Facebook. If you visit or interact with the Page, Meta processes account, device and interaction data under its privacy policy, including through cookies and possible transfers outside the EEA. We can see the profile information, comments and messages you choose to share with the Page. We use them to communicate with you, based on our legitimate interest in product information and answering enquiries (Art. 6(1)(f) GDPR), or to provide contractual support (Art. 6(1)(b)). We retain correspondence while needed to answer your enquiry and meet any related contractual or statutory obligations; Meta also controls retention on its platform under the linked privacy policy. Please use email for order details and do not post licence codes or credentials in public comments.

Meta also supplies aggregate Page Insights about visits and interactions. We and Meta Ireland are joint controllers for the processing covered by the Page Insights Controller Addendum (Art. 26 GDPR). Our interest is understanding which product information helps visitors (Art. 6(1)(f) GDPR). Meta takes primary responsibility for the GDPR obligations for this Insights processing, including information and rights requests. We receive aggregate statistics rather than the underlying Insights event records. You may exercise your rights with Meta or contact us at the address in section 1. Meta explains its retention and transfer safeguards in the linked privacy information. We do not embed Facebook content or Meta tracking code on this website.

11. Your rights

You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18) and data portability (Art. 20). Where we rely on legitimate interests, you may object at any time for reasons arising from your particular situation (Art. 21). You also have the right to lodge a complaint with a supervisory authority, for example the Berlin Commissioner for Data Protection and Freedom of Information (Berliner Beauftragte für Datenschutz und Informationsfreiheit), Alt-Moabit 59–61, 10555 Berlin.

Most LayerGlance data never reaches us, so you control it on your own devices. For data we or our processors hold, write to hello@fiddlercrab.eu. We do not sell personal data, do not use it for behavioural advertising and do not make automated decisions about you.

Privacy · LayerGlance