PhotoPort Privacy Policy

PhotoPort is a macOS app from Blackpepper Ltd. that syncs Apple Photos media to Google Photos under your control. This policy explains what data PhotoPort accesses, why it needs that data, how it is stored, and how you can manage or delete it.

Last updated: July 4, 2026

Short version

PhotoPort performs one-way sync from Apple Photos to Google Photos. It does not modify or delete your local Apple Photos library.
You choose what to sync: selected albums, future albums, or your entire Photos library if you turn that mode on.
Your photos and videos are uploaded from your Mac to your Google Photos library. They are not uploaded to PhotoPort servers.
Google OAuth tokens are stored in macOS Keychain. Local sync state stays on your Mac and, where enabled, in your private iCloud container for PhotoPort metadata.
PhotoPort does not sell user data, use Google Photos data for advertising, or use Google Photos data to train AI or machine learning models.

1. Who we are

PhotoPort is operated by Blackpepper Ltd. You can contact us through the PhotoPort support form.

This policy covers the PhotoPort website at photoport.app, the PhotoPort macOS app, and backend services used for authentication, licensing, trial usage, and app integrity.

2. Data PhotoPort accesses or collects

Apple Photos data on your Mac

PhotoPort requests Photos library access so it can read your album list, folder structure, selected album membership, media identifiers, filenames, creation metadata, and the photo or video bytes needed to prepare and upload the items you choose to sync.

PhotoPort uses this access only for sync features shown in the app. It does not modify, reorganize, or delete your local Apple Photos library.

Google Account and Google API data

PhotoPort uses Google OAuth so you can connect the Google Account that receives uploaded media. The app shows the connected account email so you know which Google Account is active.

PhotoPort requests these Google permissions for these purposes:

Permission	Why PhotoPort uses it
`photoslibrary.appendonly`	Upload photos and videos, create app-created Google Photos albums, and add uploaded media to those albums.
`photoslibrary.readonly.appcreateddata`	Read albums and media items created by PhotoPort so sync can resume, avoid repeated uploads, and reconcile app-created albums.
`photoslibrary.edit.appcreateddata`	Update PhotoPort-created album titles, add or remove PhotoPort-uploaded items from app-created albums, and keep app-created album organization in sync with your settings.
`drive.metadata.readonly`	Read Google Account storage quota information only, so PhotoPort can estimate available storage before syncing. PhotoPort does not read Google Drive files.
`openid` and `email`	Identify and display the connected Google Account and keep account-specific app settings separated.

Local sync and app data

PhotoPort stores local sync records such as selected album IDs, generated Google Photos album IDs, uploaded media mappings, upload status, retry state, rate-limit wait state, license status, and error logs. These records let the app resume after a crash or restart and avoid uploading the same item repeatedly.

Backend, licensing, and trial data

PhotoPort backend services support secure OAuth token exchange, per-install request signing, license activation, license status checks, free-trial usage, download tracking, and support requests. The backend may process an install identifier, license key or license status, hashed account identifier, trial media counts, download event metadata, request-signing metadata, and operational logs. Trial usage is counted by completed uploaded media items, not by the contents of your library.

Payment data

If you buy PhotoPort through the website, payment is handled by a payment processor such as Stripe. PhotoPort does not store full credit card numbers. We may receive purchase status, license fulfillment information, billing email, and transaction identifiers needed to deliver and support your license.

Website data

The public website does not require account registration to browse. Hosting providers may process standard server logs such as IP address, browser type, requested URL, referrer, and request time for security, diagnostics, and abuse prevention. When you download PhotoPort, the backend records a download event with limited request metadata such as source page, IP address, user agent, referrer, and time so we can measure downloads and diagnose abuse.

3. How PhotoPort uses data

