Built different for a changing world

We keep what we must to operate Curio, protect users, honor access choices, and comply with safety obligations. We do not want your private collection to become an advertising profile, a public graph, or a source of unnecessary exposure.

Curio separates account identity, collection membership, image storage, access decisions, and privacy controls so one part of the system does not have to know everything about you.

Curio may keep account records, device records, collection records, membership and sharing settings, payment or entitlement status, safety and security events, and the images you choose to place in Curio.

Private images are treated differently from ordinary account data. The goal is simple: the service should be able to operate access and sharing without casually exposing the contents of your collection.

Curio is built around pseudonymous participation. That means the app can support a Curio-facing identity that is not the same thing as every legal, billing, or safety record required behind the scenes.

Curio is designed so sharing is not just “send a file and hope.” Sharing should be tied to who is allowed in, what collection they can access, and whether that access should continue.

You choose who belongs
        |
Curio checks collection access
        |
The approved device opens the photo
        |
Access can change later

That is the heart of Curio Private: more ceremony around who can receive, open, and keep access to private collections.

Curio is designed with separation of concerns. In plain English: the place that stores an image should not also be the place that decides who gets to open it, and the part that helps open it should not need to know everything about the collection.

Collection rules
who is allowed, what changed, what was revoked
        |
        v
Key service
helps approved devices open approved photos
        |
        v
Image storage
stores protected image data for your collection

This lets Curio provide security without turning every privacy decision into a reason to centralize more personal information than the service needs.

Curio Engine is planned to make collections more useful: preference building, smarter discovery, compatibility between collections and audiences, and guidance that helps curators understand what belongs.

The privacy rule is that analysis is access. If Curio Engine helps with a collection, that should be a choice with a clear purpose, not a silent shortcut around privacy. Users and curators should be able to understand when analysis is on, what it is for, and how to turn it off where controls are available.

Curio Private is being designed for people who need more than a regular share button. Collection access, private-entry controls, security events, and revocation all exist so sharing can feel more like inviting someone into a private room than throwing a copy into a message thread.

Curio may record privacy and security events needed to protect a collection, explain access changes, and help curators respond to misuse. Security events are not preference analytics. They exist to protect the room.

Some features and collections require age-appropriate access. Curio is being designed so people participate in spaces appropriate for them, and so curators do not have to rely on weak “confirm your age” popups for serious safety boundaries.

Age verification may use a specialized third-party provider because verifying identity or age safely is its own discipline. The goal is to confirm what Curio needs for access, not to make your private collection more public inside Curio.

Ordinary app-store apps have limited control over screenshots, screen recording, and device management. Curio does not treat that as good enough for every private use case.

Private Curio may use Apple business, managed-device, or similar elevated controls where appropriate so higher-trust communities can require stronger behavior from participating devices. That adds friction, but for some users the added confidence is the product.

Curio remains useful without that elevated path. The stronger path exists for users and communities that cannot accept ordinary consumer app limits as their privacy ceiling.

• Choose what belongs in Curio and what stays in Photos.
• Use Curio Private for the collections that need stronger entry and sharing controls.
• Decide when Curio Engine can help analyze, organize, or improve a collection.
• Change sharing access as relationships, audiences, or comfort levels change.
• Keep account privacy separate from collection participation where the product allows it.

We will not build Curio around selling private taste to advertisers. We will not treat privacy as a decorative premium badge. We will not intentionally collapse legal identity, public profile, collection taste, image storage, and sharing access into one convenient exposure surface.

When Curio needs information to run the service, protect users, or meet safety obligations, we want that use to be explainable. You should know what a term is for before you accept it.

This marketing website does not host Curio accounts, collections, or product authentication. It does not intentionally set advertising cookies or social-tracking pixels of its own. Hosting providers may process ordinary request data needed to serve and secure the site.

This website is operated by Anteacore. Anteacore is a trade name of Goddard Audioworks, LLC. Questions about this notice can be sent to gaudioworksllc@gmail.com.