Privacy
Private by design.
Your photos and memory projects deserve careful handling. AoS is designed around account control, project privacy, and clear data boundaries.
Project boundary
A clean placeholder for privacy and workspace boundary visuals, without exposing private UI.
Account access
A clean media slot for account control and project access explanations.
Principles
Careful handling from project to workspace.
Privacy should be understandable at the product level: where projects live, who can access them, and what controls users can expect.
01
Your projects stay yours
AoS is built around personal memory projects, not public galleries or social feeds.
02
Account-based access
Projects belong inside signed-in workspace areas and should be accessed through the account flow.
03
Careful photo handling
Personal photos should be handled with clear boundaries across upload, editing, and project storage.
04
Clear controls coming soon
Future account controls should make project sharing, export, and deletion easier to understand.
Careful wording
Trust without overclaiming.
AoS should avoid privacy language that sounds absolute unless the underlying implementation and legal review clearly support it.
No unsupported security promises
No unverified compliance claims
No public project galleries
No casual access language
Studio privacy
Your workspace is not a marketing page.
The public site explains AoS. The actual projects, uploads, editor work, account area, and future Studio workspace remain private product surfaces.
- Account access
- Private projects
- Editor workspace
- No public feed
AoS Studio
A private home for memory projects.
See how projects, themes, reminders, orders, and future shared workflows belong in one calm workspace.