Updated 26 October 2026. Taupe is provided by LUFF LLC, a Massachusetts limited liability company. Contact support@luff.works or use our contact form for privacy questions. This page covers Taupe’s native app, optional Web Connection and Taupe Tunnel. Features can vary by device and release.
Your library and other apps
A new library starts on your device. It can hold followed podcasts, listening progress, Up Next, transcripts, notes, recordings and related history. Taupe can share this library with other apps and agents you approve; their data and permissions are not limited to what Taupe displays. Downloaded podcast audio and cached artwork are kept on the device. Device backups and exports can make additional copies.
If you put the library in iCloud Drive or another synced folder, that provider transfers its files under its own terms. Sync and backups may preserve earlier copies. Stopping sync, deleting a local item and deleting provider copies are separate actions.
Publishers and podcast search
Following, refreshing or playing a show contacts its publisher’s feed, image and audio hosts. They receive the requested address and ordinary connection information, such as your IP address and request time. A private feed address may contain an access token, so treat it as sensitive. When you search the podcast directory, Taupe sends your search words and device region to Apple’s podcast directory. Apple and each publisher control their own records and retention.
Recording and local processing
Recording a thought uses the microphone only after you choose to record and grant permission. On-device transcription and supported on-device answers use Apple system features on your device; language or model assets may need to be downloaded. Taupe may download episode audio to the device before transcribing it. Saving a transcript or answer adds it to your library, where your chosen sync and approved members can receive it. Local processing does not by itself send the recording or transcript to a LUFF model service.
Approved apps and agents
You choose which apps and agents join your library and approve their permissions. An agent’s grant can cover more than one selected question or item and can allow reading or writing within its approved library areas. The agent host or model provider handles information it receives under its own practices. Ending access prevents later authorized reads and changes; it cannot recall information already copied by an agent or another app.
Optional Web Connection
Web Connection is off until you start it in Taupe. You make a pairing code, compare the codes shown in Taupe and your browser, then approve the request. An approved browser can read your library identifier and label, plus followed-show identifiers, titles and feed addresses, including private feed addresses. This connection does not give the browser access to your notes, transcripts, listening history or audio. Keep Taupe open and online for a live connection. It stops when you leave that library; you can also stop it or revoke a browser in Settings.
Taupe seals connection content between the app and the approved browser. The LUFF relay routes that traffic and handles connection and pairing information, including device or tunnel identifiers, public keys, network addresses, request times and message sizes. Where a sealed request enters the relay’s bounded offline queue, delivered entries are removed and entries older than seven days are discarded during later queue activity. This is activity-driven logical expiry, not a promise of physical erasure on a fixed date. The relay can retain other connection, grant, security and infrastructure records without an automatic age-based purge. Stop and revoke controls prevent future access; they do not erase browser copies or all relay records. See the shared LUFF relay disclosures for more about the relay’s operation and deletion limits.
Optional Taupe Tunnel
Taupe Tunnel is an optional App Store subscription for connecting chat apps you approve to your library on your own devices. Local listening, notes and transcripts do not require it. The chat app receives the requests and library results you authorize under that provider’s own terms. Unlike the sealed browser connection above, the LUFF relay can read chat requests and results while forwarding them. The relay application does not save those readable request bodies or results in its durable storage, but connection, authorization, security and infrastructure records can remain. Disconnecting or revoking access stops later reads; it cannot erase information already received by a chat provider.
To check Taupe Tunnel access, your device sends an App Store-signed subscription transaction to the relay. The relay verifies Apple’s signature and stores the product, expiry, original transaction identifier, environment and renewal state with the tunnel identifier. Apple’s subscription notifications can update that entitlement. Apple handles billing and payment information; Taupe and the relay do not receive your payment card details. Subscription and connection records are not automatically erased when you cancel or disconnect, and infrastructure backups may persist.
If you enable the connection on an iPhone, Taupe can send its Apple Push Notification service token to the relay so a chat request can silently wake your device. The relay stores the token with the device route and push environment and uses it to send a wake request; the push notification does not contain your library content. Stopping the connection prevents future authorized access but does not promise immediate deletion of all push or security records. Contact us to request deletion of LUFF-held records where applicable.
Support and website contact
Taupe can prepare a bug report on your device with its version, your operating system, recent connection steps, a library comparison code and error codes. The report excludes library content and keys. The local journal omits events older than seven days when it next loads, updates or prepares a report; you can also clear it in the app. The report is sent only when you choose where to share it. Review any message or screenshot you add before sending.
When you email Support or submit the contact form, LUFF receives the details and attachments you choose to provide. The contact form uses Cloudflare; public support email uses Apple’s iCloud Mail infrastructure. Do not send passwords, recovery secrets, private feed tokens or a full library. Support and contact records are kept as needed to answer inquiries and meet security or legal obligations; there is no fixed automatic expiry. Ask us to remove LUFF-held information when it is no longer needed.
Retention, requests and changes
Your library remains on your devices and in copies made by your chosen sync or backup providers until you remove those copies. Revoking a connection cannot erase information a recipient already received. Relay records, support correspondence and infrastructure backups can outlast a live connection; no universal deletion deadline is promised. Contact us to request access, correction or deletion of LUFF-held information, or to ask about a specific record. We may need proportionate verification. Rights available to you depend on applicable law, and independently controlled records may require a request to Apple, a publisher or another provider.
We will update this page when Taupe’s handling changes and explain material changes where notice is required. A policy change does not itself authorize a new optional connection.