Privacy Policy
Silvester Studio CRM · last updated 25 August 2026
Silvester Studio CRM (“the app”) is a single-user tool used internally by Sylvester Studio, a one-person marketing agency based in Chișinău, Republic of Moldova. It runs locally on the operator’s own computer. It is not offered to the public and has no user accounts.
Who we are
Sylvester Studio, Chișinău, Republic of Moldova.
Contact: silvesterstudio.help@gmail.com
What data the app accesses
With your explicit consent, the app requests one Google API scope:
https://www.googleapis.com/auth/calendar.readonly— read-only access to your Google Calendar events.
This scope is read-only. The app cannot create, modify or delete anything in your calendar.
Why it accesses that data
The app displays your calendar events alongside the operator’s own work records, so that time booked in the calendar can be compared with work logged in the app. Event titles, times, descriptions and colours are used solely to display and categorise those events.
Where the data is stored
All data — including the mirrored calendar events — is stored in a single SQLite database file on the operator’s own computer. Nothing is uploaded to a server, and the app has no backend, no hosting and no cloud storage.
Who the data is shared with
No one. Data obtained from Google APIs is never sold, rented, transferred or disclosed to any third party. The app contains no analytics, no advertising and no tracking of any kind.
Limited Use disclosure
Silvester Studio CRM’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Retention and deletion
Calendar data is kept locally only for as long as the connection is active. Disconnecting inside the app deletes the stored access credentials and all mirrored calendar events immediately. You may also revoke access at any time from your Google Account permissions page, or delete the local database file outright.
Security
Credentials are stored locally on the operator’s machine and are never transmitted anywhere except to Google’s own authentication endpoints.
Changes
Any change to this policy will be published on this page with an updated date.
See also our Terms of Service.