Política de privacidad
Reflectly
Última actualización: 10 de noviembre de 2026
This Privacy Policy explains how Reflectly (the Reflectly mobile apps and the Reflectly Online website at reflectly.online, together "Reflectly," "the App") collects, uses, stores, and protects your data.
1. Who We Are
Reflectly is provided by Rustam Atai, a private individual. This is the developer name shown for Reflectly in the App Store and on Google Play. Rustam Atai is the controller of your personal data ("we," "us").
For any privacy question, data request, or account deletion request, email privacy@reflectly.online.
2. Information We Collect
Account Information
- Account details: Email address, display name, and sign-in credentials managed through Firebase Authentication. You can sign in with email and password, Google Sign-In, or Sign in with Apple. If you use Sign in with Apple and choose "Hide My Email," we receive an Apple relay address instead of your real email address.
- Profile data: Optional profile information and app preferences you choose to set.
- Session data: Sign-in sessions, authentication tokens, and device information used to keep your account secure.
Journal Content
- Diary entries: Text you write, with timestamps, tags, and related metadata.
- Mood data: Mood ratings and wellness indicators you choose to record.
- Media attachments: Photos, images, audio recordings, and video recordings you attach to entries. They are uploaded to our media storage.
- AI results: Reflections, summaries, and the journaling profile generated by AI from your entries.
Camera, Microphone, and Photos
The mobile apps and the website ask for access to your camera, microphone, or photo library only when you choose to take a photo, record an audio or video reflection, or attach an existing image. We do not access them in the background. You can revoke these permissions at any time in your device or browser settings.
Technical Information
- Search index: A word-frequency index built from your entry text (and AI summaries when present) so you can search your journal. It is stored on our servers separately from encrypted entry bodies.
- Crash and error reports: Technical reports about crashes and errors in the apps and the website (see Crash Reporting below).
- Usage analytics: On the website, usage and performance analytics only with your consent.
- Device information: Browser or device type, operating system, IP address, and device identifiers, used for security and to keep the service working.
- Local storage: Preferences, settings, and consent choices stored on your device or in your browser.
3. How We Use Your Information
- Providing your private journaling space and syncing it across your devices
- Generating AI reflections and transcripts when you use AI features
- Enabling search, export, and backup of your journal
- Creating and securing your account and sessions
- Processing subscriptions and payments
- Answering support and privacy requests
- Finding and fixing crashes and other technical problems
- Improving the App based on aggregated usage information
We do not sell your personal data or your journal content, and we do not use your journal content for advertising.
4. Data Storage and Security
Infrastructure
Your account and journal data are stored using Google Firebase (Firebase Authentication and Cloud Firestore) and our own servers. Data is encrypted in transit with HTTPS/TLS.
Encryption at Rest
Journal content encryption
Diary entry text, AI analysis results, and media attachments are encrypted with AES-256-GCM before storage. Each account has a random 256-bit master key. That key is stored on our servers in wrapped (enveloped) form using a system-managed key and is delivered to your device when you sign in so the App can encrypt and decrypt during your session.
This is encryption at rest, not end-to-end encryption: our services can access decrypted content when needed (for example, to build search indexes, run AI features you use, or provide support you request).
Limits you should know: (1) Some older data may still be in plaintext if it predates encryption—check your settings in the App. (2) When you use AI features, decrypted text or media is sent to an AI provider for that request (see AI Processing below). (3) The search index is not protected the same way as encrypted entry bodies. (4) Metadata (such as timestamps or mood fields) is not necessarily protected the same way as entry body text. (5) Thumbnails and media delivery may involve additional server-side processing.
Access Controls
- Email verification for email/password accounts
- Per-user data isolation through database security rules
- Session management, including signing out other devices
- Optional recovery key (BIP39 mnemonic phrase) to regain access to your encryption key if you lose your password
5. Third-Party Services
We share data only with the service providers below, only for the purpose described, and only to the extent needed to run the App. We require each of them to protect your data at least as well as described in this policy and in line with applicable data protection law.
- Google (Firebase): sign-in and database — account details and journal data.
- Google Sign-In: sign-in, if you choose it — name, email, and Google account ID.
- Apple (Sign in with Apple): sign-in, if you choose it — name, email or relay address, and Apple ID token.
- Google (Gemini): AI reflections and transcription — entry text, audio, and video you send to AI.
- OpenAI and Anthropic: AI reflections, only if you select them in AI settings — entry text you send to AI.
- Sentry: crash and error reporting — technical reports with your account ID.
- Paddle: payments and subscriptions — billing details.
- Google Analytics, Microsoft Clarity, and Microsoft Advertising: website analytics, only with your consent — usage data.
AI Processing
AI features send your content to a third-party AI provider only when you use them:
- AI reflections: The decrypted text of the entry is sent to Google Gemini by default, or to the provider you select in AI settings.
- Audio and video reflections: The recording is sent to Google Gemini to create a transcript you can edit before saving.
Before the first time the App sends your content to an AI provider, it asks for your permission. You can turn AI features off at any time in Profile → Settings → AI; while they are off, nothing is sent to AI providers. Your journal works without AI. The provider handles the data under its own terms for that request; we do not allow it to use your content for advertising.
Crash Reporting
We use Sentry to collect crash and error reports from the Reflectly mobile apps and the website. A report contains technical details such as the error, the app or browser version, the device or browser type, and your account ID so we can investigate problems you run into. We do not include your journal text, media, passwords, or encryption keys in crash reports. Crash reporting is part of operating the service and is separate from optional analytics.
Analytics (Optional)
On the website, with your consent, we use Google Analytics, Microsoft Clarity, and Microsoft Advertising to understand how the site is used. You can change your choice at any time in the cookie settings or in Profile → Settings → Privacy.
Payment Processing
Payments are processed by Paddle, our Merchant of Record. We do not store your payment card details.
6. Your Privacy Rights
- Access and portability: Export your journal from the App at any time.
- Correction: Update your profile information in the App.
- Deletion: Delete your account in the App (see Account Deletion below).
- Withdraw consent: Turn off AI features or analytics at any time.
- Object or restrict: Email us to object to or restrict processing.
- Complain: You may lodge a complaint with your local data protection authority.
To exercise any right, email privacy@reflectly.online.
7. Data Retention and Deletion
- Active accounts: We keep your data while your account exists.
- Inactive accounts: Data may be deleted after 3 years of inactivity, with prior notice.
- Backups: Deleted data is removed from backups within 90 days.
Account Deletion
You can delete your account in the Reflectly mobile app (Settings → Delete Account) or on the website (Profile → Delete Account). Instructions are also at reflectly.online/account-deletion.
Before we delete anything, you must sign in again with the same method you use for Reflectly (email and password, Google, or Apple). That recent sign-in confirms it is you.
When you confirm, we immediately delete your journal entries, AI results, journaling profile, sessions, MCP access tokens, encrypted media files (photos, audio, and video), scheduled email reminders, and the account record with your encryption key, and then your sign-in record.
If we had sent Google Analytics your account ID (only with your consent), we also submit a request to Google to delete the analytics data linked to that ID. Google processes that request on its own timeline. Previously aggregated reports may still include that activity in anonymous totals. This is a deletion request, not an instant or guaranteed wipe of every historical report.
If you can no longer sign in, email privacy@reflectly.online and we will delete the account for you.
8. International Data Transfers
Your data may be processed in data centers in different countries, including the United States and the European Union. Where required, transfers rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses.
9. Children's Privacy
Reflectly is not intended for users under the age of 13. We do not knowingly collect personal information from children under 13. If we learn that we have, we will delete it promptly.
10. Changes to This Policy
We may update this Privacy Policy from time to time. We will update the "Last Updated" date at the top, and for material changes we will notify you by email or in the App and ask for renewed consent where required.
11. Contact
Rustam Atai (Reflectly)
Email: privacy@reflectly.online