Effective Date: June 1, 2025

Last Updated: June 1, 2025

Jurisdiction: Tennessee, United States

You Are Still Reading. Remarkable.

This document covers how data is handled within my apps. It is distinct from the Privacy Policy, which covers personal information collection (spoiler: none). This one covers the more practical question of what my apps actually store on your device and why.

The executive summary: your data stays on your device, under your control, unless you specifically use a feature that sends it somewhere, in which case I tell you exactly where it goes.

1. Scope

This Data Usage Policy applies to all applications developed and published by Brian Ragle, operating out of Tennessee, United States. It applies to users worldwide, subject to the same regional availability limitations described in the Privacy Policy.

This policy works in conjunction with the Privacy Policy at https://brianragle.com/privacy-policy/. If you have not read that one, the short version is that I collect no personal information. This document explains what my apps do with data at the local level.

2. Local Data Storage

Some of my apps store data on your device. This is a normal and necessary part of how software works. An app that remembers your preferences or saves your work is useful. An app that forgets everything every time you close it is a parlor trick.

When an app stores data locally, the following principles apply:

Transparency. The app will make it clear what it is storing and where. You will not discover a mysterious file in your file system six months later and wonder what it is.

User control. You can delete locally stored data. Either through the app itself, or by deleting the app, or both. I will not hide data in locations that survive an app deletion unless there is a genuinely good reason to do so (such as shared container data on macOS), in which case that will be documented in the app.

Minimal footprint. My apps store what they need to function and nothing more. I am not in the business of hoarding data I have no use for.

No silent accumulation. My apps do not quietly accumulate data over time in ways that are not visible or useful to you. If an app creates logs or cache files, those are either accessible to you, periodically purged, or both.

3. What Kinds of Data May Be Stored Locally

Depending on the specific app, locally stored data may include:

  • **Preferences and settings** you have configured within the app
  • **User-created content** such as notes, saved items, or documents you have explicitly created using the app
  • **Cache data** that improves performance (images, recently accessed content, etc.)
  • **App state** such as where you left off in a workflow

Each app’s page at https://brianragle.com/apps/ describes what that specific app stores and why.

4. Data Transmission: When, Where, and Why

Here is where it gets slightly more complicated, so I will be specific.

Default state: no data transmission. By default, my apps do not transmit data to external servers. I do not have backend infrastructure collecting your usage data, syncing your preferences to a cloud I operate, or phoning home with telemetry.

Exceptions are explicit and documented. If an app has features that require sending data to an external service, those features will be:

1. Clearly described on the app’s page at https://brianragle.com/apps/

2. Clearly explained within the app itself before you use them

3. Opt-in, not opt-out, wherever technically feasible

Current categories of data transmission that may apply to specific apps:

Web search integration. If an app includes the ability to search the web, your search query will be sent to the search provider you have configured or that the app uses by default. That provider’s privacy policy governs what they do with it. I have no visibility into what they do with your query.

Bring Your Own Key (BYOK) AI integration. If an app allows you to connect your own AI provider (such as OpenAI, Anthropic, a locally-run model, or a similar service) using your own API credentials, data you submit through that feature is sent directly from your device to that provider. I am not an intermediary. I do not see it. I do not log it. Your relationship with that provider and its data practices is between you and them.

I genuinely recommend reading the terms of service and privacy policy of any AI provider you connect to your tools. Not as a legal disclaimer but as actual advice from someone who pays attention to this space. These providers collect, retain, and may use your input data in ways that vary considerably by provider and pricing tier.

5. Third-Party Services and My Responsibility (or Lack Thereof)

When you use a feature in one of my apps that transmits data to a third party, that data is now under that third party’s jurisdiction. I am not responsible for:

  • What that third party does with your data
  • How long they retain it
  • Whether they share it with other parties
  • Changes to their own privacy or data policies
  • Their security practices
  • Their compliance with applicable law in your jurisdiction

This is not me washing my hands of your welfare. It is an honest acknowledgment that once data leaves your device and travels to a server I do not operate, I have zero control over it. The practical implication is the same as it would be with any tool that connects to external services: know who you are connecting to.

Where I am aware of a third-party service’s relevant data practices, I will note them in the app documentation. Where I am not, I will say so.

6. Data Deletion

App deletion. Deleting an app from your device will remove the app’s locally stored data in most cases. On iOS, this is standard behavior. On macOS, some apps store preference files or support files in your user Library folder; the app’s documentation will note if this applies.

In-app deletion. Where it makes sense to do so, apps will include the ability to delete stored data without requiring you to delete the entire app.

My data (which doesn’t exist). Since I do not collect or store data on my own servers, there is nothing to request deletion of on my end. If you contact me asking me to delete your data, I will confirm that I hold none and you can move on with your day feeling lighter.

7. Security

Locally stored data is protected by whatever device-level security you have enabled (device encryption, screen lock, etc.). I make reasonable efforts to store data appropriately for its sensitivity level. I do not store sensitive information in plaintext when a better option exists.

