Privacy Policy

Last updated: August 19, 2026

EvalBud is an unofficial, local-first accomplishment tracking and writing-assistance app for military evaluations and award packages. This policy explains what EvalBud 1.1 handles, when information leaves your device, and the choices available to you.

Important data warning

EvalBud is not a U.S. government or Department of Defense system and is not approved to receive classified information, Controlled Unclassified Information (CUI), operationally sensitive information, export-controlled information, medical or disciplinary details, Social Security numbers, DoD ID or EDIPI numbers, deployment-sensitive information, weapon-system-sensitive information, or other protected or restricted data. Keep mission and personnel details generic.

Local-first use and optional accounts

You can use EvalBud without creating an account. Accomplishment entries, profile and service information, custom fields, generation settings, display settings, and usage-limit state are stored in the app’s local storage on your device.

An EvalBud account is optional. If you create or sign in to an account, cloud synchronization starts automatically while you are signed in. EvalBud uses Supabase for email-and-password authentication, persisted sign-in sessions, database synchronization, cloud storage, and the account-deletion function.

Cloud-synced information can include:

• your account email address and account identifier;
• profile information, including optional name, service branch, rank, specialty, duty title, unit, duty responsibilities, scope, administrative fitness or readiness fields, and selected character or initials;
• accomplishment entries, dates, titles, notes, categories, tags, metrics, impact, results, custom fields, and attachment metadata; and
• generation preferences and app display settings.

Signing out does not erase local data or cloud data. A selected profile photo and the local reminder schedule are not included in cloud synchronization.

Attachments and cloud storage

Signed-in EvalBud Pro users may choose to upload images or PDF attachments. EvalBud stores the file, file name, type, size, storage path, and related entry identifier in Supabase cloud storage and synchronized entry data. Attachments are accessed through account controls and short-lived signed links, but no online service can guarantee perfect security. Do not upload restricted information or unnecessary information about other people.

AI processing

AI features are optional. When you ask for a follow-up question, structure an entry with Tell AI, generate a draft, or request a revision, EvalBud sends the selected profile fields, entry content, instructions, conversation text, draft text, and generation settings needed for that request to the EvalBud server. The server forwards that content to OpenAI to produce the requested result.

AI requests also include a RevenueCat App User ID so the server can verify access and enforce daily limits. The server stores a one-way hash of that identifier with the date, plan level, and daily assist or generation counts. If you are signed in, EvalBud links the RevenueCat identity to your EvalBud account identifier; otherwise RevenueCat supplies an anonymous app identifier.

The 1.1 server code does not write ordinary AI request content or generated responses to the EvalBud application database. OpenAI still processes the content as EvalBud’s AI service provider, and this policy does not promise a third-party retention period. A local sensitive-data check blocks several recognizable patterns, but it cannot identify every kind of restricted information. You remain responsible for reviewing content before sending it.

Product analytics

EvalBud sends a limited, allowlisted set of product events to its server. When analytics is configured, the server salts and hashes a random installation identifier and forwards the event to PostHog without creating a PostHog person profile. Events cover app launch, onboarding and walkthrough completion, capture or accomplishment saves, completed AI and draft actions, reminder actions, support submission, paywall views, and purchase or restore completion.

Allowed analytics properties are limited to app version, platform, service branch, Free or Pro plan, coarse product or source, entry count, validation pass or fail, and whether a support notification email was sent. Analytics does not include accomplishment text, generated drafts, profile names, email addresses, unit names, attachment metadata, support descriptions, or error text. The analytics installation identifier is separate from an EvalBud account and there is no in-app analytics opt-out in version 1.1.

Purchases and subscriptions

Apple or Google processes subscription purchases through the store account used on your device. RevenueCat processes product, purchase, restore, entitlement, subscription-status, and app-user-identifier information so EvalBud can show and verify Pro access. EvalBud does not receive your full payment-card or bank-account details.

When you are signed in, EvalBud uses your EvalBud account identifier as the RevenueCat App User ID so Pro access can follow the account. Deleting an EvalBud account does not cancel a subscription and does not delete records held by Apple, Google, or RevenueCat. Manage or cancel the subscription separately through the store.

