Pico Privacy Policy

Effective date: October 29, 2026
Operator: AnAmelie
Project page: https://anamelie.com/projects/pico/
Contact: https://anamelie.com/contact/

1. About Pico

Pico is a private Android app operated by AnAmelie for personal use. The owner shares a public Reddit post, webpage, or direct-image link to Pico from Android’s share sheet. Pico prepares the supported still images with their source and attribution, holds each one for the owner’s review, and uploads only approved images to Google Photos albums that Pico creates. Pico also displays the owner’s photo library for drawing reference and can create Google Drive folders the owner lists.

Pico is not offered as a public service and is not distributed through Google Play. Pico has no server of its own: it runs entirely on the owner’s phone.

This policy covers the Pico app and its Google integration. The surrounding website may have a separate site-wide privacy policy.

2. Information Pico processes

Shared links and prepared images

When the owner shares a link to Pico, the app processes on the phone:

• the shared URL and the source page’s URL and title;
• supported JPEG, PNG, and single-frame WebP image data from that source;
• publicly displayed author, photographer, caption, credit, and attribution information;
• filenames and technical image properties;
• a private archive marker added to prepared files;
• album choices, approval or rejection, upload state, and errors.

Pico writes the source URL and available attribution into each prepared image’s metadata. Requests to source websites come from the phone, so those websites receive the phone’s IP address and ordinary request information under their own privacy policies.

Google account, Google Photos, and Google Drive

Pico signs in with Google on the phone and requests these permissions:

• Add to Google Photos (photoslibrary.appendonly): create albums and upload approved images.
• View photos and albums Pico created (photoslibrary.readonly.appcreateddata): find Pico’s albums, avoid duplicate uploads, recover interrupted uploads, and display those photos in Pico’s library. This permission does not let Pico read photos or albums created outside Pico.
• Google Drive (drive): read the owner’s folder list and the images in them so Pico can display the owner’s library, and create the folders the owner lists in Pico’s settings. Pico never renames, moves, trashes, or deletes files or folders in Drive.

Pico stores on the phone: Google sign-in credentials, identifiers and titles of Pico’s albums, identifiers of photos Pico uploaded, the folder list it read, upload state, and API errors. Pico does not analyze the owner’s Google Photos or Drive contents for any purpose other than displaying them to the owner and keeping folders and albums in order.

Optional attribution research

If the owner turns on attribution research, Pico may send OpenRouter the text of the source webpage (URL, title, caption, alt text, and nearby text) for an image whose credit is missing, to find who made it. Pico never sends image bytes to OpenRouter.

3. How Pico uses information

Pico uses this information only to:

• download and prepare images from links the owner shares;
• preserve source and attribution information;
• present images for the owner’s review;
• create or find Pico’s Google Photos albums and upload approved images;
• read and create the owner’s Drive folders as described above;
• display the owner’s library, pins, and search on the phone;
• recover interrupted uploads and show errors.

Pico does not use Google user data for advertising, profiling, credit decisions, or sale, and does not use it to train AI models.

4. Google API Limited Use disclosure

Pico’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

5. Storage and security

All of Pico’s data stays in the app’s private storage on the owner’s phone: prepared images awaiting review, the review list, settings, library index, pins, and Google credentials. AnAmelie operates no server for Pico and receives none of this data. Pico uses encrypted HTTPS connections to Google and to OpenRouter when enabled; requests to source websites use the URL from the shared link.

No method of storage or transmission is completely secure. The operator uses reasonable safeguards appropriate for a private personal app but cannot guarantee absolute security.

6. Retention and deletion

• Prepared images are deleted from the phone after upload, after rejection, or when they expire unused.
• Uploaded images remain in the owner’s Google Photos until the owner deletes them there.
• Folders Pico created remain in the owner’s Google Drive until the owner deletes them.
• Review history, settings, and the library index stay on the phone until the owner deletes them in the app, clears the app’s data, or uninstalls Pico.

7. Sharing and service providers

Pico discloses information only as needed for its workflow:

• Google: receives sign-in requests, album operations, approved image uploads with their attribution descriptions, and Drive folder requests.
• Public source websites: receive requests needed to retrieve shared pages and images.
• OpenRouter, when enabled: receives the webpage text described above, never image bytes.

These providers process information under their own terms and privacy policies. Pico does not sell personal information or disclose Google user data to data brokers or advertisers.

8. User choices and access revocation

The owner decides which images are uploaded by approving or rejecting each one. Attribution research is off unless the owner turns it on.

Google access can be reviewed or revoked from the Google Account connections page. Revoking access stops further Google Photos and Drive access; it does not delete images already uploaded or folders already created. Uninstalling Pico removes all data it stored on the phone.

For questions or requests, use the AnAmelie contact page.

9. Children’s privacy

Pico is a private personal tool and is not directed to children under 13.

10. Changes to this policy

This policy may be updated when Pico’s functionality, data practices, service providers, or legal obligations change. The effective date at the top of this page will be updated when material changes are published.

11. Contact

Questions or requests concerning Pico and this privacy policy may be directed to:

AnAmelie
https://anamelie.com/contact/