Aurora / Mood Surgeon

Privacy policy

Effective26 August 2026

A clear handoff

Your photos stay close.
AI leaves a trace.

This policy explains what Aurora - Mood Surgeon processes, what remains on your iPhone, and what is sent to a third-party image model when you ask Aurora to create an edit.

Local projects by default AI transfer on request No account or ad profile

Who this is for

This Privacy Policy applies to the Aurora mobile application, its local project features, its in-app coin purchases, and its AI image-generation flow. In this policy, "Aurora," "we," or "us" means the publisher of the Aurora app. "You" means the person using it.

Aurora is designed as a local-first iPhone app. It does not require an Aurora account, a cloud project library, or a social profile.

What Aurora handles

The app handles only what is needed to import, edit, remember, and export a mood. The labels below describe the normal path in the current build.

On device

Photos and project files

Your selected original, preview, masks, prompts, Mood Field values, anchor instructions, generated versions, and challenge records are stored in the app's local Documents area. Aurora does not create a separate face template or biometric profile; a face in a photo remains image content.

Sent on request

AI edit inputs

When you complete the Generate gesture and consent to the handoff, Aurora sends the selected image plus the prompt, mood direction, output size, and area instructions required for that edit.

On device

Voice transcript

If you choose voice input, iOS on-device speech recognition turns your words into editable text. The voice audio is not sent to the image provider by Aurora.

Apple handled

Purchases

Apple processes App Store payments. Aurora stores a local coin balance and processed transaction identifiers so a verified purchase is not granted twice.

On device

Settings and credentials

Preferences and consent state use local app storage. The configured service credential is read from the iOS Keychain after its one-time bootstrap migration.

Not collected by Aurora

Unneeded signals

Aurora does not request precise location, contacts, advertising profiles, chat history, or a persistent account identifier. There is no analytics or ad SDK in the current app code.

From your request to a final image

The following is the end-to-end behavior implemented by the current Aurora image service. Nothing is uploaded merely because a photo is opened or a Mood Orb is moved.

  1. You choose GenerateAurora waits for an explicit generation gesture and the AI data-use consent shown in the app.
  2. The image is preparedThe selected image is resized to a maximum 2048-pixel longest side and encoded as a JPEG data URI for the request.
  3. Instructions are composedAurora combines your prompt, Mood Field direction, and KEEP / TRANSFORM area instructions into one edit request.
  4. HTTPS POST is sentThe app sends an OpenAI-compatible JSON request with a Bearer credential to the configured image endpoint.
  5. The provider returns outputThe service returns base64 image data or a temporary image URL. If a URL is returned, Aurora downloads it over HTTPS.
  6. The result is handled locallyAurora decodes the image, calculates its local Mood Match score, and saves the result as a project version on this device. If the response includes a request ID, it is kept in that local version record for troubleshooting.
Important: Aurora does not send voice audio, location, photo-library history, or chat history as part of this image request. A photo containing a face may be sent when you ask for an edit, but Aurora does not create a separate biometric identifier. A provider may still receive ordinary network metadata and may retain content or logs under its own terms.

Which model receives the request?

The current default build is configured for Agnes AI's image endpoint and the agnes-image-2.0-flash model. The request uses an OpenAI-compatible shape; that does not mean the default build is calling OpenAI's public API directly.

POST https://apihub.agnes-ai.com/v1/images/generations
Authorization: Bearer <service credential>
Content-Type: application/json

{
  "model": "agnes-image-2.0-flash",
  "prompt": "<your cleaned prompt + mood + area instructions>",
  "size": "1024x1024 | 1024x768 | 768x1024",
  "extra_body": {
    "image": ["data:image/jpeg;base64,..."],
    "response_format": "b64_json"
  }
}

The endpoint and model are configuration values. If a release is configured to use an OpenAI endpoint instead, the same categories of input would be sent to OpenAI, and OpenAI's applicable API terms and data-use policies would govern that processing. See OpenAI API data-use information and OpenAI policies.

What stays on your iPhone

Aurora writes projects to the app's sandbox, including an original JPEG, a preview, mask PNGs, project JSON, and version JPEGs. Temporary export files are placed in the app cache and can be cleared from Settings. The app does not operate a remote Vault.

Deleting locally

Use Clear Vault to delete local projects, versions, and masks, or delete the app to remove its sandbox. Use Delete temporary AI files to clear cache files. iOS backups may retain app data according to your device settings.

Deleting remotely

Aurora cannot control a provider's retention of a request, response, safety record, or network log. For a provider-side request, use the provider's support or privacy channel and include the approximate request date or request ID if Aurora displayed one.

Only when you ask

Photos

Aurora uses the system photo picker so you can choose an image. It requests photo-library access only for the action you select, including saving a result to Photos.

Camera

The camera is used only after you choose Camera to capture a source image. The captured image follows the same local-first and explicit-generation flow.

Microphone and speech recognition

Microphone access is active only while you choose voice input. iOS on-device speech recognition produces editable text; Aurora does not add that audio to the AI image request.

When information leaves Aurora

  • AI image provider: the selected source image and edit instructions are sent only after you request generation and accept the in-app AI data-use handoff.
  • Apple: Apple handles App Store purchase authorization and transaction verification. Aurora does not receive your full payment card details.
  • System destinations: if you choose Save to Photos, Save to Files, or Share, iOS sends the result to the destination or people you select.
  • Legal or safety requests: Aurora may disclose information if required by law, court order, or a good-faith safety obligation.

Aurora does not sell your photos or use them for advertising.

Choices and rights

You can decline AI data-use consent, continue typing instead of using voice input, choose which image to import, clear local projects, clear temporary files, and control Photos, Camera, Microphone, and Speech Recognition permissions in iOS Settings.

Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or obtain a copy of personal information. Because Aurora has no account system, most requests can be completed directly in the app. For a question or a request involving this policy, email privacy@aurora.app.

How long data remains

Local projects remain until you delete them, clear the Vault, remove the app, or iOS removes them. Consent and local settings remain until reset or the app is deleted. Temporary exports are kept in the cache until cleared or removed by iOS.

The third-party provider controls its own retention of submitted content, generated output, abuse-prevention records, and technical logs. Review the provider's current terms before sending sensitive or confidential imagery.

Reasonable safeguards

Aurora uses the iOS app sandbox for local files, the iOS Keychain for the configured service credential, and HTTPS for image-service requests and returned-image downloads. No internet transmission can be guaranteed to be perfectly secure, and no app can guarantee that a third-party service will be error-free.

Age-aware use

Aurora is not directed to children under 13, or the minimum age required in your location. We do not knowingly collect personal information from children. If you believe a child has provided personal information, contact us so we can review the situation.

Changes to this policy

We may update this policy when Aurora's features, providers, or legal obligations change. The effective date at the top will change with a revision. Continued use after an update means the revised policy applies to future use; a material AI-data change will be presented in the app before the next generation request when practical.