AnAmelie

Pico Privacy Policy

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

1. About Pico

Pico is a private, invitation-only Discord application operated by AnAmelie. It accepts a public Reddit post, webpage, or direct-image URL from an authorized Discord user, prepares supported still images with source attribution, returns those prepared images to Discord for individual review, and uploads only approved images to Google Photos albums created and managed by Pico.

Pico is not offered as a public service. Access is limited to Discord users and channels configured by the operator.

This policy covers the Pico application and its Google integration. The surrounding portfolio website may have a separate site-wide privacy policy covering WordPress, analytics, comments, contact forms, cookies, or other website features.

2. Information Pico processes

Discord information

When an authorized user submits a URL or uses Pico’s review controls, Pico processes and may store:

  • the submitted public URL;
  • the user’s Discord user ID;
  • the configured Discord channel ID;
  • Discord message IDs used to prevent duplicate processing and maintain review controls;
  • album selections, approval or rejection actions, upload state, and error state;
  • prepared image attachments and Pico’s review or status messages in Discord.

Pico ignores ordinary conversation and messages from users or channels that are not configured for access.

Source websites and prepared media

To process a submission, Pico may retrieve a public Reddit page, public webpage, direct image, and related public page assets. It may process:

  • supported JPEG, PNG, and single-frame WebP image data;
  • source URLs and canonical page URLs;
  • publicly displayed author, photographer, caption, credit, and attribution information;
  • filenames and technical image properties;
  • a private archive marker added to prepared files;
  • temporary prepared copies of images awaiting approval.

Pico embeds the source URL and available attribution into prepared image metadata. Requests to source websites originate from the server running Pico. Those websites may receive the server’s IP address and ordinary HTTP request information under their own privacy policies.

Google account and Google Photos information

Pico uses Google OAuth 2.0 and requests Google Photos permissions to:

  • create albums and add approved media to Google Photos; and
  • inspect albums and media created by Pico.

These permissions do not grant Pico general read access to images or albums created outside Pico.

Pico may process and store:

  • Google OAuth access and refresh credentials;
  • identifiers, titles, and product URLs for albums created by Pico;
  • temporary Google Photos upload tokens;
  • identifiers and product URLs returned for media uploaded by Pico;
  • upload status and Google Photos API errors.

Pico does not download or analyze the general contents of the user’s Google Photos library.

Optional attribution research

If the operator enables OpenRouter-based attribution research, Pico may send OpenRouter a bounded set of public information for images whose publisher credit is missing. This information may include the source-page URL and title, candidate image URL and filename, alt text, caption, and nearby text. Pico does not send image bytes or the complete webpage to OpenRouter for this purpose.

3. How Pico uses information

Pico uses this information only to:

  • validate and process an authorized submission;
  • download and prepare supported still images;
  • preserve source and attribution information;
  • prevent duplicate processing;
  • present individual review controls in Discord;
  • create or locate Pico-managed Google Photos albums;
  • upload images explicitly approved by an authorized user;
  • recover interrupted or partially completed uploads;
  • diagnose errors, protect the service, and maintain its private deployment.

Pico does not use Google user data for advertising, profiling, credit decisions, or sale.

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

Pico is operated on a private server controlled by the operator. Its persistent storage may contain:

  • a SQLite database containing source details, Discord control identifiers, review and upload state, album mappings, Google upload tokens, and Google media identifiers;
  • temporary prepared media that has not yet been uploaded, rejected, or expired;
  • Google OAuth client credentials and authorized-user credentials.

OAuth files are stored with restricted filesystem permissions. Pico uses encrypted HTTPS connections when communicating with Discord, Google, and OpenRouter when enabled. Requests to public source websites use the HTTP or HTTPS URL supplied or discovered from the submitted source; HTTP connections are not encrypted. Access to the deployment and its configuration is restricted to the operator.

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

6. Retention and deletion

Pico applies the following retention behavior:

  • Prepared but unused media expires after seven days.
  • Successfully uploaded media is deleted from Pico’s local prepared-media storage after Google Photos confirms completion.
  • Confirmed rejection deletes that review item’s local prepared-media file immediately.
  • Uploaded media remains in the user’s Google Photos account until the user deletes it there.
  • Discord messages and attachments remain subject to Discord’s retention behavior and the server’s moderation or deletion settings.
  • Source details, review history, upload state, album mappings, Discord control identifiers, upload tokens, Google media identifiers, and rejected records may remain in Pico’s SQLite database until the operator deletes them.
  • OAuth credentials remain stored until they are replaced, revoked, or deleted.
  • Operational logs may be retained according to the server operator’s logging and backup configuration.

A user may contact the operator to request deletion of information retained by Pico. The operator may retain limited records when reasonably necessary for security, troubleshooting, backup integrity, or compliance obligations.

7. Sharing and service providers

Pico discloses information only as needed to operate the workflow:

  • Discord: receives submitted URLs, prepared-image attachments, review controls, and status messages.
  • Google: receives OAuth requests, album operations, approved image uploads, source-attribution descriptions, and related API metadata.
  • Public source websites: receive requests needed to retrieve submitted pages and images.
  • OpenRouter, when enabled: receives the limited public attribution evidence described above.
  • Hosting and infrastructure providers: may process stored data or network metadata as necessary to operate the private server.

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

Authorized users control whether an image is uploaded by selecting an album and pressing Add to Google Photos. They may reject an image instead, which prevents upload and deletes its local prepared-media file.

Google authorization can be reviewed or revoked from the user’s Google Account connections page. Revoking access prevents future Google Photos API access but does not automatically delete images already uploaded to Google Photos, Discord messages, or historical records retained by Pico.

Users may delete uploaded images through Google Photos and may use Discord’s available message-management controls. For access, correction, or deletion requests concerning information stored directly by Pico, use the AnAmelie contact page.

9. Children’s privacy

Pico is a private personal tool and is not directed to children under 13. The operator does not knowingly authorize children under 13 to use Pico.

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/