How visibility works
Image access is not a separate permission system. If a visitor can open the connected profile, note, team, trackable, or trackable-group page, that same visitor can open the images attached to it. If they cannot open the parent item, they cannot open the related images either.
The saved stop is an immutable logistics snapshot. If a linked note later moves, the journey keeps the original snapped coordinate so the route history does not silently change.
Trackable read models can also surface the current visible notes at that coordinate, so the route can stay accurate even when nearby notes later change.
Place, history, and access stay separate: the journey stop preserves the snapped coordinate, the note keeps its own editable record, and the note's visibility plus required access scope decides who can open note content.
- Public parents expose their images publicly.
- Private or team-limited parents keep their images private or team-limited too.
- Visible Once Accessed trackables and trackable groups expose images only after the same access rules have been satisfied for the parent item.
- The website and the API both enforce this parent-first rule before any image bytes are returned.
What is stored
LocationNotes does not keep the original full-size upload. After the safety screen passes, the server saves only resized JPEG variants so pages and Android clients can load them directly without on-the-fly resizing.
/Images/Large/{guid}-1024.jpgfor the 1024-pixel maximum-size copy/Images/Medium/{guid}-612.jpgfor the 612-pixel maximum-size copy/Images/Small/{guid}-306.jpgfor the 306-pixel maximum-size copy/Images/Thumbnail/{guid}-64.jpgfor the cropped 64 x 64 thumbnail
The large, medium, and small files keep the original proportions while fitting inside the target size. The thumbnail is always cropped to a square 64 x 64 version.
Gallery cards may still show the original upload dimensions for reference, but the downloadable website and API files are only these resized JPEG variants.
Bulk image upload on LocationNotes.com
LocationNotes.com also has a dedicated Bulk Image Upload workspace for turning a whole image batch into separate notes without typing titles or descriptions before the files are staged.
- The batch always creates one note per image.
- Titles and descriptions start from embedded image metadata, and a missing title falls back to a cleaned-up file name.
- The whole batch saves into one scope at a time: your own account or one team you already belong to.
- One shared category can be applied across the whole batch while each image card still lets you adjust the title, description, and map location individually.
- Trackables are intentionally ignored on this page so the workflow stays focused on note creation from image metadata.
- Mapped images drop pins onto the review map before save, and unfinished batches stay in browser storage on that device until you finish or clear them.
Upload safety screen
Before an image is saved, LocationNotes sends it through an OpenAI moderation check for adult or otherwise unsafe content. This helps reduce harmful uploads, but it is not a perfect guarantee that every bad image will be caught.
- Blocked uploads are rejected before any resized files are saved to disk.
- Allowed uploads are still reportable later if they are offensive, adult, misleading, or posted without the right to publish them.
- Image reporting uses the same support-ticket review flow as other inappropriate-content reports.
What can and cannot be posted
- Allowed examples: product photos, travel or location photos, profile portraits, team identity graphics, and trackable or trackable-group reference images you have the right to publish.
- Team page images are managed by current team admins, while personal profile, note, trackable, and trackable-group images are managed by the people who already have edit rights for those parent items.
- Do not post pornography, exploitative imagery, graphic abuse, hateful imagery, harassment, or content you do not have the right to share.
- Do not assume a public parent means you can publish someone else's copyrighted or private image. Permission to view is different from permission to upload.
Reporting and support tickets
Every image card can show the compact inappropriate-content reporting control. Use it when an image is offensive, adult, deceptive, or does not belong on the connected profile, note, team, trackable, or trackable-group page.
Signed-in reporters can choose to track the support ticket and follow the review status after a super-admin reviews it.
Exports and deletion
When an image is deleted, LocationNotes removes the image record and all of its stored resized copies together. The same GUID-backed image records are also the basis for broader account and team data handling so they stay traceable alongside the parent content they belong to.
Website gallery delete buttons post to the localized website route, while API clients delete the same image record with DELETE /api/images/{contentImageId}.
Related pages
- Bulk Image Upload for the dedicated one-note-per-image upload workspace on LocationNotes.com.
- Image API endpoints
- Privacy
- Delete Data
- Support