From first photo to field note.

Start a discovery and use the camera or choose existing media. Add between 1 and 10 photos or videos showing the same find. Each photo can be up to 100 MB; each video can be up to 1 GB. Tallgrass accepts supported RAW photos, although RAW decoding varies by camera format. If a RAW file cannot be prepared, export a JPEG and try again.

Add a caption and place if useful. Tallgrass currently requires a precise location to post and shares that exact map point with signed-in members. Check the map point before you submit, especially for a home, sensitive habitat, or another person's property.

Tallgrass saves a working draft on your device when local storage is available. Files upload in resumable chunks and can be staged before you press Add. Keep the app or page available while a large transfer is active. If a transfer stops, reopen the draft and retry instead of selecting different files with the same upload request.

Unfinished server upload sessions expire after 24 hours. A saved local draft and a staged server upload are separate, so clearing browser or app storage can remove the local copy even while a staged upload remains temporarily on the server.

Allow AI sharing in Profile before requesting analysis. Tallgrass checks permission again at the provider boundary for the requester and every discovery owner whose media is included. Turning it off stops new, queued, and retried provider requests; saved results remain.

Tallgrass prepares viewing copies and thumbnails before analysis. Video analysis uses sampled frames without sending video audio. New media also needs a valid content-screening result before it can publish. If preparation or analysis fails, keep the discovery and use Retry when shown.

AI reports estimate identity, rarity, encounter quality, behavior, and photographic quality. Standings and category boards use those saved results. They are a game and learning aid, not an expert determination.

If the identification appears wrong, open the discovery and choose Challenge identification. Add a concrete reason, such as a visible field mark or likely look-alike. A challenge requests a deeper reassessment and may uphold, revise, or leave the result inconclusive.

Use comments to discuss a resolved discovery. You can delete your own comments. Use Report on a discovery, comment, or member and give a concise reason for operator review. Use Block to hide each member's content and activity from the other; you control when to unblock.

Reports are not emergency services. Contact local emergency services when someone is in immediate danger. See the Community Guidelines for conduct and content rules.

Sign in with an eligible Badland account using Google or verified email and password, or use Sign in with Apple. A signed-in Tallgrass account can link an Apple identity from Profile; it does not automatically merge accounts by matching email.

Delete an individual discovery from its detail page. To remove live Tallgrass data, open Profile and choose Delete Tallgrass data. This removes Tallgrass records and files and requests revocation of a linked Apple authorization. It does not delete the separate Badland account. The Privacy Notice explains backup and audit-record limits.

Enable notifications from Profile, then allow them in the system prompt. You can change the permission later in iOS Settings. Remote completion notifications also depend on Tallgrass's Apple push configuration.

When asking for help, email [email protected] with your account email, device or browser, what you were doing, and the exact message shown. Do not send passwords, sign-in codes, session tokens, or private RAW files by email.