Service Providers and Technology
Last updated October 17, 2026
The services that help operate One-Line Journal, the information involved, and the software used to build it.
On this page 9 sections
1. About this list
Umuuwa LLC uses the services below to operate One-Line Journal and its website. This list complements the Privacy Policy. It describes the services that receive information, rather than treating every software dependency as a recipient of personal data.
“Service provider” is used here as a practical description. A company’s legal role depends on the service and information involved. It may process some information on our behalf and control other information independently. Providers may use their own downstream providers. Links to public processing terms or subprocessor lists do not, by themselves, establish which agreement, account setting, location, or retention period applies to a particular record.
2. Clerk — accounts and authentication
Clerk provides sign-in, authentication sessions, account management, and supported profile-image handling. Relevant information includes account identifiers, email, selected profile details or images, credentials handled through its authentication service, and authentication/session/security metadata. Our app connects the Clerk identity to the app’s own records. Clerk is not the store for your journal entries.
Clerk’s data-processing terms distinguish customer personal data processed on a customer’s behalf from information for which Clerk has its own responsibilities. Google and Apple sign-in can also involve the platform services described below.
3. Convex — app backend and data storage
Convex runs the application backend and stores account-linked app records, including saved journal text, dates and prompts, progress and league activity, notification preferences and installation records, and the identifiers needed to connect those records to an account. Backend functions enforce ordinary account access and perform scheduled reminders and cleanup.
Private journal text is not public league content. Operator and provider access needed to run the backend is distinct from access through another user’s account. Retention and deletion are described in the Privacy Policy; application deletion is not a promise of immediate erasure of every provider log or backup.
4. Expo — updates, diagnostics, and notifications
Expo services support app builds and updates, app observability, and push notification delivery. Relevant end-user information can include app and operating-system versions, installation/session/update identifiers, route or startup/performance information, JavaScript error details and native crash information, network request information, and push tokens and notification payloads.
Push delivery passes through Expo to Apple Push Notification service or Google Firebase Cloud Messaging. Those platform services are downstream participants in delivery. Notification payloads are used to route and display the message; this is not a journal-text export or AI feature. Expo Observe is a separate diagnostic path from Sentry and documents a minimum of 90 days of metric retention, not a universal maximum.
Build tooling can process the app’s source and bundled assets. That tooling is distinct from user journal storage in Convex. Provider access for support or active troubleshooting may be possible under the applicable service terms; we do not promise that no provider personnel can ever access processed information.
5. Sentry — errors and optional bug feedback
Sentry processes technical error reports and feedback you voluntarily submit through Report a bug. Our app configuration minimizes error-report fields and filters identifying user information out of those reports. Feedback can include the message, name, email address, or other material you choose to provide. Older app versions may have different diagnostic settings.
Enabled feedback features may provide automated summaries, categories, or spam classification, including AI-based processing. This concerns submitted feedback and should not be confused with sending your journal entries for AI analysis. Avoid including private journal passages or sensitive information in a bug report. Sentry retention varies by record type and configuration; deleting an app account does not establish immediate deletion of all feedback or diagnostics.
6. Vercel — website hosting and measurements
Vercel serves the website and receives the network and technical information needed to handle requests. The marketing pages use Web Analytics for visit measurements and Speed Insights for website performance. Information can include page or route, referrer, selected query information, time, approximate location, browser/operating-system/device details, network information, and web-performance measurements.
Vercel describes these analytics products as not using cookies to track visitors. The self-hosted legal pages do not run the website’s client-side analytics scripts, although hosting request processing still occurs. Hosting, measurement, and provider account information can have different processing roles and retention.
7. Apple and Google — platforms, sign-in, and push
Apple and Google distribute the app through their stores and provide their own account, operating-system, review, and security services. If you select their sign-in options, account identifiers and permitted basic profile information are shared through the sign-in flow. Apple may supply a private relay email address. This does not grant access to friends lists, social posts, Gmail messages, or Google Drive files.
Apple Push Notification service and Google Firebase Cloud Messaging participate in notification routing and delivery, including platform device or installation identifiers, tokens, and message payloads. Removing an app’s backend push registration does not establish that every platform identifier or provider backup has been erased. The companies also independently process information for their platform and store services under their own policies.
8. Correspondence and former policy hosting
When you email support@one-line-journal.com, your email service and the services delivering and storing our business correspondence handle the message and any attachments. Include only what is needed to answer your question. The website does not submit an email or a privacy request merely because you open a mail link.
Termly hosted our earlier policy documents and privacy-request form. These replacement pages are served by our website without a Termly script. New requests can be sent directly to the support email; you do not need to use the old Termly form. Historical Termly requests and records are not erased by this website change.
9. Technology used to build the service
The mobile app is built with React Native, React, Expo, and TypeScript. Convex powers its backend and Clerk supplies the account interface and authentication. Rive is used for app animations. Device-local data uses platform storage through Expo SecureStore and AsyncStorage. The website uses SvelteKit, Svelte, TypeScript, and Tailwind CSS.
Software frameworks and libraries are not automatically companies receiving personal information merely because they are included in the app. Fonts, icons, animations, and other bundled assets are also distinct from an external tracking service. This is a practical overview of the main technologies, not a complete dependency inventory or a guarantee of any provider’s certification.