Privacy notice

How Feny uses account, booking, workspace and connected Google data.

Feny is a multilingual booking and business-management platform. This notice explains the current data boundaries, including Google Calendar, and how to contact the service at fenix2soft@gmail.com.

Version 2026-10-01

Shared account and workspace boundaries

A user account can sign in to Feny and may be a member of one or more business workspaces. Access to a workspace is decided by that business membership and role.

A client account is not an owner workspace
Revoked access is excluded from workspace navigation
Public Marketplace content is projected separately from workspace data

Data used by Feny

Feny processes account, booking and workspace information needed for sign-in, public discovery, reservations, reminders, business operations and support. Production pages also use cookie-less aggregate web analytics and performance measurements to operate and improve the service.

Account details support sign-in, localization and security
Booking data supports the client and business booking workflow
Workspace data is evaluated only in the active business context

Purposes and legal bases

Where data-protection law requires a legal basis, Feny processes data to take steps requested by the user and provide account, booking, workspace and connected-service functions; for legitimate interests in securing and reliably operating the platform and measuring aggregate performance; with consent for an optional use only when the interface expressly asks for it; and to comply with applicable legal obligations.

Data required for an account, booking or connected feature cannot be omitted when it is necessary to provide that requested function
Legitimate-interest processing is limited to proportionate security, abuse prevention, service reliability and cookie-less aggregate measurement
Consent can be withheld or withdrawn through an available setting, unsubscribe, disconnect or verified request; withdrawal does not affect processing already carried out lawfully
Feny does not reuse data for an incompatible purpose without another valid basis and an updated notice

Google account and Calendar access

Google sign-in uses the openid, email and profile scopes and can provide the Google subject identifier, verified email, name, profile image and hosted domain when supplied by Google. Calendar access is requested separately and only after an explicit Connect action, using https://www.googleapis.com/auth/calendar.events.owned for events in calendars the user owns.

Google sign-in does not itself grant Calendar access
For client bookings, Calendar connection is optional and can be refused without losing the downloadable .ics option
Feny does not request calendar-list, sharing, contacts, Gmail or Drive access

What Feny does in Google Calendar

For a client, Feny creates or updates only the selected confirmed booking event after the client asks. For a connected business, Feny automatically creates, updates and deletes private busy-only events for eligible appointments and group sessions in the primary calendar; when Google Meet is selected, Feny may read that same Feny-created event to obtain its meeting status and link.

Client events can include business, service, property or location and appointment time
Business events contain private busy time and no client, service, contact or payment details
Feny does not list, import, analyze or use unrelated calendar events

Storage, sharing and Google Limited Use

Google API data is transmitted over HTTPS/TLS, and OAuth access and refresh tokens are encrypted at rest. Feny stores the Google identity link, granted scopes and expiry; provider event identifiers and Calendar event links; eligible Google Meet link and status; and synchronization snapshot hashes. Those references and links are protected by account, booking and workspace access controls. Event fields are sent to Google to perform the requested Calendar feature; infrastructure and database providers may process protected data only to operate Feny.

Google user data is not sold, used for advertising, credit decisions, surveillance, data brokerage or training generalized AI or machine-learning models
Google-derived profile name, verified email and avatar may be shown to the business chosen by the client under scoped appointment and client-profile access; a Meet link may be shown only to authorized workspace members and the corresponding authenticated or verified booking participant
People do not read Google user data except with the user’s specific consent, for security or abuse response, when required by law, or for permitted aggregated internal operations
Feny’s use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Google API Services User Data Policy Google Workspace API User Data Policy

Disconnect, retention and deletion

A Calendar connection is retained until it is disconnected. Disconnect asks Google to revoke the token first, then permanently deletes Feny’s encrypted Calendar credential and stored Google event references. If Feny cannot verify revocation, it directs the user to remove Feny in Google Account connections and offers a separately confirmed local cleanup after that removal.

Events already created in Google Calendar remain there until the Google account owner deletes them; Google token revocation may also require reconnection of other Feny Calendar connections using the same Google account
The Google identity link can remain for Google sign-in after Calendar is disconnected and is removed through account deletion or a verified privacy request
Short-lived OAuth state and PKCE records expire after ten minutes; security audits do not contain OAuth tokens or Google event payloads

Manage access in your Google Account Contact Feny about privacy

Roles and access requests

Feny determines the purposes and means for platform-account authentication, platform security, support and operation of its public pages. A business determines how it uses its client, appointment and workspace records, and Feny may process those records for that business under the applicable arrangement. The precise controller or processor role therefore depends on the record and context.

Use Feny support for a platform account, security or privacy request
Contact the relevant business about its service and client records, or use the authenticated workspace for operational changes
Requests can require verification before a change or disclosure

Retention criteria and requests

Use the protected support form or fenix2soft@gmail.com for privacy and data requests. Outside the specific Google and short-lived workflow periods stated in this notice, retention depends on the purpose, record type, sensitivity, security risk, active account or workspace relationship, dispute needs and applicable record-keeping obligations.

Booking, payment, security and audit evidence may need to remain after mutable profile or workspace data is erased
Feny limits a verified request when retention is still necessary for another person’s rights, security, an applicable obligation or a legal claim
When no continued basis applies, a verified request can be used to seek deletion or anonymization of the relevant data

Your data-protection rights

Depending on the law that applies to you and the relevant record, you may request confirmation and access, a copy, correction, deletion, restriction, portability or object to processing. You may also withdraw consent for a consent-based use and complain to the competent data-protection authority. These rights are not absolute and can be limited by other people’s rights, security, legal obligations or legal claims.

Choose Privacy and data in the support form or email fenix2soft@gmail.com
Do not send identity documents through the general form; Feny may instead require additional authenticated verification
State the account, business and request clearly so Feny can identify the relevant role and records without collecting unnecessary data

Help us understand visits from search

After consent, feny_organic_consent_v1 stores your choice and feny_organic_acquisition_v1 links a visit to subsequent product steps. Both are first-party HttpOnly cookies, valid for up to 30 days. The linked measurement history is retained for up to 90 days. Only the search engine, page path, language and product milestones are measured; no search terms or full referrer URL are collected. Turning off measurement removes the linked measurement history for this browser.

With your permission, Feny links a search visit to registration, business setup or a booking for up to 30 days. We do not collect your search terms. Optional; you can change this on the Cookies page.

Need a practical next step?

Use the product screen for account and workspace actions, or send a minimized support request.

Open support