Privacy policy
This policy explains what FigSync processes when it pairs your iPhone with your Mac and moves screenshots or media into the cloud folder you selected.
On this page
The short version
- We do not sell personal data, show behavioural ads, or track you across other companies’ apps and websites.
- The iPhone app does not ask you to sign in with Apple or Google; it pairs to your Mac with a short-lived six-digit code.
- In iCloud mode, media is written to your iCloud Drive. In Google mode, media is sent to your own Google Drive folder and may be temporarily stored by FigSync for delivery.
- The iOS app creates no separate standalone account; it securely pairs with the FigSync account already connected on your Mac.
1. Who is responsible
FigSync is operated by the FigSync developer. Privacy and account-deletion questions can be sent to borderwalker99@gmail.com.
2. Data we process
Account and device identifiers
We process the provider identifier returned by Apple or Google to link your account. Pairing and quota services use derived account identifiers; the provider identifier can also remain in the local account configuration used for sign-in. When available, we store your email address, display name, and profile picture from the connected account so the Mac plugin and paired iPhone can show which account is connected. Public profile information is synchronized through the FigSync service to your paired iPhone. We also store the device name and public-key fingerprint supplied by your iPhone to identify the binding and verify pairing, session refresh, disconnect, and deletion requests.
In Google mode, the service stores your account email address, destination folder identifiers, and authorized access or refresh credentials to deliver selected files to your Google Drive. FigSync does not receive your Apple or Google password.
Product interaction and quota data
We record sync mode, screenshot or album source, requested and accepted item counts, reservation state, timestamps, and delivery confirmation. This enforces the daily quota, prevents duplicate charging, and lets retries recover safely.
Photos and videos
FigSync processes only media you explicitly send. In Google mode, selected media passes through the FigSync media service to your Google Drive folder. Some upload paths first store temporary media in Google Cloud Storage so delivery can continue after an interrupted connection. Native iCloud-mode media is coordinated into your iCloud Drive container on-device. Protected retry files may remain on your device until delivery succeeds, you cancel them, or stale intake files are removed.
Operational logs
Cloud hosting providers may process network and security logs, such as request time, status, and IP address, under their own security and retention controls. FigSync does not use an advertising analytics SDK and does not intentionally send photo contents to analytics services.
3. Why we use it
- Authenticate and pair the correct iPhone and Mac.
- Deliver selected files to the correct iCloud Drive or Google Drive folder.
- Reserve, commit, or refund quota atomically.
- Detect replay, tampering, duplicate delivery, and service abuse.
- Provide support and diagnose failed delivery without treating an unconfirmed upload as success.
4. Services involved
- Apple: App Store distribution and iCloud Drive when Apple mode is selected.
- Google: Google Drive when Google mode is selected, Google Cloud Run, Firestore, and related hosting infrastructure.
- Your design tool: the FigSync plugin receives files through your local FigSync connection.
These providers process data under their own terms. Data may be processed in regions where the relevant provider operates.
5. Retention
Temporary media in Google Cloud Storage is subject to a lifecycle deletion rule after 7 days. Deletion is asynchronous and may occur later. Deleted objects can remain recoverable under the storage provider’s soft-delete policy for an additional 7 days; this is not a promise of immediate or seven-day physical erasure.
Disconnecting a device or signing out does not automatically delete the shared account profile or Google authorization credentials stored by FigSync. These records have no automatic expiry tied to disconnection. You can revoke FigSync access in your Google Account to stop further authorized access; revocation does not itself erase stored records. Contact us at borderwalker99@gmail.com to request account-data deletion.
- Pairing codes expire after 5 minutes and incomplete pending bindings are reclaimed after 10 minutes.
- Active mobile sessions remain until you disconnect the iPhone or the Mac revokes the connection.
- Disconnect and revocation receipts may be retained briefly so a lost network response can be retried safely.
- Daily quota and delivery audit records are scheduled for deletion after 90 days.
Firestore TTL deletion is asynchronous, so physical deletion can occur after the stated expiry time. Files already delivered to your iCloud Drive or Google Drive remain there until you delete them through that provider.
6. Your controls
In the FigSync iPhone app, open Settings to disconnect this iPhone. You can also disconnect either paired iPhone from the Account panel in the Mac plugin.
Disconnecting does not delete files already stored in your iCloud Drive, Google Drive, or design files. You control cloud files through Apple or Google. For a broader support request, email us at the address above.
7. Security
Device private keys stay in the iPhone Keychain/Secure Enclave and are not uploaded. Sessions are short-lived and key-bound; refresh, deletion, and handoff operations require signed proofs. Provider revocation credentials are encrypted at rest. Requests that cannot prove final folder delivery are not reported as successful.
8. Children and changes
FigSync is a professional productivity tool and is not directed to children under 13. We may update this policy when the product or legal requirements change. Material changes will be reflected by the date at the top of this page.