CastelMeet Icon

Privacy Policy — CastelMeet

Your conversations, meetings and data stay private. This policy explains exactly what CastelMeet collects, why, and how it is protected.

App: CastelMeet Category: Video Conferencing Developer: Castel Code Ltd Platform: Android 8.0+ Effective: July 13, 2025
📅 Last Updated: July 13, 2025  ·  Effective Date: July 13, 2025  ·  Version: 1.0

Table of Contents

1

Who We Are

CastelMeet is developed and operated by Castel Code Ltd, a software company based in Lusaka, Zambia, specialising in mobile applications, AI/ML solutions, web development, and communication technology.

Legal Entity & Contact Details

  • Company: Castel Code Ltd
  • Trading Name: Castel Code — Centre of App and Software
  • Location: Lusaka, Zambia
  • Website: castelcode.tech
  • Email: castelcode.tech@gmail.com
  • WhatsApp: +260 706 951 176
  • Google Play Account: Castel Code

By installing or using CastelMeet you agree to the terms described in this Privacy Policy. If you do not agree, please uninstall the application.

2

Information We Collect

CastelMeet collects only the data strictly necessary to provide secure, reliable video conferencing. The table below lists every category of data we process.

Data TypeDetailsRequiredPurpose
Display NameName you enter when joining a meetingRequiredIdentifying you to other participants
Audio StreamMicrophone audio captured during active callsRequired for callsVoice communication in meetings
Video StreamCamera video captured during active callsOptionalVideo communication in meetings
Screen Share StreamScreen content shared by you during a meetingOptionalPresentation and collaboration
Meeting Room IDUnique identifier for the meeting room you create or joinRequiredRouting participants to correct meeting
Anonymous User IDFirebase-generated anonymous UID on first launchRequiredSession management and signalling
Connection MetadataIP address region, connection quality, timestampAutomaticDiagnosing call quality issues
Device InformationAndroid version, device model — via Firebase onlyAutomaticCrash reporting, compatibility
FCM TokenFirebase Cloud Messaging tokenOptionalMeeting invite notifications

🔒 We do NOT collect: your contacts, call logs, SMS, personal files, photos outside of meetings, payment information, or any data from your device outside of active meeting sessions. We do not read your messages sent to other apps.

3

How We Use Your Information

Core Meeting Functions

  • Establishing and maintaining real-time audio and video connections between participants
  • Routing media streams between meeting participants securely
  • Displaying participant names and connection status in the meeting room
  • Managing meeting room creation, joining, and termination
  • Enabling raise-hand, mute, and participant management features

Service Quality & Reliability

  • Diagnosing and resolving connection quality issues
  • Monitoring and improving call performance
  • Crash reporting and error logging via Firebase
  • Aggregate, anonymised usage analytics for feature development

Notifications

  • Meeting invite alerts sent via Firebase Cloud Messaging
  • Meeting start reminders if scheduled in advance

We do not use your data for advertising profiling, sell data to third parties, build behavioral profiles, or share data with any government authority unless required by Zambian law.

4

Audio & Video Data

Audio and video are the core of CastelMeet. Here is exactly how your media is handled:

🔒 Media is transmitted in real-time only. Audio and video streams are transmitted directly between participants to enable live communication. Streams are not stored, recorded, or retained by Castel Code unless you explicitly enable the Recording feature (see Section 8).

Audio

  • Microphone is accessed only when you are in an active meeting and not muted
  • Audio stream is transmitted to other participants in real time
  • Audio is not processed for speech recognition, transcription, or AI analysis
  • Microphone access stops immediately when you leave a meeting or mute yourself

Video

  • Camera is accessed only when you enable your video in a meeting
  • Video stream is transmitted to other participants in real time
  • Video is not analysed, stored, or processed by Castel Code servers beyond routing
  • Camera access stops immediately when you turn off your video or leave the meeting

⚠️ Important: While Castel Code does not record or store your audio or video, other meeting participants may use third-party screen recording tools on their own devices. Castel Code has no control over recordings made by other participants on their own devices.

5

Meeting Rooms & Participants

CastelMeet uses a room-based meeting system. When you create or join a meeting room:

What Is Stored in a Meeting Room

  • Room ID: A unique identifier for the meeting session
  • Participant list: Display names of current participants (visible to all in the room)
  • Room status: Active or ended, creation timestamp
  • Raise-hand status: Whether a participant has their hand raised

What Happens When a Meeting Ends

  • The meeting room record is marked as ended in our database
  • Participant list data is cleared from active memory
  • No audio or video is retained after the meeting ends
  • Room metadata (room ID, timestamps) may be retained for up to 30 days for debugging purposes, then deleted

Your display name is visible to all participants inside the meeting room. We recommend not using sensitive personal information as your display name.

6

Real-Time Communications Technology

CastelMeet uses industry-standard real-time communication technology to establish secure peer connections between participants. Our implementation is built on proven open standards used globally for video conferencing.

How Connections Work

  • A secure signalling channel is used to coordinate connection setup between participants
  • Once connected, media streams flow directly between participants over encrypted channels
  • All connections use end-to-end encryption for audio and video streams
  • Our signalling infrastructure is hosted on Google Cloud via Firebase

Connection Data Collected

  • Approximate IP region (country/city level) — used for connection routing optimisation
  • Connection quality metrics (packet loss, latency) — used for debugging only
  • Session duration — used for service monitoring

We do not disclose the specific technical architecture or implementation details of our real-time communication system as this constitutes proprietary intellectual property of Castel Code Ltd.

7

Screen Sharing

CastelMeet allows participants to share their screen during meetings. When you use screen sharing:

Screen Share Data Handling

  • Screen content is captured only while you have screen sharing actively enabled
  • The captured content is transmitted in real-time to other meeting participants only
  • Castel Code does not store, analyse, or process screen share content
  • Screen sharing stops immediately when you end the share or leave the meeting
  • Android will display a system notification while screen sharing is active

⚠️ Your responsibility: You are responsible for what content you share on your screen. Do not share sensitive personal information, passwords, banking details, or confidential documents unless you fully trust all meeting participants.

8

Meeting Recordings

Current Recording Policy

CastelMeet does not currently offer server-side meeting recording. Castel Code does not record, store, or retain any audio or video from meetings on our servers.

Future Recording Features

If recording functionality is added in future versions of CastelMeet, we will:

  • Clearly notify all meeting participants that recording is in progress via an in-meeting indicator
  • Update this Privacy Policy before releasing the feature
  • Require explicit consent from the meeting host before any recording begins
  • Provide clear controls for participants to leave if they do not consent

Any recording done by individual participants using their own device's screen recording functionality is outside the control of Castel Code and is governed by that participant's own actions and responsibilities.

9

Camera & Microphone Permissions

CastelMeet requests the following Android runtime permissions:

PermissionWhen RequestedHow UsedCan Be Revoked
CAMERAFirst time you enable video in a meetingCapturing video stream for meeting participantsYes — via Android Settings
RECORD_AUDIOFirst time you join a meetingCapturing microphone audio for meeting participantsYes — via Android Settings
INTERNETApp installEstablishing meeting connections and signallingNo — required for app function
POST_NOTIFICATIONSFirst launch (Android 13+)Meeting invite and reminder notificationsYes — via Android Settings
FOREGROUND_SERVICEApp installKeeping meeting connection alive when screen is offNo — required for calls

Revoking camera or microphone permission means you will not be able to send audio or video in meetings, but you can still join and receive other participants' streams. You can revoke any permission at any time via Android Settings → Apps → CastelMeet → Permissions.

10

Third-Party Services

CastelMeet integrates the following third-party services. Each service's own privacy policy governs the data they process on their platforms.

ServiceProviderPurposeData Shared
Firebase Realtime Database / FirestoreGoogle LLCMeeting room management and signalling coordinationRoom IDs, participant names, connection metadata
Firebase AuthenticationGoogle LLCAnonymous user identity for session managementAnonymous UID only
Firebase AnalyticsGoogle LLCAggregate app usage analyticsAnonymised usage events
Firebase Cloud MessagingGoogle LLCMeeting invite push notificationsFCM device token
Google Cloud InfrastructureGoogle LLCHosting backend signalling servicesConnection metadata, region data