To upload selected photos and videos from Apple Photos to your Google Photos library.
To create, reuse, rename, and update PhotoPort-created Google Photos albums based on your Apple Photos album and folder selections.
To track completed uploads, retry interrupted work, respect rate limits, and recover from app crashes or restarts.
To show sync progress, sync history needed for app operation, storage estimates, warnings, and error messages.
To show the connected Google Account and give you a clear way to sign out.
To activate licenses, enforce the free trial limit, prevent abuse, and provide support.
To secure the app and backend, investigate operational failures, and comply with legal obligations.

4. Google API data use and Limited Use

PhotoPort's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

PhotoPort uses Google API data only to provide and improve user-facing sync features that are visible in the app.
PhotoPort does not sell Google user data.
PhotoPort does not use Google user data for advertising, retargeting, personalized ads, credit-worthiness, or lending.
PhotoPort does not use Google Photos data to create, train, or improve AI or machine learning models.
Humans do not read your Google Photos data except where you explicitly ask for support involving specific data, where necessary for security or abuse investigation, or where required by law.

5. Sharing and processors

PhotoPort shares or transfers data only as needed to operate the app and services:

With Google APIs, to perform the uploads and Google Photos album operations you authorize.
With backend infrastructure providers, to run authentication, licensing, trial, and security services.
With payment processors, to process purchases and license fulfillment.
With email or support providers, when needed to respond to support requests or deliver license information.
When required to comply with applicable law, enforce terms, prevent abuse, or protect users and services.

PhotoPort does not sell your personal data or Google Photos data to third parties.

6. Storage, security, and retention

On your Mac: Google OAuth tokens are stored in macOS Keychain. Sync state, logs, settings, and album mappings are stored locally for app operation.
In iCloud: If iCloud is available for PhotoPort metadata, PhotoPort may store sync state needed to resume on another Mac signed in to the same Apple account. Photo and video files are not stored in PhotoPort's iCloud metadata records.
In transit: PhotoPort uses HTTPS for Google API and backend communications.
In backend systems: License, trial, request-signing, and operational records are retained as long as needed to provide the service, support purchases, prevent abuse, satisfy legal obligations, and maintain security.
In Google Photos: Uploaded photos and videos remain in your Google Photos library until you remove them or Google removes them under its own policies.

7. Your controls and deletion choices

Photos access: You can manage PhotoPort's Apple Photos permission in macOS System Settings > Privacy & Security > Photos.
Google Account connection: You can sign out in PhotoPort settings and revoke access from your Google Account permissions page.
Album selections: You can select, deselect, and apply album changes from PhotoPort settings.
Local app data: PhotoPort settings include controls to clear local sync data and reset settings.
Google Photos content: When supported by Google Photos APIs, PhotoPort can remove PhotoPort-uploaded items from PhotoPort-created albums if you choose that option. Google Photos APIs may not allow PhotoPort to delete media directly from your Google Photos library; you can always manage and delete your Google Photos content directly in Google Photos.
Backend data: You can request deletion of backend license, trial, download, or support records through the PhotoPort support form. Some records may be retained where required for fraud prevention, accounting, legal compliance, or security.

8. Storage quota and upload quality

Media uploaded to Google Photos through the Google Photos API is stored by Google at original quality of the uploaded file and counts toward your Google Account storage according to Google's policies. PhotoPort may prepare media according to your selected upload quality before upload; that can reduce the file size PhotoPort sends, but the uploaded files still use Google Account storage.

9. Children

PhotoPort is not directed to children under 13 and should not be used by children under 13. If you believe a child has provided personal data to PhotoPort, contact us so we can take appropriate action.

10. Processing location

PhotoPort-controlled personal data is processed in the United States only. App processing happens on your Mac, and PhotoPort backend records for authentication, licensing, trial usage, and support are processed on United States-based infrastructure. Google, Apple, payment processors, hosting providers, and email providers may process data under their own privacy terms when you use their services.

11. Changes to this policy

We may update this policy as PhotoPort changes. If we materially change how PhotoPort uses Google user data or other personal data, we will update this page and provide notice or consent prompts where required before using data in the new way.

12. Contact

For privacy questions, support, or data requests, use the PhotoPort support form.