The terms for using AtlasTrack.

Using AtlasTrack means you accept these terms

By creating an account or using AtlasTrack, you're agreeing to what's on this page and to the Privacy page. If you don't agree with something here, the honest answer is: don't use the product, or don't publish/use the specific feature you disagree with — most of AtlasTrack works entirely offline in your browser regardless.

Accounts and screen names

Signing in with Google or Microsoft creates an AtlasTrack account identified by an anonymous account ID — not your real name or email (see Privacy for the details). You choose a screen name, and it's checked against a reserved/offensive-name filter before it's accepted. You're responsible for what you do under your account and screen name.

You can have one personal account. Group/seat-based accounts (an Admin with sub-user seats) are part of the paid tier described below and come with their own account-hierarchy rules once that tier is live.

What's free, what's paid

The boundary is simple and won't move retroactively against you:

• Free, and it stays free: the full visualization engine — timeline, map, relationship, graph views — offline/Nomad Mode use, your personal Voyager Vault, and BYOK AI-assisted editing.
• Paid (not live yet): group accounts with seat-based pricing, a collaborative Fleet Vault for organizations, and API access for automated data integrations.

If it runs entirely in your browser, it's free. If it depends on AtlasTrack's servers beyond basic sign-in and the free storage described above, that's where paid tiers apply once they exist.

Your content

Projects, atlases, and events you create belong to you. AtlasTrack doesn't claim ownership of anything sitting in your local browser storage or in an encrypted Vault — we can't even read a Vault's contents.

Publishing to the Server Library is different. Once you publish something, it's visible to anyone, and you're granting AtlasTrack ownership of that published content. Your screen name stays attached as an author credit, but you're no longer the exclusive owner once it's out there. Full detail on this is on the Privacy page — read it before you publish something you'd want to pull back later, because you may not be able to.

Don't publish anything you don't have the rights to. If you publish someone else's copyrighted work without permission, that's on you, not AtlasTrack.

Acceptable use

The Server Library is community-moderated. Don't:

• Publish content that's illegal, harassing, or infringes someone else's rights.
• Use a screen name designed to impersonate someone or evade the reserved/offensive-name filter.
• Try to break, overload, or reverse-engineer the parts of AtlasTrack that run on our servers (client-side/local behavior is yours to inspect — it's your browser).

Published items can be reported, and reports that cross a moderation threshold can result in takedown. Repeated or severe violations can result in account suspension.

This is a beta — no warranty

AtlasTrack is provided as-is, during active development. Features can change, break, or disappear. Nothing here promises a specific uptime, data-durability guarantee, or that a given feature will work exactly as described at any given moment. Back up anything important — export your local project files, don't rely solely on a Vault or the Server Library as your only copy of something irreplaceable.

To the extent the law allows it, AtlasTrack isn't liable for data loss, downtime, or damages arising from using beta software. If something breaks, tell us — contact info below — but we can't promise a fix on any particular timeline while this is a beta.

Suspension and termination

We can suspend or terminate an account for violating the acceptable-use terms above, or for behavior that threatens the integrity of the Server Library or other users. You can stop using AtlasTrack, and delete your account, at any time — your local browser data isn't affected by deleting your account, since it was never on our servers to begin with.

Changes to these terms

These terms will change as the product changes — that's the nature of a beta. The “last updated” date at the top reflects the most recent real revision, not a boilerplate refresh.

Questions

Reach out at contact@atlastrack.org if anything here needs clarifying.