Privacy Policy

1. Introduction

Beed ("We", "Our", "App") is committed to protecting the privacy of our users. This Privacy Policy describes the information collected when using the Beed mobile application ("App") and how this information is used.

1.1. Data Controller

Under GDPR and other data protection laws, the data controller is:

• Data Controller: Individual developer of the Beed application
• Contact: info@beed-app.com

You can use the contact information above for all your questions, requests, and objections regarding data protection.

2. Information Collected

2.1. Information Provided by Users

• Account Information: Email address, display name, username, and, if you add them, profile photo, phone number, and "About me" text
• Content: Posts, comments, messages
• Expert Profile Information: Additional information for expert users (education, experience, etc.)

2.2. Automatically Collected Information

• Usage Data: Records of actions you take in the app, for example signing up, applying to be an expert, creating a post (including the development area the post is about), liking a post, adding a comment, and booking an appointment (the expert's ID is stored as a hash). Each record includes the platform (for example, iOS or Android). In app version 1.0.21 and later, each record can also include the app language, the content language, your device's language setting, and the app version, and the app saves the app version and platform you last used in your account record.
• Crash Reports (Firebase Crashlytics): Technical information about app crashes and errors is collected. These reports are used to improve app stability and fix errors. Crashlytics collects the following technical information:
  • Device Model: Model information of the device used (e.g., iPhone 14, Samsung Galaxy S21)
  • Operating System Version: Device's operating system version (e.g., iOS 17.0, Android 13)
  • RAM and Storage Status: Device's memory and storage usage information at the time of crash
  • Call Stack: Code execution sequence and error location at the time of crash
  • App Version: App's version number at the time of crash
  • Connection Type: Internet connection type at the time of crash (Wi-Fi, mobile data, no connection)
  • Error Messages: Technical error messages and exception details
  Important: Crashlytics reports can include your Beed user ID (an internal account identifier) together with the technical information listed above.
• Device Information: Device type, operating system version, platform information

2.3. Device Permissions

The Beed app may request the following device permissions to provide certain features. These permissions are used only for the specified purposes and cannot be accessed without user consent.

• Camera Permission: Camera access is required to take profile photos and create post images. This permission is only requested when the user wants to use the camera. Camera access is only used during the photo-taking process, does not run in the background, or provide continuous access.
• Gallery/Photo Library Permission: Access to your photo library is required to select profile photos from your device and add post images. This permission is only requested when the user wants to select a photo from the gallery. The app does not access all photos on your device; it only accesses the photo selected by the user. The app only accesses the photos you select; it does not access your entire photo library.
• Notification Permission: Notification permission is required to receive notifications about important updates, messages, comments, and other interactions. This permission is used to improve user experience and deliver important information in a timely manner. You can change or completely disable your notification settings from within the app at any time.

2.4. Information Not Collected

• Location Data: Currently not used

2.5. Information Other Users Can See

Beed has community, messaging, and expert features. Other Beed users can see the following information about you:

• Your profile: your display name, your username, and your profile photo. If you add an "About me" text, it is also shown on your profile.
• Your community activity: your posts and comments, the posts you have liked, and your name and profile photo next to them.
• Expert profiles: if your expert application has been approved, your profile also shows an expert badge and the expert information you entered, such as your areas of expertise, qualifications, professional bio, years of experience, and consultation fee. An approved application means that we reviewed it; it does not mean that we verified the expert's license or qualifications (see Section 6 of the Terms of Service).
• Appointments: if you request an appointment with an expert, that expert sees your name and profile photo, the date, time, and length of the appointment, and the note you write when booking.

Parents can use a nickname as their display name. If you sign up with Google or Apple, the name and photo from that account (if available) are used as your Beed name and profile photo. You can change your name and remove your photo from your profile in the app. In app version 1.0.21 and later, when you remove your photo or replace it with a new one, the app also tries to delete the earlier photo file if you uploaded it to Beed, and posts and comments in the app no longer show the removed photo. Posts and comments keep a copy of the photo address from when they were written, so a post or comment may still show your earlier photo if your profile cannot be loaded at that moment or if the person viewing it uses an older version of the app. Removing or replacing your photo in app version 1.0.20 or earlier does not delete the earlier photo file from our storage.

Search: Users who are signed in with an account (not a guest session) can search for approved experts by name or username. Search results show only the display name, username, profile photo, and whether the person is an approved expert. The app also receives each person's internal account ID, which it uses to open their profile or start a conversation; the ID is not shown on screen. Currently, parents do not appear in search results. If you have blocked someone, or someone has blocked you, neither of you appears in the other's search results.

Not shown to other users: In app version 1.0.21 and later, the app does not show other users your email address, your phone number, or when you last signed in.

Privacy settings (app version 1.0.21 and later):

• Profile Visibility: when this setting is off, other users who open your profile page in the app see that it is private, and you do not appear in search results. Your name and profile photo still appear next to your posts, comments, and messages.
• Allow Messages: when this setting is off, other users cannot start a new conversation with you in the app (from the New Message screen, search results, or your profile page). Conversations that already exist can continue. Older versions of the app (1.0.20 and earlier) do not apply this setting to the Message button on your profile page.

3. Artificial Intelligence (AI) Content Disclosure

The Beed app contains some content that was created with artificial intelligence (AI) support. Specifically, "teaching stages" or "instructional stages" content was developed with AI assistance. This content is pre-created and static (not generated in real-time during app use).

3.1. Current AI Content Status

• Pre-Created Content: The app currently contains pre-created, AI-supported content (particularly teaching stages/instructional stages). This content is static and not generated during user interaction.
• No Active Generation: The app does not currently generate new AI content in real-time during user interaction. User-provided information is not sent to AI services for active content generation.
• Intended Users: The Beed app is designed for use by parents, guardians, and professionals (such as special education teachers and experts). The app is not intended for direct use by children.

3.2. AI Content Limitations and Responsibilities

3.3. Medical / Educational Regulation Disclaimer

The Beed app is not a medical device and does not provide medical diagnosis, treatment, or clinical services. Educational content is provided for informational and supportive purposes only.

3.4. Future AI Features

Future versions of the app may introduce active AI content generation features that create content in real-time based on user input. If such features are introduced:

• Users will be informed about the new AI features and their implications.
• This Privacy Policy will be updated to reflect the new functionality.
• Consent will be requested when required, and users will be informed during onboarding or feature activation.
• For information about data transfer related to future AI features, see Section 6.5.

4. Use of Information

Collected information is used for the following purposes:

• Account Management: Creation and management of user accounts
• Service Provision: Operation of app features
• AI-Supported Content Delivery: Providing previously created AI-supported education plans and materials. Currently, the app does not generate new AI content in real-time during user interaction. If future active AI generation features are introduced, they will be described in this policy and users will be informed.
• Communication: Communication with users (notifications, updates)
• Analytics: Analyzing app performance and user experience
• Error Fixing: Detecting and fixing app errors
• Security: Preventing and detecting security breaches

5. Data Security

5.1. Data Storage Location

The Beed application stores data with Google Firebase, on Google Cloud Platform's infrastructure.

• Data Region: App data in Cloud Firestore (such as your profile, development records, posts, and messages) is stored in the United States (multi-region location nam5). Files you upload to Firebase Storage (such as photos and videos) are stored in the European Union.
• Encryption: All data is encrypted both during transmission (TLS/HTTPS) and during storage (at-rest encryption). Firebase uses Google Cloud's industry-standard encryption technologies.
• Infrastructure: Data is hosted on Google Cloud Platform's secure and highly available infrastructure. Google Cloud has international security certifications such as ISO 27001, SOC 2, SOC 3.

5.2. Security Measures

• Encryption: Sensitive data is transmitted over encrypted connections (HTTPS/TLS)
• Hashing: User IDs are hashed in analytics data

6. Data Sharing and Third-Party Services

The Beed app uses the following third-party service providers to provide our services and improve the app experience. These services process your data according to their own privacy policies.

6.1. Firebase Services (Google)

Our app uses Google's Firebase platform:

• Firebase Authentication: Used for user authentication and account management. Email, Google, and Apple account information is processed by Firebase Authentication. Firebase Authentication creates the links in email address verification and password reset emails. When these emails are not sent through our own email service (see Section 6.4), Firebase Authentication sends them.
• Cloud Firestore: Used for storing app data (user profiles, education plans, performance records, posts, messages). Data is transmitted over encrypted connections.
• Firebase Storage: Used for storing files uploaded by users (profile photos, media content).
• Firebase Crashlytics: Collects app errors and crash reports: technical information (device type, operating system, error messages) and your Beed user ID.
• Firebase App Check: Used to ensure app security and prevent abuse.

6.2. Google Sign-In

Google Sign-In SDK is used for signing in with a Google account. Google processes this data according to its own privacy policy. When you sign in with your Google account, Google's privacy policy applies.

6.3. Apple Sign-In

Apple Sign-In SDK is used for signing in with an Apple account. Apple processes this data according to its own privacy policy. When you sign in with your Apple account, Apple's privacy policy applies.

6.4. Other Service Providers

• Railway: Hosts our backend servers (api.beed-app.com and, from app version 1.0.21, profil-api.beed-app.com). Requests the app sends to api.beed-app.com for subscription verification and the Zoom integration can include your user ID. The username availability check sends the username you choose. When you ask for a password reset email, the app sends your email address and the email's language; when you ask for an email address verification email, it sends a sign-in token and the language. When you search for people, the app sends the search text, a sign-in token, and, when available, an app integrity token (Firebase App Check) to profil-api.beed-app.com. To prepare the results, this server reads the account information it needs from our database and returns only the information described in Section 2.5. It does not store the search text or copies of profiles.
• Google Workspace (Gmail): We may send email address verification and password reset emails from a beed-app.com address through Google Workspace. To send them, our server (see Railway above) passes your email address, the email's language, and a one-time link to Google. Google processes this data as our service provider. Google Workspace may keep a copy of each sent email in our sending mailbox.
• Apple App Store and Google Play: Subscriptions are purchased through your App Store or Google Play account. Apple or Google processes the payment; we receive information about your purchase and subscription status.
• Zoom: Used for online appointments with experts. See Section 7.

6.5. AI Services Data Transfer

Current Status: Currently, the app does not actively generate new AI content during user interaction. Therefore, user-provided content is not routinely sent to AI services for real-time generation.

Future AI Features: Future versions of the app may introduce active AI content generation features that require sending some user-provided information to AI services (e.g., OpenAI API). If such features are introduced:

Data Transfer Details (for future features):

• Transferred Data: If active AI generation is enabled, information provided by users (e.g., student development information, education goals, education plan requests) may be sent to AI services.
• Anonymization: Personal identifying information (name, ID number, email address, etc.) would be removed before being sent to AI services whenever possible. However, education information necessary for content generation may be sent.
• Third-Party AI Services: OpenAI API may be used if active AI generation features are enabled. Other AI services may be used in the future. This Privacy Policy will be updated when such features are introduced.
• Data Retention: AI service providers have their own privacy policies. For information about OpenAI's data retention policies, please review the OpenAI Privacy Policy.
• Data Usage: If active AI generation is enabled, data sent to AI services would be used only for real-time content generation. It would not be used for retroactive model training (according to OpenAI's current policy).

User Notification: Users will be informed when active AI generation features are introduced, and this Privacy Policy will be updated accordingly.

6.6. Data Sharing Policy

• Personal Data: Your personal data is not shared with third parties except for the services mentioned above. The information described in Section 2.5, and the content you post in the community, is visible to other Beed users.
• Advertising Data Sharing: Collected user data is not used for advertising purposes in any way and is not shared with advertising providers. The Beed app does not contain ads and user data is not processed or sold for advertising purposes.
• Analytics Data: Analytics and usage data are stored in Cloud Firestore with a hashed user ID.
• Data Security: All third-party services use industry-standard security measures and make efforts to protect your data.

Important: Third-party services have their own privacy policies. For more information about these services' data processing practices, you can review the relevant service providers' privacy policies:

• Firebase Privacy Policy
• Google Privacy Policy
• Apple Privacy Policy

7. Zoom Integration

The Beed app integrates with Zoom to provide online meeting and consultation features for expert users. This section explains how we use and protect your data when you connect your Zoom account to Beed. It supplements this Privacy Policy and should be read together with Zoom’s own policies.

7.1. Data accessed via Zoom

When you authorize Beed through the Zoom App Marketplace (OAuth authorization), we receive an authorization token that allows us to access limited information from your Zoom account. We request only the following OAuth scopes from Zoom:

• meeting:write:meeting – to create and manage Zoom meetings on your behalf
• meeting:read:meeting – to read basic information about meetings created via Beed
• user:read:user – to read basic account information (such as your Zoom user ID and email)

Through this integration, we may access and store the following information:

• Your Zoom user ID and Zoom account ID
• Your Zoom email address, first name, and last name
• Meeting metadata created via Beed (meeting ID, topic, scheduled date/time, join URL, host URL, and basic settings). The meeting topic is the note the parent writes when booking the appointment, if any; otherwise it is a default title. It is saved as the meeting title in the expert's Zoom account.

7.2. How Zoom data is used

We use the data obtained via Zoom only for the following purposes:

• To create, update, and manage Zoom meetings associated with your Beed appointments
• To generate and display Zoom join links and meeting details inside the Beed app
• To link your Beed expert profile with your Zoom account and show connection status
• To ensure security of the integration and prevent abuse or unauthorized use

7.3. Legal basis and relationship with Zoom

We process your Zoom-related data primarily on the basis of:

• Contract performance: To provide the online consultation and scheduling features you request.
• Legitimate interest: To maintain a secure and reliable integration with Zoom.
• Consent: You explicitly grant permission when you authorize Beed in the Zoom App Marketplace. You may revoke this authorization at any time by uninstalling the app from Zoom or disconnecting it within Beed.

Zoom Video Communications, Inc. is an independent third party. Your use of Zoom is also governed by Zoom’s own Privacy Policy and Terms of Service.

7.4. Tokens and retention

As part of the OAuth process, we receive access tokens and refresh tokens from Zoom. These tokens are kept only in our server's memory and used only to perform API calls required for the integration (such as creating or updating meetings).

• Tokens are kept for up to 5 minutes at a time and are not saved to a database.
• When you disconnect Zoom in Beed, the tokens are removed from our server's memory. If you remove the Beed App in the Zoom App Marketplace, any token still in memory expires within 5 minutes.

Zoom meeting details (such as meeting ID and join link) are stored with your appointment records in Beed and are deleted when you delete your Beed account.

7.5. Data subject rights for Zoom-related data

Your general data protection rights described in this Privacy Policy (such as the right of access, rectification, erasure, restriction, objection, and data portability) also apply to personal data processed via the Zoom integration. You can exercise these rights by contacting us at support@beed-app.com.

You may also need to contact Zoom directly for requests related to data that Zoom processes as an independent controller.

7.6. No payments through Zoom

Beed does not process payments through Zoom. Any payments related to Beed (if applicable) are handled outside of Zoom. Zoom is not used as a payment processor for Beed, and no billing information is obtained from Zoom.

8. Data Retention

• Active Accounts: Data is retained as long as the account is active
• Deleted Accounts: When you delete your account in the app, deletion takes place immediately. Some data is not deleted; see Section 8.1
• Analytics Data: Analytics data, in which user IDs are stored as a hash, is not deleted when you delete your account

8.1. Account Deletion Process

The Beed app allows users to easily delete their accounts from within the app. The account deletion process is performed as follows:

How to Delete an Account?

1. Tap the profile icon at the top right of the home screen
2. On your profile page, tap the Settings (gear) icon
3. Under Account Settings, select Security
4. Select Delete Account and confirm in the two dialogs that follow
5. If asked, sign in again (with Google, Apple, or your password)

If you cannot use the app, you can ask us by email to delete your account (see the Account Deletion page). We process these requests within 30 days of receipt. We delete the same data that is deleted when you delete your account in app version 1.0.21 or later, and the same exceptions in "Data Not Deleted" below apply.

What Happens When an Account is Deleted?

When you delete your account, the following processes occur:

• Account Information: Your account profile (such as your name, email address, and phone number) is deleted. In app versions up to 1.0.20, your profile photo file is not deleted (see "Data Not Deleted" below).
• Content: Your posts and comments are permanently deleted. In app version 1.0.21 and later, your conversations and the messages in them are also deleted, including the messages the other person sent you, and the other person will no longer see the conversation (for photos, videos, and files the other person sent you, see "Data Not Deleted" below). We also try to delete the files that are linked from your account and content at the time of deletion: your current profile photo (if you uploaded it to Beed), the photos and videos in your posts, and the files in messages you sent. Some files are not deleted (see "Data Not Deleted" below). In app versions up to 1.0.20, your messages and uploaded files are not deleted (see "Data Not Deleted" below).
• Education Data: Your education plans, performance records, and development tracking data are deleted
• Expert Profile: If you are an expert user, your expert profile and appointment history are deleted
• App Access: You cannot sign in with your account and cannot access all your data within the app

Waiting Period and Recovery

• No Waiting Period: When you delete your account in the app, deletion takes place immediately. There is no waiting period, and a deleted account cannot be restored.

Data Not Deleted

The following data is not affected by the account deletion process or is subject to different retention periods:

• Messages and Uploaded Files: In app versions up to 1.0.20, your messages, your conversations, and the photos, videos, and files you uploaded (profile photo, post media, message attachments) are not deleted when you delete your account in the app. In app version 1.0.21 and later, and for deletion requests sent by email, the following are not deleted: files that are no longer linked from your account or content at the time of deletion (for example, earlier profile photos that were not deleted when you replaced or removed them in app version 1.0.20 or earlier, and photos, videos, or files from posts or conversations you deleted earlier); files that could not be deleted at the time of deletion; and photos, videos, and files other people sent you in messages, together with the copy of those messages that the app keeps for the sender.
• When Someone You Messaged Deletes Their Account: If a person you have a conversation with deletes their account using app version 1.0.21 or later, or asks us by email to delete it, that conversation, including the messages you sent, is deleted, and you will no longer see it in the app. If you sent photos, videos, or files in that conversation, the copy of those messages that the app keeps for you (including any text you wrote with them) and the files themselves are not deleted.
• Analytics Data: Analytics events, in which your user ID is stored as a hash, are kept.
• Crash Reports: Crash reports can include your user ID.
• Subscription Records: Records that link your App Store or Google Play subscription to your account are kept.
• Reports and Blocks: Content reports you submitted and your list of blocked users are kept.
• Likes: Your likes on other people's posts and comments (stored with your user ID), and the list of posts you shared, liked, or commented on, are kept.
• Copies of Your Name: Copies of your name in notifications other users received (for example, about your likes, comments, or appointment requests) and, if you are an expert, on posts and comments you approved are kept.
• Server Logs: Technical logs on our servers, which can include your user ID, are kept.
• Legal Obligations: Data that must be retained due to legal requirements (e.g., financial records) continues to be stored.
• Zoom Meetings: Zoom meetings already created in an expert's Zoom account, including the meeting title, are not deleted by Beed.

8. User Rights

In accordance with GDPR and other data protection laws, users have the following rights:

• Right of Access: You can request access to your personal data
• Right to Rectification: You can request correction of incorrect data
• Right to Erasure: You can request deletion of your data
• Right to Object: You can object to data processing
• Data Portability: You can transfer your data to another service

9. Children's Privacy

The Beed app does not knowingly collect personal data from children under 13 years of age. If we discover that we have collected information from a child under 13, we will delete this information. Some data may not be deleted; see "Data Not Deleted" in Section 8.1. The Zoom integration is intended for use by adult professionals and is not designed for direct use by children.

If a parent or guardian believes their child's personal information has been collected without authorization, they can contact us at info@beed-app.com. In this case, we will delete the child's personal data. Some data may not be deleted; see "Data Not Deleted" in Section 8.1.

10. Cookies and Similar Technologies

Our app does not use cookies. However, Firebase services and third-party services may use cookies for technical purposes. These cookies are necessary for app functionality.

Firebase SDKs may use device identifiers instead of cookies. These identifiers are not cookies. They are used for technical purposes such as app functionality and analytics.

11. Privacy Policy Changes

This Privacy Policy may be updated from time to time. Users will be notified of significant changes.

12. Disclaimer and Legal Warnings

12.1. AI & Education Content Disclaimer

Content provided in the Beed app, especially AI-supported education plans and educational content, is for guidance and support purposes only. For detailed information about AI content, please refer to Section 3.

12.2. General Disclaimer

• The app is provided "as-is".
• No guarantee is made that the app will operate uninterrupted, error-free, or securely.
• No liability is accepted for data loss, material damage, or other losses arising from app use.

13. Explicit Consent / Consent Mechanism

13.1. Consent for AI Content Usage

By using the app, you acknowledge the AI-related disclosures in Section 3 and the legal warnings in Section 12.

13.2. Future AI Features and Consent

If active AI content generation features are introduced in future versions of the app, users will be informed during onboarding or feature activation, and consent will be requested when required. For information about data transfer related to future AI features, see Section 6.5.

13.3. Consent Withdrawal

Currently, the app does not send user data to AI services for active content generation. If future AI features that require data transfer are introduced and you wish to withdraw your consent, you may choose not to use those specific AI features. However, it may not be possible to retrieve data already sent to AI services (depending on AI service provider policies).

14. Contact

15. Legal Basis (GDPR)

Our data processing activities are based on the following legal bases:

• Contract: Data necessary to provide services (account creation, saving education plans, messaging, etc.) is processed under contract. App services cannot be provided without this data.
• Legal Obligation: Data processed due to legal requirements (e.g., financial records, tax obligations).
• Legitimate Interest: Data processing for app security, error detection, and improvement (Crashlytics, security logs, etc.).
• Explicit Consent: Situations requiring user consent (e.g., uploading profile photo, notification preferences, AI content usage). Consent can always be withdrawn.

15.1. Analytics Data and Right to Object

The Beed app collects analytics data in which user IDs are hashed. We offer the following options:

• Right to Object: You can object to legitimate interest-based data processing (e.g., security logs, error reports). You can send your objection to info@beed-app.com. Your objection will be evaluated and processed within the framework of legal requirements.
• Consent Withdrawal: You can withdraw your consent at any time for data processed with explicit consent. When consent is withdrawn, the relevant data processing is stopped (except for legal obligations).