Citewrite Privacy Policy

Effective date: July 14, 2026
App: Citewrite for macOS
Developer: Luke Steuber
Contact: luke@lukesteuber.com

Citewrite is designed to keep document processing on your Mac. This policy
explains the limited cases in which data leaves the Mac, what the developer's
hosted service stores, and how to remove local and hosted data.

The short version

What runs on your Mac

Core work happens locally:

Citewrite never renames, consolidates, or exports a document you have not
accepted. Rename in Place is collision-safe, journaled, and undoable.
Consolidation copies and verifies files and leaves the source files unchanged.

Optional public-catalog lookups

Public-catalog lookup is off by default. If you enable online lookups, Citewrite
sends a bibliographic identifier it extracted, such as a DOI, arXiv ID, PMID,
or ISBN. If a document has no usable identifier, Citewrite may send its
extracted title. It uses these public services:

Document excerpts are never sent to these catalogs. The catalog operators
process identifiers, titles, network metadata, and responses under their own
terms and privacy notices.

Optional hosted citation resolution

For documents that local tools and catalogs cannot resolve, Citewrite offers a
hosted citation service at api.dr.eamer.dev. The feature is gated by the
online-lookups setting and a confirmation for each batch.

For each document you confirm, Citewrite can send:

The gateway accepts no more than 25 documents in one request. It uses the data
only to produce the requested citation response. Application logging records
method, route, status, and duration; responses include a correlation identifier.
Gunicorn access logging also records the remote network address, request line,
status, response size, referrer, and user-agent string in the host's system
journal. There is no Citewrite-specific journal retention period; entries are
removed as the host journal rotates under its system limits. The gateway does
not write or log filenames, metadata, candidate records, excerpts, generated
citations, API keys, or request bodies. Service records can nevertheless be
linked through an installation identifier, network metadata, or an optional
service credential. Citewrite requires no in-app account or sign-in.

The gateway relays the request to the first available provider in its configured
chain: Groq, xAI, Mistral, OpenAI, Anthropic, or Google Gemini. Availability can
change because providers may be disabled, unavailable, or out of capacity. A
provider receives the prompt needed to answer the request and processes it
under that provider's own terms and privacy practices. Those practices may
include provider-side security logging or retention; Citewrite does not promise
that an upstream provider immediately deletes a request.

Current provider policies are available from
Groq,
xAI,
Mistral,
OpenAI,
Anthropic, and
Google. Provider terms can change; review
the applicable provider's current policy before sending confidential material.

Per-install free-tier quota

If you use the hosted citation service without an API key, Citewrite sends a
random UUID generated for that app installation. It is not an Apple Account,
advertising identifier, hardware serial number, or user account. The gateway
stores only three quota fields: that UUID, the UTC date, and the number of
documents accepted on that date. It does not store the request body in the quota
table.

Quota rows currently have no automatic expiration and remain until the operator
deletes them. The UUID is not a name, email address, Apple Account, advertising
identifier, or hardware identifier. Ordinary access logs separately include the
network and request metadata described above. A global daily-count row is also
stored for service cost control.

If you add a hosted-service API key, Citewrite stores it in the macOS Keychain.
Keyed requests use the gateway's key-based quota records instead of the random
per-install identifier. The gateway stores a hash and prefix for each
service key, its customer label and billing details when configured, last-used
time, and daily request count. These records can be linked to the applicable
service customer. A provider key you supply for direct use identifies your
account to that provider under its own terms.

Your own model provider

You may instead configure Anthropic, OpenAI, Google Gemini, or an
OpenAI-compatible server. Hosted vendors require your own API key; a local
server such as Ollama or LM Studio may not.

This feature is off until you select a provider, enable online lookups, and
confirm a batch. Citewrite then sends the shown filename, extracted metadata,
and bounded excerpt directly to the selected provider. The developer does not
relay these direct requests. The selected provider processes them under its own
terms. API keys are stored in the macOS Keychain and are sent only to the
provider they authenticate.

When the configured server is on your own Mac, the request stays on your Mac.

Optional research evidence synthesis

The research workspace can synthesize excerpts you selected with either a
local server or a hosted provider you configured. A hosted synthesis runs only
after you enable online lookups and confirm that individual run. The
confirmation shows the destination, model, question, instructions, and every
reviewed excerpt before transmission.

Questions, selected excerpts, responses, and provenance are stored locally so
you can revisit them. A hosted provider processes the transmitted request under
its own terms. A local-server synthesis does not leave your Mac.

Local storage

Citewrite stores local data in its macOS sandbox container, including settings,
security-scoped folder bookmarks, batches, document records, extracted study
text, accepted evidence, research imports, synthesis records, and visualization
specifications. API keys are separate generic-password items in the macOS
Keychain. Files you rename, consolidated libraries, sidecars, and exports remain
in the folders you chose.

Deleting the Citewrite application bundle alone does not reliably delete
the sandbox container, Keychain items, renamed source files, consolidated
libraries, sidecars, or exports.

How to delete data

Before deleting Citewrite, you can remove each saved key in Settings. If you
used the keyless hosted service, Settings also shows an Installation quota
ID
. Copy it and email it to luke@lukesteuber.com before deleting Citewrite
if you want its gateway quota rows deleted. Opening Settings does not create an
ID. To remove all Citewrite data from a Mac:

  1. Quit Citewrite.
  2. Delete the Citewrite application from the Applications folder.
  3. In Finder, choose Go → Go to Folder…, enter
    ~/Library/Containers/app.citewrite.macos, and move that container to the
    Trash. This removes local app records, settings, bookmarks, and the random
    per-install identifier.
  4. Open Keychain Access, search for app.citewrite.macos, and delete the
    Citewrite generic-password items you no longer want. Removing the app or its
    container does not automatically remove them.
  5. Separately delete any consolidated libraries, sidecars, or exports from the
    folders you selected. Renamed source files remain where they are; use
    Citewrite's Undo Last Rename before removing the app if you want to reverse
    the most recent rename journal.

Deleting the local installation UUID prevents future use of that UUID but does
not delete historical quota rows already stored by the gateway. To request
deletion of a quota UUID or other gateway record, email
luke@lukesteuber.com. Make the request before deleting the container so you
can copy the Installation quota ID from Settings. Because Citewrite has no
sign-in, the developer needs that ID or information about a service key to
locate the record.

What Citewrite does not do

Legal bases and privacy rights

Optional online processing occurs only at your request to provide the feature
you selected. Where consent is the applicable legal basis, you can withdraw it
by turning off online lookups and not confirming another run.

Depending on where you live, you may have rights to access, correct, delete, or
restrict personal data processed by the developer, and to complain to a privacy
authority. Citewrite stores no in-app account profile. If a hosted-service key
maps to a customer record, that record may include a customer label, billing
details, subscription identifiers, last-used time, and daily request counts.
Email the privacy contact below to request access, export, correction, or
deletion of gateway records, with enough information to locate them. Records
held by a direct or upstream provider are subject to that provider's privacy
process.

California residents: the developer does not sell or share personal information
as those terms are defined by the CCPA/CPRA and does not discriminate against
people for exercising privacy rights.

Children

Citewrite is a research productivity tool and is not directed to children under
13.

Changes to this policy

Updates will be posted at this URL with a new effective date. Material changes
to data handling will also be reflected in app or release documentation.

Contact

Privacy questions and deletion requests: luke@lukesteuber.com

Copyright © 2026 Luke Steuber.