JRNL Privacy Policy

1. This website at a glance

• The JRNL marketing website lets you read about the product and view example app screenshots. It does not collect journal entries, run AI composition, or upload your journal when you visit it.
• Its appearance control stores your selected theme in your browser under the local-storage key jrnl-site-theme. This setting stays in that browser until you change it or clear the site’s stored data. It is not an advertising identifier and is not sent to us by the appearance feature.
• The website currently serves its fonts, images, and scripts from its own origin. Its application code does not load third-party analytics, advertising pixels, session-replay tools, or social-media trackers.
• Delivering a page still requires network communication. Our web server and hosting or security providers may process an IP address, requested URL, request time, browser or device information, response status, and diagnostic or security records.
• Links to support and other websites take you to those services. Information you submit there is handled under their applicable notices. This website does not contain an account-registration, payment, newsletter, or support-submission form.

These statements describe the current website. If we introduce materially different collection or optional tracking, we will update the relevant notices and obtain consent or provide opt-out controls where required before the new processing begins.

2. Information involved in JRNL features

The information processed depends on what you use. A description of a feature in this policy does not mean it is available in every release, platform, or plan.

Information you provide. If you create a JRNL account or contact us, we may receive your name, email address, account details, communications, support attachments, and information needed to respond. Paid features, where offered, involve transaction, entitlement, and billing-status information. Payment providers handle payment information under the applicable checkout arrangements; do not send payment-card details through ordinary support messages.

Journal content. The app stores thoughts, entries, tags, preferences, and attachments used for journaling. These can include text, selected photos, drawings, and transcribed speech. Local storage of this material does not itself mean that we receive a copy. Sections 3–5 describe when information can leave the device.

Technical and account records. Online requests may produce service, authentication, device/app-version, usage-count, error, abuse-prevention, and security records. We use these to deliver and protect the requested service and manage access. Content is not automatically included in every diagnostic or usage event.

Connected services. If a JRNL feature lets you connect an outside account, we receive only the information made available through that connection and its authorized scope. Review the connection notice and the other service’s controls. JRNL does not obtain your gaming profiles or social accounts merely because another Lod Softworks product supports them.

We may derive information such as approximate location from an IP address or whether a request succeeded. We do not treat those limited technical inferences as permission to analyze private journal content for unrelated purposes.

3. Local journals and device permissions

JRNL’s core journal workflows are local-first. When you use local capture, reading, editing, search, preferences, or export without invoking a connected feature, the app’s journal files remain on your device. Creating an account does not by itself upload the whole journal.

Photos, microphone access, speech recognition, files, or other device capabilities are used when you invoke a feature that needs them and grant any required permission. Permission to use a device capability is not permission for unrelated advertising, analytics, or cloud processing. Availability and on-device transcription support vary by platform; review the product’s status and permission prompts.

You can manage device permissions through the operating system. Denying or revoking a permission may make its associated feature unavailable. The operating system, device manufacturer, or an independently enabled device-backup service may process data under its own settings and policy, separately from a JRNL cloud feature.

Deleting a JRNL server account does not automatically delete local journal files. Conversely, uninstalling an app or clearing its storage can remove local information without deleting an account or data already stored by a connected service. Export important information before deleting it where the product supports export.

4. Optional AI and automated processing

When you choose a remote AI feature, such as composing a draft from selected thoughts, JRNL sends the selected input and the context described for that feature to the configured service. For AI composition, that includes selected text and requested drafting options. An AI or cloud provider may process the request on our behalf. This is different from on-device processing and requires a network connection.

JRNL does not continuously send your entire journal to AI merely because the feature exists or you have an account. The current JRNL composition service returns an editable draft and does not persist the journal text or source material in its account database. Account entitlements, successful-use counts, and security or audit records are separate from journal content.

Third-party AI providers may have processing, retention, abuse-monitoring, and security-review arrangements that differ from our application database. We do not promise universal zero retention, exclusively automated access, or processing in a particular country unless a specific feature expressly provides that commitment. Ask support about the provider and handling applicable to a feature before submitting material for which those details matter.

We do not use your private JRNL content, or authorize a provider to use it, to train general-purpose AI models without a separate clear notice and affirmative opt-in. Processing needed to deliver your request, and disclosed security or abuse review, are distinct from that training permission. Enabling AI is not permission to turn on sync, backup, advertising, or unrelated optional analytics.

