Privacy Policy

Effective October 25, 2026

FREBLK is a social scheduling application that helps users understand when they are free, compare availability with people and groups they choose, and coordinate plans. This Privacy Policy explains what data FREBLK accesses, collects, uses, stores, shares, retains, and deletes.

1. Information users provide to FREBLK

Depending on how a user chooses to use FREBLK, the service may process account and profile information such as name, email address, username, profile photo, interests, availability status, city or school preferences, events created directly in FREBLK, friend relationships, group memberships, plan proposals, votes, messages, and privacy preferences.

2. Google Calendar data FREBLK accesses

Google Calendar connection is optional. If a user chooses to connect Google Calendar and grants permission, FREBLK requests the read-only Google Calendar scope needed to retrieve calendar information.

Information returned by the Google Calendar API may include calendar event titles, event start and end times, event locations, all-day event information, cancellation status, and other event metadata provided through the read-only calendar API response.

FREBLK does not use its Google Calendar read-only permission to create, modify, or delete events in a user's Google Calendar.

3. How FREBLK uses Google user data

FREBLK uses Google Calendar data only to provide user-facing scheduling functionality requested by the user. Specifically, FREBLK uses calendar information to:

display imported calendar commitments inside the user's FREBLK schedule;
determine when the user is busy or free;
calculate free-time windows;
detect scheduling conflicts;
compare availability with friends or groups when the user has chosen to share schedule access; and
support plan proposals and other scheduling features initiated by FREBLK users.

FREBLK does not use Google Calendar data for advertising, ad targeting, credit decisions, or selling user profiles.

4. How Google Calendar data is stored

When a user connects Google Calendar, FREBLK may import calendar event information into FREBLK's application database so that scheduling and availability features can operate. Imported event records may include the event title, start time, end time, and location. FREBLK's current Google Calendar connection is read-only.

FREBLK may also store connection metadata needed to remember that a calendar was connected. Authentication and application data are handled through FREBLK's service providers and infrastructure.

5. How Google Calendar data is shared

FREBLK does not automatically make a user's full Google Calendar visible to other FREBLK users. Users control schedule-sharing permissions inside FREBLK.

Depending on the user's selected sharing level, another approved friend or group may be allowed to see only that a time is busy, an event name, additional event details, or no information. FREBLK does not sell Google user data to third parties.

6. Other service providers

FREBLK uses service providers to operate the application, including infrastructure for authentication, database storage, application hosting, and network delivery. These providers may process information on FREBLK's behalf only as necessary to provide those services.

7. Google API Services User Data Policy

FREBLK's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

8. User-controlled schedule privacy

FREBLK provides privacy controls so users can decide who can access schedule information and at what level. Friendship alone does not automatically grant full calendar access. Users can choose busy-only, event-title, fuller-detail, or no-sharing settings where those options are available.

9. Data retention

FREBLK retains account and application data while it is reasonably needed to provide the service and maintain the user's account. Imported calendar records may remain in FREBLK until they are removed through application functionality, the relevant connection is disconnected and associated data is removed, the user deletes relevant information, or the user's account is deleted, subject to legitimate security, legal, or backup requirements.

10. Disconnecting Google Calendar

A user can disconnect a supported calendar connection from FREBLK. A user can also revoke FREBLK's Google Account access through Google's account permission controls. Revoking access prevents FREBLK from making new authorized Google Calendar API requests using that authorization.

11. Account deletion

FREBLK provides an account-deletion control in Settings. When a user requests account deletion, FREBLK will remove or de-identify account data as required to complete deletion, subject to information that must be retained for legitimate security, fraud prevention, legal, or technical backup purposes.

12. Security

FREBLK uses reasonable technical and organizational safeguards designed to protect information from unauthorized access, loss, misuse, or alteration. No online service can guarantee absolute security.

13. Children

FREBLK is not intended for children under 13.

14. Changes to this policy

This Privacy Policy may be updated as FREBLK changes. The effective date at the top of this page will be updated when material changes are made.

15. Privacy questions

Privacy questions can be raised through FREBLK's support channel or account interface. FREBLK will publish a dedicated branded support contact as part of its production support setup.