Privacy notice

Garage stores information supplied by its users and connected services: account names and email addresses; client, vendor and applicant details; project briefs and schedules; uploaded files; messages and approvals; finance records and payment references; notification preferences; and activity and delivery records. The information held depends on the features used and the user’s role.

Authentication uses account credentials and session cookies. Browser push, when enabled, stores a device subscription so notifications can be sent to that browser. Hosted card checkout is handled by the payment provider; Garage does not collect card numbers or security codes in its own forms.

Information is used to authenticate and approve users, provide access to assigned work, manage client projects and suppliers, process approvals and finance workflows, deliver requested notifications, and diagnose connection failures. Authorized administrators manage access to these records.

An administrator authorizes Calendar event access for a Google account. The granted permission can cover events on calendars accessible to that account; the Garage connection is configured to use a selected calendar. Garage checks access, reads linked event records, and creates, updates or removes its linked project and campaign events.

Event details may include a project or campaign title, job code, dates, status, client name where provided, reminder offsets, and a link back to Garage. The bridge stores calendar and event identifiers, update timestamps and deletion state to keep synchronization consistent. OAuth credentials and the refresh token are stored in the Hostinger bridge environment; access tokens are used by the bridge to call Google. They are not displayed in Toolbox or stored in the source repository.

Calendar synchronization runs from Garage to Google. It does not import Google edits into Garage and does not add attendees or send calendar invitations.

When these separate connections are configured, Garage sends project information to an authorized Google Apps Script to create project folders, upload or list project files in the configured Drive location, and record activity in a selected spreadsheet. File contents, file names, project identifiers and activity details are processed for those purposes. Garage can store the resulting Drive folder and file links. The Google account authorizing the script determines the access available to it.

Hostinger hosts Garage, the connection bridge and their stored records. Configured Google services receive the information needed for the features described above. Zoho Books receives customer and finance information for requested bookkeeping operations. Lipila receives payment-request and payer details needed for its checkout or collection workflow. Mailchimp receives contact and audience-segmentation information when that connection is used. Email and push providers receive the addresses or device subscriptions and content needed to deliver notifications.

Records are also available to Garage users with the relevant permissions. Provider-side copies are subject to the provider’s own controls and policies. Authorizing Calendar does not make the calendar or Garage projects public.

Garage’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Google user data is not sold, used for advertising, or used to train generalized artificial-intelligence or machine-learning models.

Garage and bridge records remain in their configured persistent storage until removed through supported controls or an administrator’s maintenance process. There is no single automatic deletion period for all record types. Financial or project records may need to be retained for ongoing work or applicable recordkeeping requirements. A copy stored with a connected provider is not automatically removed whenever a Garage record is removed; Calendar linked-event removal is handled as described above. Backups and provider records have separate retention arrangements.

You can manage available notification preferences in Garage and revoke browser notification permission in your browser settings. The authorizing account owner can revoke Google access through Google Account → Security → Your connections to third-party apps and services. Revocation stops future authorized access but does not itself delete existing Garage records or events and files already stored with a provider.

Contact Loghouse using the address below to request access to, correction of, or deletion of your information, or to ask an administrator to disconnect an integration and remove stored credentials. Requests are assessed against the records involved, access permissions and any applicable retention requirements.