Information used by the app
Almost Crossed helps you build a personal map of memories and explore possible shared places and dates with someone you choose. The app reads the date and location information attached to photos and videos you allow it to access. Your chosen name, optional avatar, settings and personal map data are stored on your device. The app processes your memories on your device to build your personal map and timeline. You do not need an Almost Crossed account.
Versions with import features can add places and dates from files you choose from Google Photos, a Google Takeout ZIP archive, a Google Maps Timeline export, events from calendars you select, or a calendar file (.ics). You can also add a dated pin, use a link containing coordinates, or confirm a place and date from a selected image, text file or the first page of a PDF, such as a ticket or booking. Supported versions can read text in some photos to suggest additional places.
Almost Crossed reads and processes these materials on your device. We do not receive original photos or videos, export files, documents or recognized text as part of the import. The app saves place, time and source details on your device for your map. When importing from your calendar, the app reads selected event information with your permission, leaves your calendar as it is, and does not save event titles or descriptions. Almost Crossed does not ask you to sign in to Google or sync these sources in the background. If you open Google Photos, Google Takeout or Google Maps, or select files from cloud storage, the service you use handles those actions under its own policies.
The app uses Apple Maps on iPhone and Mapbox on Android for the base map. These map services may receive requests for the areas displayed and technical connection information. The app draws your memory points on the map on your device.
Comparisons and sharing
Your chosen name can be visible to nearby devices looking for people in Almost Crossed. When you compare memories, the devices exchange encrypted information. The other person may see your name, avatar, the relationship start date entered for the comparison, matching places and dates, and confirmation of shared access. Places and dates from imported sources can take part if both app versions support them. The app shares your timeline of cities and dates, including cities without matches, when you both separately agree to share it.
A temporary relay may carry encrypted messages and process connection details such as session identifiers, IP addresses and delivery logs. If you share a card or timeline through another app, the recipient and service you choose receive what you share. You can manage camera, nearby-device, local-network and notification permissions in your device settings.
Optional analytics
App analytics are optional. The Share app analytics choice in setup and Settings controls usage analytics, crash reports, performance information and attribution together. If you decline, these optional services stay off. Turning the choice off stops new collection and clears unsent app analytics, but cannot recall information already received. Declining does not affect comparisons or purchases.
When you agree, Google Firebase, Amplitude and AppsFlyer may receive app interactions, diagnostic and performance information, crash reports and attribution data, together with app, device and installation identifiers. We use this information to understand use, fix problems and measure how people find the app. These services are not intended to receive your original photos or videos, private comparison content or full location history. The providers and controls available to an older installed copy may differ. We do not treat a choice made for a narrower set of services as consent to newly added services.
We do not show third-party ads or sell your data for money. Analytics is separate from the information that app stores and RevenueCat need to validate and restore purchases. Reading this policy is not consent.
Purchases
If you buy Full Access, the relevant payment provider processes your payment. This may be Apple, Google Play or, where offered, Robokassa. We receive information needed to confirm the purchase, restore access, handle refunds and prevent fraud, such as a transaction or order identifier, product, status and a device access key. We do not receive your full payment-card number.
For a Robokassa purchase, we provide the amount, order details and receipt email. Robokassa processes the payment and may issue a tax receipt. We retain the email and order information needed to verify or restore access and assist you. If you request email-based recovery, Yandex Cloud Postbox sends a one-time code. A person with whom you share access may see that access is confirmed, but not your receipt, card details or store password.
For a website purchase in Russia, we use the email you provide, the order amount, number and status, the version of the terms you accepted, and technical connection information. This lets us create and protect the order, check whether payment is available, provide a receipt and restore access. The checkout page uses an essential cookie for up to 24 hours so you can continue an order and check its status in the same browser. It contains no email address or card details. Robokassa processes the payment on its own page.
If checkout offers Share purchase statistics and you select it, we use the type of device used to visit checkout and information about checkout, payment and restoration to produce summary statistics. The restoration platform may also be recorded if you have enabled app analytics. The summary report contains no email address, IP address, full browser identifier or card details. We do not send these records to external analytics services. You can buy, receive your receipt and restore access either way. To withdraw consent, contact support from the email address used for the order.
Support and website visits
If you contact support or send in-app feedback, we receive what you provide, such as your email, message, rating, attachments and any app or device details included with it. We use this information to respond and investigate the issue. We may use support tools, including OpenAI, to help handle a request.
When you visit our website, hosting and security providers process ordinary connection information such as IP addresses and request times. We also use Cloudflare Web Analytics for page-view and performance statistics. According to Cloudflare, that service does not use cookies or local storage to track visitors. See Cloudflare Web Analytics.
Service providers
We share information only as needed to provide the features above, process purchases, respond to support requests, operate the website and measure app use when you enable it. The relevant providers are listed below. Meta and TikTok may apply to older installed copies. Current optional analytics uses Google, Amplitude and AppsFlyer. Providers acting for us must protect information under their applicable agreements. Stores and payment providers may also process information under their own policies. We may disclose information when law requires it or to protect the service and its users.
- Analytics and diagnostics. Google, Amplitude, AppsFlyer.
- Purchases. Apple, Google, RevenueCat, Robokassa, Yandex Cloud Postbox.
- Support and website visits. Resend, OpenAI, Cloudflare.
- Attribution in some installations. Meta, TikTok.
- Maps. Apple Maps, Mapbox.
- Service hosting. Amvera, Render.
Why we process information
Where the law requires a legal basis, we use information to provide the app and purchases you request, comply with legal duties and pursue legitimate interests in security and support. We use separate consent for optional app analytics and website purchase statistics. Device permissions and analytics choices can be changed in the app or system settings. Withdrawing consent does not undo processing that already occurred.
Retention and deletion
Your photos stay in your photo library or the service where you keep them. We do not receive copies of those photos or a list of places from your personal map. To remove places and dates saved in Almost Crossed, open Manage saved data in Settings. Resetting or uninstalling the app removes its local data. Some protected purchase records may remain so you can restore access.
If you enabled analytics, uninstalling the app does not erase technical information already sent for statistics and diagnostics, such as the app version, performance or crash information. We keep this information as needed to understand use and fix problems. Analytics providers may have their own retention periods. You can ask support to delete this information.
We keep order records as needed to restore access, handle refunds and disputes, and comply with the law. We keep support requests to respond and investigate the issue. Temporary comparison sessions are removed after they end or expire. The other participant may still have results you already shared.
Your rights and choices
Depending on the law that applies to you, you may request access to, correction or deletion of your personal information, a copy of it, or limits on its use. You may turn off Share app analytics in Settings, object to certain processing or request an applicable advertising-related opt-out. To make a privacy request, email almostappsup@gmail.com and mention Almost Crossed. We may ask for the minimum information needed to find your records and verify the request. You can also complain to the relevant data-protection authority.
Where information is processed and how we protect it
When the app uses the Russia processing region, Amvera servers in Moscow handle temporary QR comparison sessions and server-side purchase verification. Robokassa orders and recovery of those purchases also use our Russian infrastructure. The app uses services hosted by Render for the international route.
The app’s processing region determines which Almost Crossed server handles these operations. App stores, map services and analytics providers, if you enable analytics, process information for their own functions. This processing can take place outside your country, including in the United States. You can ask support about processing countries and transfer safeguards.
Connections to the server are encrypted, and the app encrypts comparison messages on your device before sending them. Email-based recovery of a Robokassa purchase uses a one-time code.
Children
Almost Crossed is not directed to children under 13. A higher minimum age or guardian consent may apply under local law. Contact us if you believe a child has provided personal information.
Changes
This policy describes Almost Crossed across app versions, including future updates, until we replace it. We will revise the policy and its date when our practices change, notify you of material changes where required, and ask for a new choice when the law requires one.
Operator details
Show legal operator information
Almost Crossed is provided by Alexander Rysev, who is responsible for the processing described in this policy. For privacy requests, contact almostappsup@gmail.com.
