Crucially (“we,” “us,” or “our”) operates the Crucially mobile applications and the website at crucially.app (together, the “Services”). This Privacy Policy explains how we collect, use, disclose, and safeguard information when you use our Services.
1. Who we are
Crucially is operated by a small developer team. For privacy-related questions, contact us at support@mail.crucially.app.
2. Information we collect
2.1 Account and authentication
Crucially uses Firebase Authentication. Depending on sign-in method:
- Google Sign-In (Android): We receive identifiers and profile data from Google and Firebase (for example, email address, display name, and profile photo URL as provided by your Google account).
- Sign in with Apple (iOS): We receive identifiers and profile data from Apple and Firebase (for example, email when Apple shares it, or the private relay email Apple provides; name on first sign-in when applicable).
We do not offer password-based sign-in inside the app.
2.2 Content you create
We process posts, comments, media attachments (photos, videos, and related metadata), and profile information you choose to provide (such as display name and avatar). Media may be captured with your device camera or microphone, or selected from your photo library, as described in the app’s permission prompts.
2.3 Device and technical data
To operate sync and security, we may collect and use:
- A device identifier generated on first install and stored on your device.
- Platform (iOS or Android).
- Firebase Cloud Messaging (FCM) token for push notifications, registered with our servers.
- Network and sync metadata needed to deliver updates between your connections (for example, event hashes, delivery acknowledgments).
2.4 Connections and social graph
Crucially is designed for a small circle of connections (up to 10 connections per account). We store connection relationships, display names, avatar URLs, and related timestamps so you can see who you are connected to and receive their posts.
2.5 Crash and error diagnostics
When configured in a build, we may use Sentry (or similar tooling) to collect crash reports and error logs. These may include stack traces, device/OS information, and contextual messages that help us fix bugs. We do not use this data for advertising.
2.6 This website (crucially.app)
If you submit your email on our landing page waitlist, we store that email in Firebase Firestore along with a creation timestamp. We may use Firebase Analytics (Google Analytics) on the website only to understand basic traffic and usage of the site. The mobile app does not include Firebase Analytics in the same way as the landing page.
3. How we use information
We use the information above to:
- Provide, maintain, and improve the Services (including account management, feeds, comments, and media sync).
- Send push notifications related to sync, recovery, and activity between your connections (you can disable notifications at the OS level).
- Support peer-assisted recovery (see below) so your content can be restored when needed.
- Diagnose crashes and errors.
- Communicate with waitlist subscribers about the beta or launch (if you joined the waitlist).
- Comply with law and enforce our Terms of Service.
4. Peer-assisted recovery
Crucially’s design includes a friend backup model: in order to help you recover your timeline if you lose a device, encrypted or encoded sync data may be requested from your connected peers through our servers and, in some cases, their devices. By using the Services and connecting with others, you acknowledge that recovery-related data may transit through our infrastructure and peers you have connected with, solely to operate the service.
5. Where data is processed
We use service providers including Google (Firebase, FCM, Google Sign-In), Apple (Sign in with Apple), cloud hosting for our backend and object storage, and optionally Sentry. Data may be processed in the United States and other countries where those providers operate. By using the Services, you consent to such processing.
6. Sharing of information
We do not sell your personal information. We do not run third-party ad networks in the app for behavioral advertising. We share information only:
- With service providers who assist in operating the Services (hosting, Firebase, push, analytics on the site, crash reporting), subject to their terms and policies.
- With your connections as needed to deliver posts, comments, and recovery-related data as described in the product.
- When required by law, legal process, or to protect rights and safety.
7. Retention
We retain account and content data as long as your account is active and as needed to provide the Services. Sync and queue metadata may be transient. Waitlist emails may be retained until we no longer need them for the beta or launch, or until you ask us to remove them. Crash logs may be retained for a limited period for debugging.
8. Your choices and rights
Depending on where you live, you may have rights to access, correct, delete, or export personal data, or to object to certain processing. To exercise these rights or ask questions, contact support@mail.crucially.app.
You can stop using the app at any time. You may delete your Firebase account through the mechanisms we provide in the app when available, or request account deletion by contacting support. Some data may remain in backups for a limited period.
9. Children
The Services are not directed at children under 13 (or the age required by your jurisdiction). We do not knowingly collect personal information from children. If you believe we have, contact us and we will take steps to delete it.
10. Security
We use reasonable technical and organizational measures to protect information. No method of transmission over the Internet is 100% secure.
11. Changes to this policy
We may update this Privacy Policy from time to time. We will post the updated policy on this page and update the “Last updated” date. Continued use of the Services after changes means you accept the revised policy.
12. Contact
Crucially — Privacy inquiries:
support@mail.crucially.app