For data transmitted to third-party services, security in transit is handled by the connection protocols between your device and that service (standard HTTPS/TLS). I cannot make representations about the security practices of services I do not operate.

8. Children

My apps are not directed at children under 13. As detailed in the Privacy Policy, I do not collect personal information from anyone, which makes inadvertent collection from children structurally impossible. Users under the relevant age threshold in their jurisdiction should have a parent or guardian review this policy, which they will likely not do but which I am obligated to suggest.

9. Changes to This Policy

If I change this policy meaningfully, I will update the “Last Updated” date at the top and note significant changes on the relevant app pages. Continued use of an app after a policy change constitutes acceptance of the updated terms.

10. Contact

Questions about data handling in a specific app? Ask.

Brian Ragle

Tennessee, United States

Email: bragle@gmail.com

Apps: https://brianragle.com/apps/

Support: https://brianragle.com/support/

Fecha de vigencia: 1 de junio de 2025

Última actualización: 1 de junio de 2025

Jurisdicción: Tennessee, Estados Unidos

Resumen ejecutivo

Tus datos permanecen en tu dispositivo, bajo tu control, a menos que uses específicamente una función que los envíe a algún lugar, en cuyo caso te digo exactamente a dónde van.

1. Almacenamiento local de datos

Algunas de mis aplicaciones almacenan datos en tu dispositivo. Cuando una aplicación almacena datos localmente, se aplican los siguientes principios:

Transparencia. La aplicación dejará claro qué está almacenando y dónde.

Control del usuario. Puedes eliminar los datos almacenados localmente, ya sea a través de la propia aplicación o eliminándola.

Huella mínima. Mis aplicaciones almacenan lo que necesitan para funcionar y nada más.

Sin acumulación silenciosa. Mis aplicaciones no acumulan datos de forma silenciosa con el tiempo.

2. Tipos de datos que pueden almacenarse localmente

Dependiendo de la aplicación específica, los datos almacenados localmente pueden incluir: preferencias y configuraciones, contenido creado por el usuario, datos de caché y estado de la aplicación.

3. Transmisión de datos: cuándo, dónde y por qué

Estado predeterminado: sin transmisión de datos. Por defecto, mis aplicaciones no transmiten datos a servidores externos.

Las excepciones son explícitas y están documentadas:

Integración de búsqueda web. Si una aplicación incluye la capacidad de buscar en la web, tu consulta de búsqueda se enviará al proveedor de búsqueda configurado. La política de privacidad de ese proveedor rige lo que hacen con ella.

Integración de IA con tu propia clave (BYOK). Si una aplicación te permite conectar tu propio proveedor de IA usando tus propias credenciales de API, los datos que envíes a través de esa función se envían directamente desde tu dispositivo a ese proveedor. Yo no soy un intermediario. No veo esos datos ni los registro. Tu relación con ese proveedor y sus prácticas de datos es entre tú y ellos. Te recomiendo genuinamente leer los términos del proveedor de IA que conectes.

4. Terceros y mi responsabilidad

Cuando usas una función que transmite datos a un tercero, esos datos quedan bajo la jurisdicción de ese tercero. No soy responsable de lo que ese tercero haga con tus datos, cuánto tiempo los retiene, si los comparte con otras partes, ni de sus prácticas de seguridad.

5. Eliminación de datos

Eliminación de la aplicación. Eliminar una aplicación de tu dispositivo eliminará los datos almacenados localmente en la mayoría de los casos.

Mis datos (que no existen). Dado que no recopilo ni almaceno datos en mis propios servidores, no hay nada que solicitar eliminar de mi parte.

6. Contacto

Brian Ragle

Tennessee, Estados Unidos

Correo: bragle@gmail.com

Soporte: https://brianragle.com/support/

Date d’entrée en vigueur : 1er juin 2025

Dernière mise à jour : 1er juin 2025

Juridiction : Tennessee, États-Unis

Résumé

Vos données restent sur votre appareil, sous votre contrôle, sauf si vous utilisez spécifiquement une fonctionnalité qui les envoie quelque part, auquel cas je vous dis exactement où elles vont.

1. Stockage local des données

Certaines de mes applications stockent des données sur votre appareil. Les principes suivants s’appliquent : transparence, contrôle utilisateur, empreinte minimale, pas d’accumulation silencieuse.

2. Transmission des données

État par défaut : aucune transmission de données. Par défaut, mes applications ne transmettent pas de données à des serveurs externes.

Intégration de recherche web. Si une application inclut la recherche web, votre requête sera envoyée au fournisseur de recherche configuré. La politique de confidentialité de ce fournisseur régit l’utilisation de vos données.

Intégration IA avec votre propre clé (BYOK). Si une application vous permet de connecter votre propre fournisseur d’IA, les données que vous soumettez sont envoyées directement de votre appareil à ce fournisseur. Je ne suis pas un intermédiaire. Je ne vois pas ces données. Votre relation avec ce fournisseur et ses pratiques en matière de données vous concerne exclusivement.

