Privacy Policy
Updated: August 12, 2026
Who we are
In this Policy, PatternLabs means the PatternLabs Service and the person who operates it (“we”, “us”). Contact: support@patternlabs.org. Automatic messages may come from no_reply@patternlabs.org — that address is not for user inquiries.
This Policy does not cover third-party sites or services opened via external links or embedded in the Service that act as independent data controllers.
Who may use the Service
We do not knowingly collect data from people who cannot validly consent or enter an agreement under applicable law. If we learn that such data was obtained without a proper basis, we will take reasonable steps to delete or restrict processing.
What we process
Account & sign-in
- Email — registration, OTP sign-in, access recovery, and service messages.
- Google Sign-In — when you sign in with Google, we receive your Google Account identifier, email address and, where provided by Google, your name and profile image. We use this data to create your account, authenticate you, and keep the account secure. We do not receive your Google Account password. Google’s own terms also apply to the sign-in flow.
- Display name — if you set one in your profile.
- User ID, account and session status — to run the account, sync data, and manage authorization.
- OTP codes and send metadata — code, request time, expiry, use status, and anti-abuse signals.
- Auth token — stored on device in secure storage for the active session.
Guest mode & device
- Client / install ID — guest settings, guest limits, and distinguishing installs. After sign-in, some guest data may be linked to the account.
- Account ID if signed in; device platform and push delivery id; app language, timezone, and UI settings if sent by the app.
Product use
- Selected exchanges, markets, pairs, and timeframes; filter chains and shortlist state; search/session state needed for features.
- Favorites and saved settings; alert rules (pair, timeframe, pattern, related params); in-app notification list.
- Usage counters and plan / feature entitlement status.
Technical, security & diagnostics
- IP address, request time, network/server logs; device type, OS and app version; API metadata and abuse signals.
- Basic crash/error diagnostics on our servers.
- Google Firebase Analytics — app usage metrics such as sessions, devices, approximate region, and automatic analytics events, to understand product performance. This is not precise GPS location and is not used for personalized cross-app advertising tracking.
- Google Firebase Crashlytics — we use Firebase Crashlytics (Google) to diagnose crashes and improve app stability. It may process technical crash data, including an app installation identifier, device information, OS and app versions, error logs, and stack traces. We use this data to identify, analyze, and resolve technical issues.
Push
We use Firebase Cloud Messaging. A push token may be created and registered with PatternLabs when the app starts or a device session initializes — including before you create a specific alert. Display depends on OS permissions. You can disable notifications in system settings; a stored token may remain until refreshed, invalidated, or related data is deleted.
Support
Support is by email and Telegram. Via Telegram we may process Telegram ID, name, username, profile photo, and other data Telegram provides, plus message text, attachments, and conversation history. Do not send passwords, OTP codes, seed phrases, private keys, or full payment details to support.
Payments
The Service is currently provided free of charge. User or technical limits may apply to certain features and may change. Before any paid features or subscriptions are introduced, this Policy will be updated.
Website
The site may process IP, browser/device type, language, date/time, pages requested, referrer, and server logs. It may use cookies or local storage needed for language, UI, security, and correct operation. If we add optional analytics cookies, we will update this Policy and provide a choice where required by law.
What we do not request
The current app does not request precise location, contacts, camera, microphone, photos, or device files. That does not limit what you voluntarily send via a third-party support channel.
Where data comes from
Why we process it
- create and maintain accounts (email OTP and Google Sign-In) and sessions;
- provide guest mode and the market search engine (filters, shortlist, related features);
- save filters, favorites, alerts, and settings;
- send service emails, OTP codes, and push notifications;
- enforce free limits and feature quotas;
- understand product usage and improve the app via Firebase Analytics;
- diagnose and fix crashes and errors via Firebase Crashlytics and our server logs;
- security, abuse prevention, reliability, and support;
- comply with law and protect PatternLabs and users.
Legal bases
Who we share with
- Hosting, database, backup, and network providers — API, site, and storage. Our primary infrastructure is currently located in the European Union. Some service providers may process data in other countries. Infrastructure locations and service providers may change, and this Policy will be updated where necessary.
- Email (SMTP) provider — OTP and service mail.
- Google Firebase — Cloud Messaging (push), Analytics (usage metrics), and Crashlytics (crash reports). Google may process related device/technical data under Google’s terms for Firebase.
- Google Sign-In / Google Identity — when you sign in with Google.
- Telegram — if you contact support via the bot.
- TradingView — when charts load in WebView; TradingView may receive ordinary connection data under its policy.
- Apple / Google — install, store use, purchases, and subscriptions.
- Exchanges (e.g. Binance, Bybit) — public market data APIs. We do not send them your email or name for normal search-engine use.
- Advisors and authorities when required by law or to protect rights; a successor if the project is transferred, with applicable protections.
We do not sell personal data, do not share it with data brokers, and do not use it for personalized cross-app advertising tracking.