Support communications

Support reports are sent only when you choose to submit one. A report may include the issue type, affected feature, your description, expected behavior, reproduction steps, error text, relevant AI input or output, custom instructions, an optional contact email, and your choice about anonymized example use. EvalBud also attaches app version, platform, operating-system version, device model, subscription status, RevenueCat environment, submission time, and the most recent app error. It does not automatically attach your accomplishment log, profile, or generated drafts.

Submitted reports and diagnostics are stored in EvalBud’s support database. OpenAI processes the core report and diagnostics to categorize, summarize, prioritize, and group issues. Relevant AI input, problematic output, and custom instructions are included in that AI triage only when you affirmatively allow anonymized example use; those fields are still stored with the report whether or not you opt in.

An email service provider may receive the report reference, issue summary, category, feature, severity, platform and operating-system information, app version, and optional contact email to notify EvalBud support. Raw report details are not copied into that notification email. If you open the direct-email option, your email app and email provider handle the message you choose to send.

Voice entry, photos, reminders, and device services

Voice entry is optional and uses the speech-recognition service available through your device’s operating system. EvalBud receives the transcript and does not store a raw audio recording in its local or cloud data model. The platform speech provider may process audio under its own settings and terms. If you save or send the transcript, it is handled like other accomplishment or AI content.

A profile photo you select is copied into EvalBud’s local app storage. It is not cloud-synced, included in EvalBud backup exports, or sent to AI. Weekly reminders are local operating-system notifications; EvalBud does not register a push token or send the reminder schedule to its server.

Exports and backups

JSON backup and CSV export files are created on your device and may contain profile information, accomplishments, settings, and attachment metadata. Attachment file contents and the device-only profile photo are not bundled in the JSON backup. Importing a backup is processed locally, but imported supported data can later synchronize automatically if you are signed in.

To create a DOCX draft, EvalBud sends the draft title and text to its server, which returns the generated file without writing the draft to the EvalBud application database. When you use a share button, the operating-system share sheet and the destination you select receive the file or text. You are responsible for protecting copies saved to Files, cloud drives, email, messaging apps, or other destinations.

Basic network processing and service providers

When the app contacts an online service, the EvalBud server and service providers necessarily process request and network information. The server uses request IP addresses transiently for rate limiting. Version 1.1 does not document a fixed retention period for every server-side or provider record.

Service-provider categories used by version 1.1 include Supabase for authentication, database synchronization, storage, and account deletion; OpenAI for AI drafting and support triage; RevenueCat and the Apple App Store or Google Play for subscriptions; PostHog for configured product analytics; backend hosting and PostgreSQL database services; SMTP or email providers for support notifications; and operating-system services for speech recognition, notifications, document and photo selection, and sharing.

Account and data deletion

While signed in, you can choose Account & Cloud → Delete Account. The implemented deletion flow removes the Supabase authentication account, synchronized cloud entries and user state, and files in the account’s attachment storage. Local accomplishments, profile information, settings, the local profile photo, and other on-device data remain on that device so EvalBud can continue in local mode.

Request deletion of your EvalBud account and associated cloud data without opening the app.

Account deletion does not automatically remove separately stored support reports, anonymized product analytics, hashed AI usage counts, exported files, or store and RevenueCat subscription records. It also does not cancel an active subscription. For help deleting identifiable records outside the automated account flow, or if you no longer have access to the app, email support@evalbud.com with “EvalBud account deletion request” in the subject. Include only the account email or support-report reference needed to locate the records; do not send restricted content.

Security and retention

EvalBud uses platform and provider access controls, but no app or online service can guarantee complete security. EvalBud does not claim to be DoD-approved and must not be used for classified, CUI, protected, or restricted information.

Retention varies by data type and service. Version 1.1 does not implement or document one fixed retention period for support reports, hashed AI usage counts, analytics events, or third-party subscription records, so this policy does not promise one. Cloud account data is removed through the implemented account-deletion flow described above; local and exported copies remain under your control until you delete them from the applicable device or destination.

Contact

Questions or requests can be sent to support@evalbud.com.