Privacy Policy – DevFellowship
Last updated: 07/10/2026.
DevFellowship (“DevFellowship”, “we”) is committed to protecting user privacy across its mobile and web platforms (the “Platform”).
This Privacy Policy explains how personal data is collected, used, and protected in compliance with applicable data protection laws.
1. Data We Collect
Data provided by users:
- Email address (required)
- Name (web only, optional)
- Profile photo (web only, optional)
- User ID assigned to your account
- Recordings and other content you create in DFL Studio (see section 10)
No additional personal data is required to create an account.
2. How We Use Data
Personal data is used solely for:
- Account creation and authentication
- Platform access
- Educational service delivery
- Operational communications
- Legal compliance
3. Payments
The Platform does not process payments via the mobile app.
DevFellowship does not store financial or card information.
4. Analytics
Our websites and web apps, including devfellowship.com and DFL Studio on the web, load a self-hosted Umami analytics script from analytics.devfellowship.com to measure how they are used. It runs on our own infrastructure and is not an advertising or cross-app tracking service. The DFL Studio iOS app shows the web app inside the app, so the same script may run there. We use it only for our own products and not to track you across other companies’ apps or websites.
The app and the web apps also send diagnostics so we can find and fix problems: error and crash reports, performance traces and, when an error happens, a replay of the session screen, which can show on-screen content. These go to Sentry, a third-party error-monitoring service. Performance traces and metrics also go to DFL’s own OpenTelemetry collector. None of this is used for advertising or cross-app tracking, it is not used to identify you for advertising, and it is not sold.
We may add other analytics tools in the future, with updates to this policy.
5. Data Storage
Data is securely stored using cloud infrastructure, primarily Supabase (database and authentication). Files uploaded from DFL Studio (recordings and rendered videos) are stored in Amazon Web Services S3 object storage.
6. Third-Party Services
Educational content may be embedded from third-party platforms such as YouTube, subject to their own privacy policies.
We use Sentry (error and crash reports, performance traces and session screen replays) for error monitoring, and Groq for speech-to-text transcription, as described in sections 4 and 10.
7. User Rights
Users may request access to or correction of their personal data, and may request deletion of their account and the data linked to it, including the recordings and videos they created in DFL Studio, subject to legal limitations.
To request deletion, contact: [email protected]. We answer deletion requests within 30 days.
8. Children’s Privacy
The Platform is not specifically intended for children, and we do not knowingly collect children’s personal data.
9. Policy Updates
This Privacy Policy may be updated at any time.
10. DFL Studio (recordings)
DFL Studio is our app for recording and producing video lessons. It is available on the web and as an iOS app.
- Camera, microphone and photo library. The app asks for access to the camera and microphone to record your lessons, and to your photo library when you choose an image for a slide. Access is requested by your device and you can withdraw it in its settings.
- Your face and voice. A recording can contain your face and voice. They are content you choose to record. We do not use them for biometric identification, advertising or tracking, and we do not sell them.
- Where recordings go. A recording is first saved on your device. It is then uploaded to DFL storage (Amazon Web Services S3, through a DFL upload service) so that the video can be rendered. It is linked to your account.
- Transcription. To create captions, the audio of a recording is sent to a speech-to-text provider, Groq, and the text is returned to your project.
- Retention. Recordings, projects and exports are kept until you delete them or ask for your account to be deleted. After a deletion request, they are removed from our active systems within 30 days. Backups may persist for a limited period after that.
11. Contact
Privacy contact: [email protected]