Barq Dev operates Barq Meet, a scheduling service. This policy explains how we handle information about account holders, guests who book meetings, and visitors. Contact meet@barq.dev for privacy questions or requests.
1. Information we collect
- Account information: your Google account identifier, name, email address, profile photo, time zone, username, profile information, preferences, and account approval status.
- Scheduling information: event types, availability rules, selected calendars, bookings, meeting locations, answers to booking questions, and cancellation or rescheduling details.
- Guest information: a guest’s name, email, time zone, form answers, extra invitees, and the meeting they choose. Hosts choose their booking questions; guests should avoid including sensitive personal information that is unnecessary for a meeting.
- Technical information: session identifiers, security logs, limited device and browser information, booking-page view counts, referral and campaign parameters, and product usage events when analytics is enabled.
2. Google account and Calendar access
Google Sign-In identifies you and supplies your name, email, and profile photo. With your permission, we access your calendar list so you can select calendars, event start and end times, availability and free/busy information, and event attributes needed to identify conflicts (such as all-day, declined, or free events). We use this information to show bookable times and avoid conflicting meetings. We do not need to read unrelated event descriptions or attachments.
We create calendar events for bookings, add invited attendees and Google Meet links, and update or delete those booking events when meetings are rescheduled or canceled. We may read public holiday calendars to apply your chosen availability rules. Guests see available slots, not your private calendar or existing event details.
We store OAuth access and refresh tokens encrypted at rest, with encryption keys kept separate from application data. Selected calendar identifiers, settings, booking event references, and a short-lived cache of busy times support the scheduling features. We do not send Google calendar data, tokens, or booking answers to analytics.
3. Google Limited Use disclosure
Barq Meet uses and transfers information received from Google APIs in accordance with the Google API Services User Data Policy, including its Limited Use requirements. These restrictions also apply to data derived from Google API data.
We use Google data only to provide or improve the visible scheduling features described here. We never sell Google user data, use it to serve advertising, or transfer it to advertising platforms, data brokers, credit providers, or information resellers. We do not use it to train generalized artificial intelligence models.
We transfer Google data only with your consent as needed to provide these features (for example, adding invited guests to a calendar event), for security purposes, or to meet applicable legal obligations. Any transfer in a merger or asset sale requires your explicit prior consent. We do not allow humans to read your Google data unless you affirmatively agree to access to specific data, or access is necessary for security purposes, such as investigating abuse, or to comply with law. These limits apply to our staff, contractors, and service providers.
4. Why we use personal information
We use information to authenticate accounts, review access requests, calculate availability, prevent double bookings, deliver invitations and reminders, support cancellations and rescheduling, provide support, and protect against abuse. Hosts receive the details guests submit for their meetings. Other invited attendees may see attendee names and email addresses in calendar invitations.
Where GDPR-style rules apply, our legal bases are performance of the service agreement, our legitimate interests in operating and securing the service, compliance with legal duties, and consent where required (including optional analytics and Google authorization). We do not make legal or similarly significant decisions solely through automated processing.
5. Cookies and analytics
An essential session cookie keeps you signed in and protects your account. Theme preferences may be saved in browser storage. These are used for the service, rather than advertising. When configured, PostHog EU processes limited product analytics on application and public booking pages; we disable input autocapture and session recording and mask page text and element attributes. We do not include booking form answers, guest contact information, Google calendar contents, or tokens in analytics events.
We do not use advertising cookies. Where consent is legally required for optional analytics, it must be obtained before that analytics is enabled. You may block nonessential cookies in your browser; blocking the session cookie prevents sign-in.
6. Service providers and sharing
- Google: sign-in, Calendar and Meet integration; Google Workspace delivers transactional emails containing the meeting and recipient information needed for delivery.
- PostHog EU: limited product analytics when enabled, processed using its EU service.
- Cloudflare Turnstile: bot protection on booking and meeting-management forms. It processes technical browser and network signals to distinguish legitimate use from abuse.
We use these providers for their stated purposes, with access limited to what each function needs. We may disclose information when legally required or necessary to protect people and the service. We do not sell personal information. If processing crosses national borders, we use applicable contractual or other lawful safeguards where required. You can contact us for information about safeguards relevant to your data.
7. Security
We protect information using encrypted connections, encrypted Google tokens, access controls, session protection, rate limits, and restricted operational access. We monitor failures and abuse and maintain backups. No online service can guarantee absolute security. Please report suspected security problems to meet@barq.dev.
8. Retention, disconnection, and deletion
We retain account settings and meeting records while needed to provide the service to you. Busy-time caches are short-lived. Operational and security records are kept only for troubleshooting, abuse prevention, or applicable legal requirements. Database backups rotate out after 14 days.
Deleting your account removes your account and associated application data and revokes your Google tokens. You can request deletion through account settings or by emailing meet@barq.dev from your account address. Removed data expires from rotating backups within 14 days, except where a legal obligation requires limited retention. If a backup is restored, deletion requests must be reapplied.
You can revoke Google access at any time in your Google account permissions. Revocation stops further Calendar access and may make booking unavailable; it does not itself delete your application account. Emails already delivered and calendar invitations held by other participants remain under their control.
9. Your rights and guest requests
Depending on where you live, you may request access to, correction of, deletion of, or a portable copy of your data; restrict or object to processing; and withdraw consent without affecting earlier lawful processing. You may complain to your local data protection authority. Contact meet@barq.dev to exercise these rights. We may need to verify your identity before fulfilling a request.
For guest data collected by a host, the host determines the purpose of the meeting and form questions. Contact the host for requests about their use of your information, or contact us for help with data stored in this service. We do not charge for ordinary privacy requests.
10. Children and policy changes
This service is not directed to children under 13. If you believe a child’s information has been submitted, contact us so we can investigate and remove it. We will update this policy when our practices change and notify account holders of material changes. If a new use of Google data requires consent, we will request it before that use begins.
11. Contact
Barq Dev, Pakistan
Privacy and support: meet@barq.dev