1. Who this policy covers
This Privacy Policy explains how Twinly handles information when you use its website, Android app, and optional Google Photos connection. Twinly is an invitation-only photo organizer. It helps you find similar photos and organize unwanted copies; you decide what to keep, move, or delete.
For questions, privacy-rights requests, or account-deletion requests, contact the Twinly operator at support@twinly.cloud. This policy applies to Twinly, not to Google, your phone manufacturer, or other independently operated services.
2. Information we access and collect
Account and invitation information: your sign-in email, account identifier, authentication records, invitation status, and access-revocation records. Password authentication is handled by our authentication service. Twinly does not ask you for your Google password. The app owner can review invited email addresses and invitation status to manage private access.
Phone photos: with Android permission, Twinly reads photo previews and metadata such as file names, sizes, photo dates, and device media identifiers. It calculates image fingerprints for similarity grouping. Gallery scanning and Animals/People/Places classification run on your device. This phone-gallery scan and sorting flow does not upload your photo images to Twinly cloud storage.
Saved scan results: Twinly automatically saves grouped photo metadata, image fingerprints, device media identifiers, and your Keep/Delete choices to your private account so results can be restored. Image files and thumbnails are not saved by this sync. Metadata and fingerprints are still treated as account information.
Google Photos, if you connect it: Google supplies your connected account email and account identifier, authorization credentials, and information about photos you explicitly select in Google’s Photos Picker, including selected media identifiers, file names, media types, and temporary access information. Twinly’s server downloads resized image previews from Google and sends them to your app or browser for comparison. These previews pass through our service; this import flow does not save them in Twinly’s photo storage. It does not give Twinly unrestricted access to your whole Google Photos library.
Technical and support information: our hosting and authentication providers process connection, security, and error information, which may include IP addresses, browser or device information, request timing, and diagnostic records. If you contact support, we receive the message and any information you choose to include. Do not send passwords, authorization codes, or private photos unless necessary for a request.
3. Why we use information
We use account information to authenticate invited users, maintain account security, and manage access. We use photo previews and fingerprints to show and group similar photos. We use saved metadata and choices to restore your scan results. We use Google credentials only to connect the account you authorize and retrieve the batches you select. We use support and technical information to answer requests, maintain the service, investigate failures, and prevent abuse.
Connecting Google Photos is optional and separate from signing in to Twinly. Each invited user connects their own accounts, and multiple Google accounts can be connected separately. The app owner’s Google account is not used to access other users’ libraries.
Twinly is not a photo backup service. Moving a photo into a local folder does not delete it from Google Photos or transfer it between Google accounts. Twinly cannot delete your original cloud photos through the Google Photos Picker connection.
4. Google data and Limited Use
Twinly’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. Twinly also follows the Google Photos APIs User Data and Developer Policy.
The Google Photos connection requests basic account identification (openid and email) and read-only access to media selected through the Photos Picker (photospicker.mediaitems.readonly). It does not request permission to read Gmail messages or delete Google Photos originals.
Google user data is used only to provide or improve the visible, user-facing photo connection and organization features you authorize. We do not sell Google user data, use it for advertising, build advertising profiles from it, or use it to train generalized artificial-intelligence or machine-learning models. Twinly does not send your Google Photos to a generative-AI photo-quality reviewer.
We restrict transfers of Google user data to what is necessary for the authorized features, applicable law, security, or another purpose specifically permitted by Google’s Limited Use rules. A merger, acquisition, or asset transfer involving such data must remain consistent with those rules and applicable consent requirements.
We do not allow people to read Google user data except with your affirmative agreement to view specific information, when necessary for security or legal compliance, or for another exception expressly permitted by Google’s Limited Use rules. A new use of Google data outside your original permission requires updated disclosures and any additional consent Google or applicable law requires before that use begins.
6. Storage, retention, and security
Account, invitation, connected-account, and saved scan information is retained while needed to provide the service or maintain authorized access. Disconnecting a Google account removes its linked-account record, saved authorization grant, and associated Picker-session records from Twinly’s active database. It does not erase previously saved scan metadata, delete your Twinly account, or automatically revoke Google’s own permission record.
OAuth state and Picker sessions have limited validity; expiry prevents further use but does not necessarily immediately erase the corresponding database records. Imported previews and on-device thumbnails are used for the active photo workflow rather than kept as a permanent cloud photo collection. Clearing an app or browser session ends that session’s preview access.
When you request deletion, we assess and remove information that is no longer necessary, subject to identity verification and lawful retention needs. Security, invitation-revocation, or legal records may need to be retained to prevent unauthorized access or meet legal obligations. Copies in provider backups or logs may remain until their retention cycles expire. We do not promise immediate erasure from every backup or a fixed retention period that our providers have not confirmed.
Safeguards include authenticated private access, user-scoped access checks, and encrypted stored Google refresh credentials. No online service or device can be guaranteed completely secure. Protect your phone, email, and account credentials, and contact support promptly if you suspect unauthorized access.
7. Your choices and privacy rights
You can decline Google Photos linking, select only the photos you want to import, disconnect a linked account in Twinly, and remove Twinly’s Google permission in your Google Account’s third-party connections settings. Android settings let you change photo permissions. Revoking a permission stops future authorized access but does not by itself delete previously stored information.
To request access, correction, export, or deletion of your information or your entire Twinly account, email support@twinly.cloud with the subject “Privacy request” or “Delete my Twinly account.” Include the email used for Twinly, but never your password. You do not need to sign in to send a request. We may request proportionate identity verification to avoid deleting or disclosing another person’s information, and we respond within applicable legal time limits.
An account-deletion request includes a request to remove linked Google grants and saved scan information, except information that must lawfully be retained. Removing Twinly information does not delete photos on your phone or in Google Photos. Where applicable, you may also object to processing, request restriction, withdraw consent, or complain to your local privacy regulator. Your rights depend on the laws that apply to you.
Where data-protection law requires a legal basis, we process information as necessary to provide requested services, with your consent for optional access, for proportionate security and operational interests, or to meet legal obligations. You may contact us about the basis for a particular use. Withdrawing optional consent may make the corresponding feature unavailable.
8. Browser storage and children
The app and authentication services use browser or app storage and session information to keep you signed in and support the service. The application does not include advertising-tracking features. Hosting providers may use essential security mechanisms described in their own notices.
Twinly is not directed to children and does not knowingly collect personal information from children in violation of applicable law. If you believe a child has supplied information without required authorization, contact support@twinly.cloud so we can investigate and take appropriate action.
9. Changes and contact
We will update this page and its effective date when this policy changes. Material changes to data use will be communicated through the app or account email as appropriate, and additional consent will be requested when required. Policy changes do not override Google’s restrictions on previously obtained Google user data.
Privacy, support, and deletion requests: support@twinly.cloud.