EvalBud LLC provides EvalBud, an independent accomplishment-record and writing-assistance app for the Air Force, Space Force, Army, Navy, Marine Corps, and Coast Guard. EvalBud is not a government system and is not affiliated with or endorsed by the U.S. Government, Department of Defense, or a military service.
Information you must not enter
Do not enter classified information, Controlled Unclassified Information, operationally sensitive or export-controlled information, Social Security or DoD ID numbers, personal medical or disciplinary details, or other information you are not authorized to place in a non-government system. Automated checks cannot identify every restricted fact. Review what you enter, share, or send to AI.
Personal records and optional accounts
Core accomplishment capture and the Personal Log can work on your device without an account. Device data can include your name, service, rank, specialty, duty title, unit, responsibilities, service-readiness and fitness fields, accomplishments, dates, metrics, custom fields, drafts and settings.
If you create an account, Supabase processes your email, account identifier and authentication/session data. After you explicitly link supported device data to that account, profile, accomplishment, preference, readiness and settings data can synchronize while you are signed in. Signing out does not erase local or cloud data.
The selected profile photo and local reminder schedule are device-local in the current app; EvalBud does not include them in its cloud sync, ordinary backup export, analytics or AI requests. Reminders use local operating-system notifications; the reviewed app does not register a remote push-notification token.
Eligible signed-in Pro users can upload supported image and PDF attachments to private storage. File content and metadata, including name, type, size, account-scoped path and related entry, are stored. Authenticated controls and temporary signed links provide access. Deletion removes the local reference and attempts remote cleanup; failed cleanup is retried for the same signed-in account.
AI and saved drafts
When you choose Tell AI, follow-up, generation, revision or an AI-assisted analysis, selected profile fields, relevant accomplishments or draft text, instructions, conversation and generation settings are sent to EvalBud’s backend and OpenAI for that request. Voice entry uses the operating system’s speech-recognition service; EvalBud receives the transcript and does not intentionally store raw voice audio in its data model. Platform speech providers may process audio under their own policies.
Tell AI returns a preview for you to review and save. AI results are drafting aids and may be incorrect; review them before use. Ordinary unsaved Personal AI inputs and responses are not intentionally persisted in the application database by the normal generation route. Network and AI providers still process them; we do not promise a particular third-party retention period or zero retention.
If you explicitly save a signed-in Personal draft, Draft History stores the draft, immutable revisions, generation context and bounded source snapshots, hashes, and validation/provenance records. Restoring creates a new revision rather than erasing earlier revisions. Signed-out drafts and editor recovery can remain on the device. A personal draft deliberately sent for Team review becomes a frozen Team copy with bounded sources and minimal validation/provenance metadata; it is not a live link to your entire Personal Log or revision history.
We process verified account identity, plan status, hashed usage identities and request counts to enforce entitlement, quotas, abuse controls and spending safeguards. Client-reported Pro status is not authority for paid Team Award Package generation.
Team sharing, packages and generated results
Team requires authentication and the applicable workspace permissions. Team processes workspace and member identity, roles and assignments, invitation recipients and delivery state, selected contributed/shared accomplishments, sharing grants and revocations, review comments and decisions, package metadata and frozen sources, generation briefs, source-owner AI-consent records, generated results, and export/audit records. These records are stored on EvalBud’s production services and database so authorized members can collaborate and retrieve them.
Creating an account or joining a Team does not automatically upload your whole Personal Log. Contribution, sharing and routing are user-directed and bounded to selected content. Current server-side membership, role, scope, consent and package rules determine who can read or act on Team content. Military rank, job title or Pro payment does not create permission to another person’s records.
Team Award Package AI generation sends authorized, consented package inputs to OpenAI and stores generation status and results. The initiating person needs both generation authority and active server-verified EvalBud Pro. A recipient or authorized reviewer does not need Pro merely to receive, read or review an existing generated package. Team AI output requires human review before use/export.
Revoking a share or withdrawing source consent restricts applicable future access or generation and can invalidate dependent package use. It does not guarantee that an already exported, copied or previously received document disappears from someone else’s device. Team records, frozen package inputs, generated results and audit/provenance records follow their workspace and safety lifecycle rather than automatic blanket deletion.
Organization administration and verification, sponsored seats, and Team billing are not currently offered.
Safety, reports, blocking and appeals
Acceptable-use acceptance is recorded with the account and policy version. Team content may be screened through automated sensitive-content checks and OpenAI moderation. Moderation processing is separate from optional paid drafting. Users can report content or users, block contact, and submit an appeal where available. Submitted summaries/statements, content references, block records, moderation actions, appeal decisions and audit records are stored and processed by authorized moderation operators. Reports and blocks do not grant general access to another person’s private records.
A support or bad-output report can include the text and diagnostics you submit, an optional contact address, and optional examples of AI input/output or instructions. Review the contents and the anonymized-example choice before submission; you can change that choice. Submitted report fields can be stored even if example use is declined. When permitted, selected example fields can be sent to OpenAI for classification; ordinary report narratives/diagnostics may also be processed for support classification. We do not promise that choosing an anonymized example removes every identifying detail. Do not submit restricted information. Support classification can use a deterministic fallback when AI is unavailable or limited. Email services can receive minimal notification summaries, not the full raw report/example payload.
Purchases, analytics and service providers
Apple or Google processes purchases. RevenueCat processes purchase, restore, receipt, entitlement, subscription-status and app-user-identifier information; signed-in purchase identity is associated with the verified EvalBud account. EvalBud does not receive your full payment-card or banking details.
The app sends a limited allowlist of product events to its backend. If configured, the backend hashes/salts a random installation identifier and forwards product events to PostHog without creating a named person profile. Events may include version, platform, service, Free/Pro status, capture method, entry counts, validation status and coarse feature interactions. The allowlist excludes accomplishment/draft text, names, emails, unit names, attachment metadata and raw support descriptions. The current app does not provide an in-app analytics opt-out. Hashed identifiers are not a promise that all data is fully anonymous.
The public EvalBud website uses Cloudflare Web Analytics, which loads a Cloudflare-hosted JavaScript beacon to measure page views, traffic sources and website performance. This website analytics setup is separate from the mobile app's product analytics, and it does not receive Personal Log, saved-draft or Teamspace content. Cloudflare may process technical information about website visits under its own privacy practices.
When a visitor selects an outbound link to EvalBud's Apple App Store or Google Play listing, the website also sends a minimal event to PostHog containing only the selected store, a broad website-section label, a fixed public service/resource page label, and broad source and medium categories when known. It also records whether the source category came from a recognized campaign tag or the current page’s referrer. Campaign tags are supplied labels, not proof that an advertisement caused a click or install. Each event uses a new temporary random identifier; the website does not set analytics cookies or retain persistent visitor identifiers for this measurement. The event does not contain Personal Log or Teamspace data, full referral URLs, query strings, or visitor-entered content. Browser privacy settings and blockers can prevent events from being recorded, so reported store-link clicks are approximate and are not confirmed installs.
Providers include Supabase for authentication/database/storage, OpenAI for AI and moderation/support processing, RevenueCat and app stores for subscriptions, PostHog for configured analytics, hosting/network/database providers, support email providers, and operating-system services. IP/network data can be processed for delivery, security and rate limiting. Provider policies and infrastructure logs may have their own retention practices.
We do not sell accomplishment content. We disclose information as needed to deliver requested features, facilitate user-directed Team sharing, secure and meter the service, process subscriptions, support users, maintain the service, or meet legal obligations. The app does not use advertising or cross-app tracking in the reviewed production configuration. Data is transmitted to our services using encrypted connections; this is not a claim of end-to-end encryption or government approval.
Exports, deletion and retention
User-created backups, exports and shared documents remain under the user’s control. Portable JSON backups do not include attachment file contents, the device-only photo/reminder schedule, or Draft History revision/validation records. Supported Personal DOCX operations send reviewed text to the backend for document rendering; Team export uses authorized reviewed package records and records export provenance.
Use Settings → Account & Cloud → Delete Account, or request deletion through account-deletion instructions. Team account cleanup must be confirmed before the in-app flow deletes the Personal account. A workspace-owner handoff or a pending/held cleanup may require support assistance; the app reports that deletion is incomplete rather than pretending it succeeded.
The completed Personal deletion flow removes the Supabase authentication account, supported synchronized personal entries/state, Personal Draft History and associated revision/validation records, and account-scoped private attachments. It removes that account’s local Draft History/replay cache and attachment links. Local accomplishment text, profile/settings, device photo, signed-out drafts and user-created exports can remain for local use; remove them separately if desired.
Deleting an account does not cancel an Apple/Google subscription or automatically erase separately stored support reports, hashed usage counts, analytics, transaction/provider records, security/entitlement records, or all Team records. Previously routed frozen copies, review/package provenance, safety reports/actions/appeals and audit records may remain for workspace integrity, dispute handling, security or legal needs. Team cleanup records pending, held, ready or completed states and verifies cleanup; it is not immediate blanket erasure. Contact support to request review of identifiable retained records.
Retention varies by data type, purpose, workspace lifecycle, legal obligations and provider. We do not promise a fixed automatic expiry for categories that have no such implemented rule.
Your choices and contact
You choose whether to create/link an account, upload attachments, use AI, share selected Team content, consent to package AI use, export, or submit reports. You can revoke permitted sharing, use blocking/reporting, review subscription settings with your store, and request deletion as described above.
Contact support@evalbud.com. Include only the account email or report reference needed for support; do not email restricted content, accomplishment files or credentials.