You're offline. The last computed result is still valid; new calculations will wait until you're reconnected.

Terms of Service

Effective date: 2026-05-27

Terms of Service

Last updated: 2026-05-27

By using Ibis Ballistic you agree to the terms below. They are

intentionally short and practical.

What the app is

A precision-shooting ballistic calculator + logbook. It computes

trajectories, drop, wind drift, and saves your shooting sessions for

later review. The calculations are reference-grade but not a

substitute for a competent shooter's judgement at the rifle.

What you may do

  • Use the app for lawful precision-shooting activities — range

    • practice, training, competition, hunting.

  • Create profiles, log sessions, export your data.
  • Share aggregate community statistics if the logbook.community

    • feature is enabled for your account.

What you may not do

  • Use the app to plan, assist, or facilitate any act of violence

    • against another person.

  • Scrape, automate, or rate-evade the platform. Per-user rate-limits

    • exist; bypassing them is a violation.

  • Impersonate another user, create fake accounts to dodge admin

    • blocks, or use the platform after an admin has rejected your

    approval.

  • Reverse-engineer the application beyond what's allowed by

    • applicable open-source licences.

Disclaimer

The ballistic engine is calibrated against published reference cases

(Litz, Savkin, Vodorezov) and round-trips Sierra / Hornady / Berger

factory data within published tolerances. However:

  • Real-world conditions vary; the operator is responsible for

    • zeroing the rifle and confirming holds on the range.

  • The app is provided AS IS without warranty of any kind.
  • The authors are not liable for any direct or indirect damages

    • resulting from acting on the app's output.

API Terms — /api/v1/* (paying customers)

These additional terms apply to anyone authenticating with an API

key against the public API surface (/api/v1/*). The full API

reference lives in docs/api-v1.md.

  • Fair use. API keys are tied to a single account. You may not

    • resell or sub-license them, share them between distinct

    organisations, or front them with a paid API of your own that

    resells our compute. Internal company use across teams is fine.

  • Plan & quota. Each plan (free / pro / payg)

    • carries a monthly unit quota and a per-minute rate limit. Quota

    resets at the UTC month boundary. Hitting quota returns `402

    quota_exceeded; hitting rate limit returns 429 rate_limited`.

    Both are documented in api-v1.md.

  • Output ownership. Compute results (DOPE tables, trajectories,

    • drone-intercept solutions) are yours; the calculator software is

    ours, licensed under MIT (see LICENSE in the repo). You may

    use the output commercially without attribution.

  • Billing. API billing is currently manual (/admin/api-keys,

    • see docs/api-v1.md); a payment provider has not yet been wired.

    Billing disputes are resolved by writing to the admin contact

    email (below) — chargebacks against a future payment provider

    are not appropriate for the current manual flow.

  • Versioning & sunset. /api/v1 is stable in shape; breaking

    • changes ship as /api/v2, never as a silent change to /api/v1.

    An endpoint heading toward deprecation will carry

    Deprecation: + Sunset: headers (RFC 8594 / 9745) at least

    one calendar quarter before the cutoff; clients can also poll

    GET /api/v1/_status from CI for lifecycle changes.

  • Termination. We may revoke API keys for breach of these

    • terms, of the prohibitions in «What you may not do» above, or

    for abuse patterns that destabilise the service for other users.

Sub-processors & data flows

Data sent to or generated by the app may pass through third-party

sub-processors (Google OAuth, Resend transactional email,

ipwho.is geo-resolver fallback, Railway hosting). The full list

plus operator opt-outs is in

docs/privacy.md § Third parties (sub-processors).

Continued use after a flagged update to that list counts as

acceptance.

Account lifecycle

  • Accounts may be soft-deleted by the user (/profile/delete-account,

    • 30-day grace).

  • Admins may block, reject, or hard-purge accounts that violate

    • these terms.

  • Audit-log records of admin actions are retained for 1 year per

    • the Privacy Policy.

Changes to these terms

We may revise these terms; significant changes will be flagged on the

login page. Continued use after a flagged update counts as acceptance.

Contact

Same admin email as listed in the Privacy Policy footer.

Privacy · Terms · Back to app