FiliLearn Legal
App Privacy And Permissions
What the FiliLearn mobile app collects and why each device permission is requested.
- Effective Date
- September 16, 2026
- Last Updated
- September 16, 2026
- Version
- Version 1
This page explains common permissions the FiliLearn mobile application may request and why they may be needed.
FiliLearn should request only permissions necessary for active features.
1. Microphone
FiliLearn may request microphone permission for:
- Pronunciation practice
- Voice recording
- Live Classes
- Live classroom audio
- Other learning activities requiring speech
Suggested iOS permission explanation:
FiliLearn uses your microphone for pronunciation practice and live Live Classes.
Do not request microphone access until a feature requiring it is used or permission is otherwise contextually appropriate.
2. Camera
FiliLearn may request camera permission for:
- Live Live Classes
- Profile photograph capture
- Teacher verification where appropriate
- Other camera based learning functionality
Suggested iOS explanation:
FiliLearn uses your camera for live Live Classes and profile features when you choose to use them.
3. Photos
FiliLearn may request photo library access when a User chooses to upload:
- Profile photograph
- Teacher verification materials
- Approved attachments
- Other selected media
Prefer modern system photo selectors where possible so FiliLearn does not require broad photo library access unnecessarily.
Suggested explanation:
FiliLearn accesses photos you choose to upload for your profile or supported account features.
4. Notifications
FiliLearn may request notification permission for:
- Class reminders
- Teacher messages
- Reschedule requests
- Booking confirmations
- Learning reminders
- Announcements
- Account alerts
Suggested permission context:
Turn on notifications so you do not miss class reminders, teacher messages, and important FiliLearn updates.
Do not make promotional notifications indistinguishable from necessary class alerts.
5. Haptic Feedback
FiliLearn may use device haptics for:
- Answer feedback
- Lesson completion
- Learning milestones
- Class confirmations
- Navigation feedback
Users should be able to disable haptic feedback inside Learning Experience settings.
6. Location
FiliLearn should NOT request precise location unless a future feature has a legitimate and disclosed need for it.
Timezone functionality should not automatically require precise GPS location.
If location is introduced later, update this document and applicable store disclosures before enabling it.
7. Contacts
FiliLearn should not request access to a User’s address book unless a future feature genuinely requires it.
Do not request Contacts permission for marketing growth.
8. Bluetooth
FiliLearn should not request Bluetooth permission unless required for a clearly identified feature.
9. Tracking
FiliLearn should not use cross app tracking merely for general analytics.
If FiliLearn later performs activity that meets Apple’s definition of tracking, appropriate App Tracking Transparency permission must be implemented before tracking occurs.
10. Account Information
The app may transmit account information to FiliLearn servers so that Users can:
- Sign in
- Maintain progress
- Book classes
- Access subscriptions
- Communicate with Teachers
- Synchronize learning history
11. Learning Activity
Learning data may include:
- Lesson completion
- Practice results
- Vocabulary progress
- XP
- Stories completed
- Live Class information
This information may be linked to the Learner account because account based progress synchronization requires identification.
12. Audio
Pronunciation audio may be transmitted for processing where required to provide pronunciation feedback.
The Privacy Policy should describe whether audio is retained or processed temporarily.
13. Classroom Video And Audio
Live Classes may transmit live video and audio to FiliLearn’s authorized video infrastructure.
Recorded sessions are subject to the Classroom Recording Consent.
14. Payments
Payment information may be processed by an authorized payment processor or app marketplace.
FiliLearn should not unnecessarily store complete card information.
15. Third Party SDKs
FiliLearn is responsible for understanding the privacy behavior of SDKs integrated into the application.
Before every App Store or Google Play submission, review all SDKs for:
- Collected data
- Data use
- Tracking behavior
- Required permissions
- Privacy manifests
- Privacy disclosures
16. Apple App Privacy Disclosure
Before submitting FiliLearn to Apple, review every category of data collected by FiliLearn and integrated third parties.
Potential categories requiring review may include:
- Contact information
- User content
- Audio data
- Photos
- Identifiers
- Purchases
- Usage data
- Diagnostics
- Other information associated with accounts
Do not automatically select these categories without confirming actual implementation.
The App Store privacy responses must reflect what the shipping app actually collects.
17. Data Linked To Identity
Where data is associated with a FiliLearn account, it may need to be disclosed as linked to the User for App Store purposes.
Do not incorrectly classify account connected information as anonymous.
18. Tracking Declaration
Do not declare FiliLearn as tracking Users unless the actual implementation meets the platform definition.
Likewise, do not declare “no tracking” if an integrated SDK is performing tracking.
Audit all SDKs first.
19. Privacy Manifest
Maintain the appropriate iOS privacy manifest.
Review:
- Data types
- Required reason APIs
- Integrated SDK privacy manifests
- Tracking domains if applicable
Generate and inspect the Xcode privacy report before App Store submission.
20. Google Play Data Safety
When an Android application is released, complete the Google Play Data Safety information based on actual:
- Collection
- Sharing
- Security practices
- Data purposes
- Deletion mechanisms
- Third party SDK behavior
Keep Google Play disclosures consistent with FiliLearn’s Privacy Policy.
21. Permission Denial
The app should continue functioning wherever technically possible when optional permission is denied.
Example:
If camera permission is denied, ordinary self paced lessons should still work.
If microphone permission is denied, reading lessons should remain accessible even though pronunciation recording may not function.
22. Permission Education
Before triggering an operating system permission dialog, show contextual UI explaining why FiliLearn needs that permission.
Do not display multiple permission requests immediately when the app first launches.
Request permissions when the User reaches the relevant feature.
23. Children
Permission requests involving younger Learners must follow the account’s parental authorization requirements where applicable.
24. Account Deletion
Where required by an app marketplace or law, provide an accessible method for Users to begin account deletion.
Account deletion should also follow the Privacy Policy and applicable retention requirements.
25. Changes
This page should be updated whenever FiliLearn introduces a new category of device permission or materially changes how app data is used.
26. Contact
Privacy and permission questions:
- legal@heybuddysolutions.com
-
Legal Contact
HeyBuddy Enterprises LLC
9245 Laguna Springs Dr., Suite 200
Elk Grove, California
United States
