Effective date: September 23, 2026
This policy explains how Siftello ("we", "us") handles information when you use the Siftello mobile app or visit siftello.web.app. For privacy questions or requests, contact commonlistapp@gmail.com.
Your photos stay in your photo library
Siftello helps you review and organize photos on your device. It accesses the photos you permit, displays previews and photo details, remembers your review choices, and asks the operating system to apply actions you confirm, such as changing a favorite or deleting selected photos.
Siftello does not upload your photos or thumbnails to us, Firebase, or RevenueCat. Photo-library identifiers, album names, and individual keep or review choices are used locally; they are not included in Siftello's custom analytics events. We do not operate a photo backup service or use your photos to train AI models.
Your device's photo service may separately download cloud-backed originals or synchronize changes with services such as iCloud Photos. Those services operate under their own settings and privacy policies.
Information used by the app
Local app data. Siftello stores settings, onboarding status, optional sharing choices, reviewed photo identifiers, and the review queue in the app's local storage. This lets you resume a cleanup and keep your preferences between launches. No Siftello account is required.
Purchases and access. We use RevenueCat and the store through which you purchase to load offers, verify purchases, restore access, and manage subscription entitlements. RevenueCat assigns a random app user identifier and processes purchase or receipt information, product and transaction identifiers, subscription status, and technical information needed to communicate with its service. This processing can occur when the app checks access, even before you make a purchase. We do not send RevenueCat your photos, name, or email address through the app, and automatic advertising/device identifier collection is disabled in our RevenueCat configuration. Apple or Google handles payment information; Siftello does not receive your full payment card details. RevenueCat also provides purchase reporting so we can understand subscription activity. RevenueCat's privacy information explains its practices.
Optional access codes on Android. If you redeem an access code, the app sends the code and its existing random RevenueCat app user identifier over HTTPS to our Firebase Cloud Functions service. The service checks the code and asks RevenueCat to grant Premium to that identifier without a store purchase. This does not create a sign-in account. Connection information, including your IP address, is processed to handle the request and limit abuse. A hashed IP value and attempt counts are held temporarily in the function's memory for rate limiting; this does not remove the IP address from Google's standard request logs. Those logs can contain IP addresses, request times, technical client information, response status, and timing measurements. We do not intentionally log submitted codes or request bodies, and the feature does not send photos or album names. This processing occurs when you choose to redeem a code, including when optional analytics and crash reporting are off.
Optional usage analytics. If you enable Usage analytics, Google Analytics for Firebase receives information about app use, such as screens visited, onboarding and permission outcomes, cleanup session types and counts, deletion results, and purchase or restore outcomes. The SDK also processes app-instance identifiers and general app, device, and interaction information, including approximate location inferred from the connection's IP address. We use this information to understand which features work well. Our custom events use predefined categories and counts rather than photo content, album names, photo identifiers, or free-form text. Advertising consent remains disabled; we do not use this data for targeted advertising. Google's Analytics data controls explain the SDK's collection settings.
Optional crash and performance reports. If you enable Crash and performance reports, Firebase Crashlytics and Performance Monitoring process technical information such as installation identifiers, app and operating system versions, device characteristics, error types and stack traces, timing measurements, and network performance information. Performance reports can include approximate location derived from an IP address, such as a country. Siftello does not request precise GPS location. This helps us investigate crashes and slowdowns. Siftello's custom error reports remove exception message text and use predefined operation names. Native SDK crash reports may still contain technical diagnostic details. We do not attach photos, photo previews, or album names to reports.
Technical service configuration. Firebase SDKs may make requests to obtain installation identifiers and service configuration even when optional usage and diagnostic reporting is off. These requests may process installation identifiers, IP addresses, and basic app or device metadata needed to configure the services. The optional reporting switches control usage events and crash/performance reports; they do not disable every technical SDK request. These configuration requests do not include your photos or album names. See Firebase's data-processing information.
Support messages. If you email us, we receive your email address and whatever you include in the message. We use it to respond, investigate the issue, and handle your request. Please avoid sending photos, passwords, payment card details, or other sensitive material unless it is necessary for the request.
Your choices
Both optional reporting switches are off by default. You can use the app without enabling them. Change either choice in Settings → Privacy → Help improve Siftello. From version 1.2.1, these preferences are available only in Settings; earlier versions may also show these choices during onboarding. Previously saved choices remain in effect until you change them. These reports are not used for advertising or tracking you across other companies' apps and websites.
Turning off Usage analytics stops new analytics collection and resets Analytics data stored locally by the SDK. Turning off Crash and performance reports stops Siftello's custom reporting and requests deletion of unsent crash reports. The native crash-reporting setting fully takes effect the next time the app starts, so close and reopen the app after disabling it. Changing a switch does not automatically erase reports already received by a provider; you can contact us about that data.
Optional sharing choices do not disable purchase verification or the network requests needed to provide access, including an access-code request you choose to make. You can avoid access-code processing by not using that feature.
You can revoke or limit photo access in your device's settings. The app can work only with the photos the operating system makes available to it. You can clear saved swipe progress in Siftello's settings and remove items from the review queue without deleting the corresponding photos. Device controls for removing app data and backups depend on your operating system.
This website
The website is hosted on Google Firebase Hosting. The hosting service processes connection information, including IP addresses, to deliver pages and protect the service from abuse. We do not add website analytics, advertising trackers, tracking cookies, account registration, or a contact form. The interactive demonstration runs in your browser with sample photographs; it does not access your photo library or upload files. Email contact links open your own email application.
Why we process information
Where data protection law requires a legal basis, we rely on:
- Your consent for optional usage analytics and crash/performance reporting. You may withdraw it in the app without affecting the lawfulness of earlier processing.
- Providing the service or taking steps you request for app functionality, purchase verification, restored access, access-code redemption, and related support.
- Our legitimate interests in delivering and securing the website and access-code service, configuring technical services, preventing fraud and abuse, maintaining service records, and responding to general enquiries, subject to your rights.
- Legal obligations where records must be kept or information must be disclosed by law.
Photo access is controlled separately by your device's permissions. We do not make automated decisions about you that produce legal or similarly significant effects.
Providers and international processing
Google provides Firebase Hosting, Cloud Functions and its supporting Cloud Run/Cloud Logging infrastructure, and the optional Firebase/Analytics services. RevenueCat provides purchase and entitlement infrastructure. Apple and Google provide their respective app stores and payment services. Email providers process messages you send to our support address. Providers receive information for the purposes described above, and may also process service information under their own terms. We may disclose relevant information if legally required or necessary to protect rights and prevent abuse.
These providers operate internationally, including in the United States, so information may be processed outside your country. Applicable provider data-processing terms describe transfer safeguards, including standard contractual clauses where relevant. You can review the Firebase data-processing terms and RevenueCat data-processing addendum, or contact us for information about safeguards relevant to your data.
We do not sell personal information or share it for cross-context behavioral advertising.
How long information is kept
Local settings and progress remain until changed or removed through the app or applicable device controls. Photo retention is governed by your photo library, cloud settings, and the deletion actions you confirm.
Purchase records are retained as needed to verify and restore entitlements, administer subscriptions, handle refunds or disputes, and meet applicable legal requirements. Support correspondence is kept for as long as needed to resolve the request and related issues or legal obligations.
If you redeem an access code, RevenueCat keeps the resulting entitlement record to provide that access. Rate limiting uses ten-minute windows; expired entries are removed when the function next handles a request or when its instance stops. These entries are not a permanent access-code database. Standard server request logs are retained for 30 days under our current Google Cloud Logging configuration. Administrative audit logs follow Google's separate 400-day retention period. See Google's log-retention information. A function's execution region does not determine the location of all provider records or logs.
Optional Analytics data follows the service's configured retention periods and deletion processes. Retention can differ for user-level data and aggregate reports; switching collection off does not remove historical aggregate reports. Google's retention documentation explains those distinctions.
Google states that Crashlytics begins removing crash data and associated identifiers after 90 days. Performance Monitoring begins removing IP-associated events after 30 days and installation-associated or de-identified performance data after 60 days. Firebase Hosting retains IP data for a few months. Provider deletion and backup processing may take additional time. See Firebase's privacy and retention information.
Firebase installation identifiers used for service configuration may remain until deletion is requested. Google describes removal from live and backup systems within 180 days after a deletion request. Contact us if you want help with data associated with an installation; identifying the relevant records may require additional information.
Your privacy rights
Depending on the law that applies to you, you may have rights to access, correct, delete, receive a portable copy of, or restrict processing of your personal information, and to object to processing based on legitimate interests. You may also withdraw consent and complain to your local data protection authority.
To make a request, email commonlistapp@gmail.com. Describe your request and the app or purchase involved. We may need proportionate information to verify the request and locate relevant records. Because Siftello has no account system and does not upload your photo library, we cannot identify every installation from an email address or retrieve your local photos and progress. We will explain any applicable limits rather than ask for unrelated personal information.
Children and security
Siftello is a general-purpose photo utility, not a service designed specifically for children. If you believe a child has provided personal information to us inappropriately, contact us so we can investigate and take appropriate action.
We limit the information sent by the app and use the security features of the device and our service providers. No system can guarantee absolute security. Keep your device protected and maintain independent backups of photos you wish to preserve.
Changes to this policy
We may update this policy when the app, providers, or legal requirements change. The effective date above identifies the current version. Where required, we will provide additional notice or request a new choice before materially changing consent-based processing.