Who owns an annotation that stays attached to a place?

AR anchors make virtual arrows, notes, reviews, and reminders genuinely useful: the content can stay attached to a real location instead of living only in one session. ARKit supports world anchors that can reappear across sessions, and ARCore Cloud Anchors can be resolved by other devices and assigned a time-to-live.

But what happens in a shared office, rented apartment, or public venue? If my mixed-reality note remains visible to the next tenant or visitor, can the creator, property owner, platform, or current occupant edit or delete it? Who handles a misleading review or a private reminder left in the wrong place?

I’d prefer explicit ownership, visibility, moderation, and expiration controls—possibly automatic deletion unless an anchor is renewed. Persistence is the feature, but it could also turn physical spaces into unmoderated, reputation-bearing data layers. Disagree, propose a permission model, or share examples from spatial-computing prototypes.

I’d separate the anchor from the annotation. The anchor is a coordinate reference; the note, author, audience, and expiry belong in an application layer. That makes deletion and migration possible without pretending the physical location itself has an owner.

The current occupant needs a visible “what is here?” view, not necessarily unilateral deletion. Otherwise a landlord could erase useful maintenance notes, while a previous tenant could leave social baggage behind. Permission needs to be legible at the moment someone encounters the layer.

The documented APIs establish persistence, sharing, time-to-live, and removal mechanisms. They do not establish who has authority over a place-linked annotation. That distinction matters: a technical delete function is not the same thing as a governance rule.

Expiration helps, but renewal can become a tracking mechanism. I’d want opaque, rotating identifiers and access decisions made before resolving private annotations. Otherwise the system may reveal that something exists at a location even when it withholds the text.

Users will not manage four ownership roles every time they pin a reminder. My product-shaped answer is defaults: creator controls content, venue controls public visibility, and occupants get a simple report/remove request. Exceptions can go through moderation instead of a permissions spreadsheet.

Make the policy travel with the data. An annotation should carry creator, scope, expiry, renewal history, and deletion authority, with a local cache that honors tombstones offline. Otherwise different apps will resurrect content after someone thought it was gone.

I’m not convinced property owners should control everything visible in a space. That turns “ownership” into a censorship lever. A restaurant should remove harassment from its premises, but perhaps not erase an independent accessibility note merely because it dislikes the review.

The ugly operational question is appeals. A coworking operator may need to remove a dangerous instruction immediately, then preserve an audit record while the creator contests it. “Delete” should probably mean hidden from normal viewers, with narrowly controlled retention for disputes.

For a prototype, I’d start with seven-day anchors and an explicit renew button. Long-lived persistence is opt-in, and the UI shows who can remove the item. Cheap, understandable, and enough to test whether people actually return to spatial notes.

We used to call this leaving a note on a door, except now the door cannot peel it off. Give every note an expiry and a plainly visible owner. If nobody renews it, let the place forget.