AI output may contain errors or personal information drawn from your input. Review it before saving or sharing. JRNL’s drafting features are not used to make legal or similarly significant decisions about you. Do not include another person’s sensitive or confidential information unless you have an appropriate right or legal basis to submit it.

5. Optional cloud sync and backup

Where a release offers sync or backup and you enable it, designated journal data, attachments, settings, and associated account or device information may be transmitted to and stored by the service and its hosting providers. The feature’s notice and controls explain its scope. This policy does not enable those features for you.

Sync may propagate changes and deletions across connected devices. Backup may preserve copies for the period and restore options described by the product. Neither is the same as requesting AI composition, and neither should be inferred from simply signing in or visiting the marketing website.

Turning a feature off stops future activity associated with that choice as explained by its controls. It does not necessarily delete existing remote copies, complete a pending deletion, or recall data already processed. Use the applicable cloud-deletion controls or contact us for help. Local files, server data, and subscriptions may require separate actions.

6. Why we process information

We use information for the relevant purposes described here: delivering requested features; maintaining accounts and access; processing purchases and usage entitlements where applicable; responding to support and privacy requests; communicating service or security notices; diagnosing failures; protecting users and systems; and meeting legal obligations. Technical and aggregate information can help us improve reliability and usability without treating private journal content as general-purpose analytics material.

Where a law requires us to identify a legal basis, we rely on the basis appropriate to the activity: performing a contract or taking requested pre-contract steps, meeting a legal obligation, legitimate interests such as proportionate service security and reliability where those interests are not overridden by your rights, or consent where required. We do not rely on acceptance of Terms of Use as blanket consent for every kind of processing.

If we want to use personal information for a materially different purpose, we will provide the notice and choice required by applicable law. Consent-based processing can be withdrawn through the applicable control or by contacting us, without changing the lawfulness of processing before withdrawal.

7. Cookies, analytics, and advertising choices

The marketing website’s current storage practice is the appearance preference described in Section 1. It does not currently use optional analytics or advertising trackers. Account-based services on other origins may use authentication, session, or security technologies needed for their operation.

App analytics. We plan to offer optional product-usage analytics in the JRNL app. If introduced, these analytics will be off until you opt in, and the app will explain the information involved. You will be able to withdraw that choice through its controls. This choice is separate from essential online delivery, account, security, and abuse-prevention records, and from AI, sync, and backup choices. Private journal content will not be included merely because you opt into usage analytics.

Website analytics. We may introduce website analytics as a standard part of operating and improving the website. These may process page requests, visits, interactions, referring pages, device or browser characteristics, and related identifiers, as specified in the updated notice. Such processing may run by default only where the relevant technology, purpose, and applicable law permit it. We will not treat a business preference for analytics as proof that a tracker is legally essential. Where prior consent is required, the relevant processing will wait for consent; where opt-out rights apply, those rights remain available. A voluntary toggle for every form of permissible website measurement is not promised by this policy.

We honor applicable privacy choices, including legally recognized preference signals such as Global Privacy Control where relevant. A device permission, an AI opt-in, or accepting the Terms does not replace a legally required analytics or advertising choice. Advertising is a separate activity and is not automatically enabled by either kind of analytics.

We do not sell private JRNL journal content or use it for targeted advertising. The current JRNL marketing website does not sell personal information or share it for cross-context behavioral advertising. Other products’ advertising arrangements do not change this website’s behavior. If practices subject to a sale, sharing, or targeted-advertising opt-out change, we will provide the legally required disclosure and controls.

You can clear website storage through your browser and use available product, browser, or operating-system privacy settings. Clearing the appearance preference resets that preference; it does not delete a JRNL account or local app journal. Browser “Do Not Track” is not the same signal as Global Privacy Control; the website does not maintain a separate Do Not Track response because it currently has no optional cross-site tracking to disable.

8. When information is shared

We disclose information only for the relevant purposes described in this policy, subject to applicable law and your choices. Recipient categories may include:

• Service providers: hosting, infrastructure, security, AI processing, email delivery, support, and payment providers, where used for the requested service. We use appropriate contractual restrictions for providers processing personal information on our behalf.
• People or services you choose: recipients of an export or sharing action, or a service you authorize us to connect. A journal is not made public by the existence of a sharing feature in another product.
• Professional advisers and lawful recipients: advisers, regulators, courts, or other recipients when reasonably necessary for legal obligations, valid process, fraud prevention, safety, or protecting rights.
• Business-transfer participants: parties involved in a merger, acquisition, financing, reorganization, or transfer of the relevant business, subject to appropriate safeguards and legally required notice. Such a transaction does not remove existing privacy obligations.

Information you independently share with another service or person becomes subject to their handling as well. Disconnecting a service does not always erase previously shared copies. We do not claim that pseudonymous identifiers are anonymous; any aggregate or deidentified information must be handled consistently with the applicable legal standard.

9. Retention, deletion, and security

We retain personal information only as long as reasonably needed for the purpose for which it was processed, including providing the requested service, maintaining a necessary account or transaction record, addressing security or abuse, resolving disputes, and meeting legal obligations. The period depends on the information, the feature, account status, and any stated retention setting or legal requirement. A specific product notice or contractual retention commitment controls where one is provided.

Local journal files remain under your device’s storage controls. Server-account deletion and privacy requests affect information within our control; some minimal legal, transaction, security, or audit records may need to remain. Deletion from active systems may precede the ordinary expiration of protected backup copies. Where an exception applies, we limit retained information to that purpose rather than treating it as permission for unrelated use.

We use administrative, technical, and organizational safeguards appropriate to the information and service. No method of storage or transmission is completely secure. This policy does not promise a particular certification, audit schedule, encryption architecture, or recovery guarantee. Protect your device and account credentials, and contact support if you suspect unauthorized access.

10. Your rights and requests

Depending on where you live and whether the relevant law applies, you may have rights to confirm processing, access or obtain a portable copy of information, correct inaccuracies, request deletion, restrict or object to processing, withdraw consent, or opt out of sale, sharing, targeted advertising, or certain profiling. Not every jurisdiction provides every right, and lawful exceptions may apply.

Use available account, app, or device controls, or email privacy@lodsoftworks.com. Identify the relevant product and request; do not send your password, a complete journal, or identity documents unless we explain why particular verification is reasonably necessary. We may need proportionate verification to protect your information. An authorized agent may submit a request where the law permits, subject to appropriate verification of that authority.

We respond within the time required by applicable law and explain applicable denials or exceptions. Where available, you may appeal by replying to the decision or contacting the same privacy address and stating that you seek an appeal. We will not unlawfully discriminate against you for exercising privacy rights. A feature may nevertheless be unable to work without information genuinely needed to deliver it.

If the Utah Consumer Privacy Act applies to the processing, Utah residents can request the rights it provides, including access, deletion of information they provided, a copy of that information, and opt-outs from sale and targeted advertising. Utah incorporation alone does not make every business or activity subject to that Act. You may contact the Utah Division of Consumer Protection with a complaint. Where another privacy authority has jurisdiction, you may complain to that authority as well.

11. Children and teenagers

JRNL is a general-audience product, not specifically designed or marketed for people under 18. Use by a minor may require parent or guardian involvement and is subject to applicable product and provider age rules. The Services are not directed to children under 13.

We do not knowingly collect personal information from children under 13, or a higher age where applicable law requires it, unless a particular service expressly supports that use with the required parental notice, consent, and safeguards. If you believe a child has provided information improperly, contact privacy@lodsoftworks.com so we can investigate and take appropriate action. General website access is not a substitute for any required child-data safeguards.

12. International processing

Lod Softworks is based in the United States. Information submitted to an online feature may be processed in the United States and other countries where the relevant providers operate. Those countries’ laws may differ from yours. Device-local use and remote processing should not be treated as the same activity.

Where applicable law requires a transfer mechanism or other safeguards, we use the legally required arrangements for the relevant transfer. Merely visiting a website or accepting its Terms is not a blanket waiver of international-transfer protections. Contact us for information about safeguards applicable to a feature or request.

13. Changes and contact

We may update this policy to reflect product, provider, or legal changes. The published version will show its last-updated date. For material changes, we provide additional notice appropriate to the service and obtain consent where required before beginning the new processing. Continued use alone is not new consent where the law requires an affirmative choice.

Lod Softworks LLC — Utah, United States
Privacy questions and rights requests: privacy@lodsoftworks.com
Product and support questions: lodsoftworks.com/support
Terms of Use: jrnl.now/Terms