3. Responsabilité concernant les tiers

Lorsque vous utilisez une fonctionnalité qui transmet des données à un tiers, ces données sont sous la juridiction de ce tiers. Je ne suis pas responsable de ce que ce tiers fait avec vos données, de la durée de leur conservation, ni de leurs pratiques de sécurité.

4. Contact

Brian Ragle

Tennessee, États-Unis

E-mail : bragle@gmail.com

Support : https://brianragle.com/support/

Data de vigência: 1 de junho de 2025

Última atualização: 1 de junho de 2025

Jurisdição: Tennessee, Estados Unidos

Resumo

Seus dados permanecem no seu dispositivo, sob seu controle, a menos que você use especificamente um recurso que os envie para algum lugar, caso em que digo exatamente para onde vão.

1. Armazenamento local de dados

Alguns dos meus aplicativos armazenam dados no seu dispositivo. Quando um aplicativo armazena dados localmente, os seguintes princípios se aplicam: transparência, controle do usuário, pegada mínima, sem acúmulo silencioso.

2. Transmissão de dados

Estado padrão: sem transmissão de dados. Por padrão, meus aplicativos não transmitem dados para servidores externos.

Integração de pesquisa na web. Se um aplicativo inclui pesquisa na web, sua consulta será enviada ao provedor de pesquisa configurado. A política de privacidade desse provedor rege o que eles fazem com ela.

Integração de IA com sua própria chave (BYOK). Se um aplicativo permite que você conecte seu próprio provedor de IA usando suas próprias credenciais de API, os dados que você enviar por meio desse recurso são enviados diretamente do seu dispositivo para esse provedor. Não sou intermediário. Não vejo esses dados. Sua relação com esse provedor e suas práticas de dados é entre você e eles. Recomendo genuinamente ler os termos do provedor de IA que você conectar.

3. Exclusão de dados

Excluir um aplicativo do seu dispositivo removerá os dados armazenados localmente na maioria dos casos. Como não coleto nem armazeno dados nos meus próprios servidores, não há nada a solicitar exclusão da minha parte.

4. Contato

Brian Ragle

Tennessee, Estados Unidos

E-mail: bragle@gmail.com

Suporte: https://brianragle.com/support/

Datum des Inkrafttretens: 1. Juni 2025

Zuletzt aktualisiert: 1. Juni 2025

Zuständige Rechtsordnung: Tennessee, Vereinigte Staaten

Zusammenfassung

Ihre Daten verbleiben auf Ihrem Gerät, unter Ihrer Kontrolle, es sei denn, Sie verwenden gezielt eine Funktion, die sie irgendwohin sendet. In diesem Fall teile ich Ihnen genau mit, wohin sie gehen.

1. Lokale Datenspeicherung

Einige meiner Apps speichern Daten auf Ihrem Gerät. Es gelten folgende Grundsätze: Transparenz, Benutzerkontrolle, minimaler Footprint, keine stille Akkumulation.

2. Datenübermittlung

Standardzustand: keine Datenübermittlung. Standardmäßig übermitteln meine Apps keine Daten an externe Server.

Websuche-Integration. Wenn eine App die Möglichkeit zur Websuche bietet, wird Ihre Suchanfrage an den konfigurierten Suchanbieter gesendet. Dessen Datenschutzerklärung regelt die Verwendung Ihrer Daten.

BYOK-KI-Integration. Wenn eine App Ihnen erlaubt, Ihren eigenen KI-Anbieter mit Ihren eigenen API-Zugangsdaten zu verbinden, werden die von Ihnen übermittelten Daten direkt von Ihrem Gerät an diesen Anbieter gesendet. Ich bin kein Vermittler. Ich sehe diese Daten nicht. Ihre Beziehung zu diesem Anbieter und dessen Datenpraktiken liegt zwischen Ihnen und ihm. Ich empfehle aufrichtig, die Nutzungsbedingungen des KI-Anbieters zu lesen, den Sie verbinden.

3. Verantwortung gegenüber Dritten

Wenn Sie eine Funktion nutzen, die Daten an Dritte überträgt, unterliegen diese Daten der Zuständigkeit dieses Dritten. Ich bin nicht verantwortlich für das, was dieser Dritte mit Ihren Daten macht, wie lange er sie aufbewahrt oder für seine Sicherheitspraktiken.

4. Datenlöschung

Das Löschen einer App von Ihrem Gerät entfernt in den meisten Fällen die lokal gespeicherten Daten. Da ich keine Daten auf eigenen Servern erhebe oder speichere, gibt es auf meiner Seite nichts zu löschen.

5. Kontakt

Brian Ragle

Tennessee, Vereinigte Staaten

E-Mail: bragle@gmail.com

Support: https://brianragle.com/support/