Google Privacy Policy: policies.google.com/privacy
Firebase Privacy: firebase.google.com/support/privacy

Proprietary Technology Disclosure

CastelMeet's core real-time communication engine, signalling architecture, and media routing implementation are proprietary technologies developed by Castel Code Ltd. The specific implementation details, algorithms, and system design are protected as intellectual property and trade secrets of Castel Code Ltd and are not disclosed in this policy.

11

Data Retention & Deletion

Retention Periods

  • Audio & Video streams: Never stored — deleted from memory immediately after transmission
  • Meeting room records: Retained for up to 30 days after meeting ends, then permanently deleted
  • Anonymous user account: Retained while app is installed or until deletion is requested
  • Connection metadata: Retained for up to 14 days for debugging, then deleted
  • Analytics data: Aggregated and anonymised — retained for 14 months per Google Analytics defaults
  • Screen share content: Never stored — transmitted in real-time only
  • Push notification tokens: Retained until app is uninstalled or token refreshed

How to Delete Your Data

To request deletion of all your data, email us at castelcode.tech@gmail.com with the subject line "CastelMeet Data Deletion Request". We will delete your anonymous account record and all associated meeting metadata within 30 days.

Uninstalling CastelMeet removes all locally stored data from your device immediately. Server-side data requires a deletion request as above.

12

Data Security

Castel Code implements multiple layers of technical and organisational security to protect your data and communications:

Technical Security Measures

  • Encrypted Media Streams: All audio and video is transmitted over encrypted real-time communication channels — conversations cannot be intercepted in transit
  • Encrypted Signalling: All connection coordination data is transmitted over TLS-encrypted HTTPS channels
  • Firebase Security Rules: Database access is restricted by authenticated session rules — participants can only access rooms they have joined
  • R8 Code Obfuscation: Release builds are obfuscated to protect our proprietary implementation from reverse engineering
  • Anonymous Authentication: No personally identifiable credentials are stored or transmitted — identity is managed via anonymous session tokens
  • No Persistent Media Storage: Audio and video are never written to disk or retained on any server

While we implement industry-standard security practices, no system is completely risk-free. We recommend keeping your Android OS and CastelMeet updated to the latest version and only sharing meeting room IDs with trusted participants.

13

Children's Privacy

CastelMeet is a general-purpose video conferencing application intended for users aged 13 years and above. The app is rated for general audiences on Google Play.

We do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe your child has used CastelMeet and provided personal data, please contact us at castelcode.tech@gmail.com and we will take appropriate action within 30 days including deletion of any associated data.

14

Your Rights

As a CastelMeet user you have the following rights regarding your data:

Your Data Rights

  • Right to Access: Request a summary of data we hold linked to your anonymous session ID
  • Right to Deletion: Request deletion of all data — see Section 11 for the process
  • Right to Withdraw Consent: Revoke camera, microphone or notification permissions at any time via Android Settings without deleting the app
  • Right to Opt Out of Analytics: Disable Firebase Analytics via Android Settings → Privacy → Ads
  • Right to Data Portability: Request a copy of any stored data linked to your session in a readable format
  • Right to Object: Object to any specific data processing by contacting us at the address below

To exercise any right, email castelcode.tech@gmail.com. We respond within 30 days.

15

Changes to This Policy

We may update this Privacy Policy as CastelMeet gains new features, as legal requirements change, or as our data practices evolve. When significant changes occur we will:

How You Will Be Notified

  • Update the "Last Updated" date at the top of this page
  • Display an in-app notice on the next app launch after a significant change
  • Update the Privacy Policy link on the Google Play Store listing
  • For material changes affecting your rights, provide at least 14 days notice before the change takes effect

Continued use of CastelMeet after a policy update constitutes acceptance of the revised terms. Previous versions of this policy are available on request.

16

Contact Us

For any privacy questions, data requests, or concerns about CastelMeet, reach Castel Code through any of the channels below:

Castel Code Logo

CASTEL CODE LTD

Centre of App and Software

📍 Lusaka, Zambia

✉️ castelcode.tech@gmail.com

💬 WhatsApp: +260 706 951 176

🌐 castelcode.tech

Response time: within 30 days for data requests · within 5 business days for general enquiries.