← Back to GP2SM
Privacy Policy
Last updated: February 25, 2026
The short version: GP2SM transfers your photos from Google Photos to SmugMug. We don't store, analyze, or keep your photos. They pass through our servers in memory during transfer and are immediately discarded.
What GP2SM Does
GP2SM ("we", "our", "us") is a data migration tool operated by Glen Fiebich. It copies photos you select from your Google Photos library to your SmugMug account. You choose which photos to transfer using Google's Picker interface, and you choose which SmugMug gallery receives them.
1. Data Accessed (Data Collection)
When you use GP2SM, we access the following types of data:
Google User Data:
- Google account email address and profile name: Obtained through Firebase Authentication (Google Sign-In) to identify your account within GP2SM.
- Selected photo content and metadata: When you use Google's Picker to select specific photos, GP2SM accesses the photo files (image data) and associated metadata (filename, MIME type) for those selected items only. We use the
photospicker.mediaitems.readonly scope, which limits access exclusively to photos you explicitly select — we cannot browse or access your full Google Photos library.
SmugMug Data:
- SmugMug account information: Your SmugMug username and gallery list, used to let you choose where to upload photos.
2. Data Usage
We use Google user data exclusively to provide the photo transfer service:
- Email address and profile name: Used solely for account authentication, identifying your transfer jobs, and sending optional email notifications about transfer status (if you enable notifications).
- Selected photo content: Downloaded from Google Photos and uploaded directly to your SmugMug account. Photo data passes through our server's memory during transfer and is never written to disk, cached, or retained after the transfer completes.
- Photo metadata (filename, MIME type): Used during transfer to preserve filenames and set correct file types when uploading to SmugMug. Filenames are included in transfer history records so you can see which files were transferred.
We do not use your Google user data for advertising, marketing, analytics, profiling, training machine learning models, or any purpose other than performing the photo transfer you requested.
3. Data Sharing
Your Google user data is shared only as follows:
- SmugMug: Your selected photo content and filenames are transmitted to SmugMug's API to complete the transfer you requested. This is the core function of the service — transferring your photos to your own SmugMug account at your direction.
- Firebase (Google Cloud): Your email address, authentication tokens, and transfer job metadata are stored in Firebase services (Authentication and Firestore), which are operated by Google Cloud. Firebase is used as our backend infrastructure.
We do not sell, rent, license, or share your Google user data with any advertisers, data brokers, analytics providers, or other third parties. No third party receives your data except as described above.
4. Data Storage & Protection
What we store:
- SmugMug OAuth credentials: Your SmugMug access token and token secret are stored in Firebase Firestore so you don't have to re-authorize each session. These are stored in security-rules-protected documents accessible only to your authenticated Firebase account.
- Transfer job records: Metadata about each transfer (photo count, gallery name, completion status, filenames) is stored in Firestore to display your transfer history. No photo content or image data is stored.
- Email notification preferences: Your notification settings, if configured.
What we do NOT store:
- Your photos or image data — photo content passes through server memory during transfer and is immediately discarded
- Your Google access token — this is held in browser memory only and is never written to any database or persistent storage
- Photo EXIF data, location data, or face recognition data
- Your Google Photos library structure or contents beyond the items you select
Security measures:
- All data is transmitted over HTTPS/TLS encryption
- Firestore security rules restrict each user's data to their authenticated account only — no user can access another user's tokens or transfer history
- SmugMug OAuth credentials are stored in a private Firestore subcollection protected by security rules
- Google access tokens exist in browser memory only for the duration of the session
- Server-side Cloud Functions run in Google Cloud's secured infrastructure with no persistent local storage
5. Data Retention & Deletion
Retention periods:
- SmugMug OAuth credentials: Retained until you disconnect your SmugMug account or request deletion.
- Transfer job records: Retained indefinitely to provide transfer history, unless you request deletion.
- Google access tokens: Not retained — exist in browser memory only and are discarded when you close the browser tab or end your session.
- Photo content: Not retained — exists in server memory only during active transfer (typically seconds per photo) and is immediately discarded after upload to SmugMug.
How to delete your data:
- Revoke Google access: Remove GP2SM from your Google account at any time via Google Account Permissions. This immediately prevents GP2SM from accessing any of your Google data.
- Disconnect SmugMug: Sign out of GP2SM to stop future transfers.
- Request full data deletion: Email glen@gp2sm.com to request deletion of all your stored data, including SmugMug credentials, transfer history, and account information. We will process deletion requests within 30 days and confirm completion by email.
Third-Party Services
GP2SM relies on the following third-party services to operate:
- Firebase (Google Cloud): Provides authentication, database (Firestore), Cloud Functions, and hosting. Firebase Privacy Policy.
- Google Photos Picker API: Provides the photo selection interface and read access to selected photos. Google Privacy Policy.
- SmugMug API: Provides gallery listing and photo upload functionality. SmugMug Privacy Policy.
No other third-party services receive your data.
Your Control
- You choose exactly which photos to transfer — GP2SM cannot access photos you don't select.
- You can revoke GP2SM's access to your Google account at any time via Google Account Permissions.
- You can disconnect SmugMug by signing out of GP2SM.
- You can request deletion of all your stored data by emailing glen@gp2sm.com.
Google API Services Limited Use Disclosure
GP2SM's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically, GP2SM:
- Only uses Google user data to provide the photo transfer service you requested
- Does not transfer Google user data to third parties except as necessary to complete the transfer to SmugMug at your direction
- Does not use Google user data for serving advertisements or marketing
- Does not use Google user data to train machine learning or AI models
- Does not allow a human to read your Google user data unless you provide affirmative consent, it is necessary for security purposes, it is required to comply with applicable law, or the data is aggregated and anonymized for internal operations
Changes to This Policy
We may update this privacy policy from time to time. Changes will be posted on this page with an updated "Last updated" date. Continued use of GP2SM after changes constitutes acceptance of the updated policy.
Contact
For questions about this privacy policy or to request data deletion, contact: glen@gp2sm.com