Appointment Valet Privacy Policy

Effective date: October 7, 2026 Last updated: October 7, 2026

Infoliage LLC, a Nevada limited liability company ("Infoliage," "we," "us"), makes Appointment Valet for macOS (the "App"). This Privacy Policy explains what information the App handles, where it goes, and the choices you have. It applies only to the App and to support, diagnostics, and privacy requests relating to the App. It does not cover third-party services you connect to the App, such as Google or your CalDAV provider. Those services have their own privacy policies.

Summary

The App runs locally on the Mac on which you use it ("the Mac running the App"). Your calendar data, account credentials, and Google access tokens are stored on that Mac.
During normal App operation, Infoliage does not operate a server that receives your calendar events, contacts, login credentials, or Google data. If you contact us for support, we receive the information you choose to send us, as described in Section 4.
Your CalDAV username and password are stored in the macOS Keychain on that Mac. The App does not send them to Infoliage.
Google access is granted by you through Google's OAuth consent screen. Infoliage does not receive your Google password.
If the Mac running the App provides an "On My Mac" calendar source and you grant Calendar access, you can optionally copy selected events into a dedicated local "Appointment Valet" calendar. This feature is not available on every macOS installation.
Subscriptions and purchases are processed by Apple. Infoliage does not receive or store your payment card information.
We do not sell your information, use it for advertising, or use it for tracking.

1. Information the App Accesses

To provide its features, the App accesses the following on the Mac running the App and through the services you connect:

a. Google account information (Basic Profile). When you sign in with Google, the App requests the email and profile scopes. It uses and stores your email address and, when available, your name to identify which Google account is connected. The App does not use or retain your profile picture.

b. Google Calendar data. The App requests https://www.googleapis.com/auth/calendar.events to read, create, update, and delete calendar events, and https://www.googleapis.com/auth/calendar.calendarlist.readonly to read the list of calendars you subscribe to and related calendar information. These permissions let you select calendars, import appointments, and synchronize events with other calendars you connect. The App does not request permission to create or delete Google calendars or change their sharing permissions.

c. CalDAV calendar data. If you connect a CalDAV calendar (for example, a calendar hosted by iCloud, Fastmail, Nextcloud, or another provider), the App reads and writes events on that server using the account credentials you enter.

d. CalDAV and sync credentials. Usernames, passwords, and any app-specific passwords you enter for CalDAV servers are stored in the macOS Data Protection Keychain on that Mac.

e. Google OAuth tokens. Access and refresh tokens that let the App call Google on your behalf are stored in the macOS Data Protection Keychain on that Mac. You can revoke the App's Google access at any time (see Section 6).

f. Local app data. Sync settings, the mapping between events in different calendars, and app preferences are stored on that Mac, typically in the App's sandboxed container.

g. Purchase status. If you subscribe, the App checks your subscription status on that Mac using Apple's StoreKit APIs. The App does not receive your payment details.

h. Optional local Calendar copies. When you enable local copying, the App requests full Calendar access through macOS EventKit so it can create, find, update, and delete its own copied events. It manages a dedicated calendar named "Appointment Valet" in an "On My Mac" source; it does not use this feature to import or modify unrelated calendars or events. You choose which connected calendars to copy and the detail level for each: Limited copies the event's time range with a generic title and omits its location and description; Full also copies its title, location, and description. Source notifications are not copied, and local copies do not create alarms.

Local copying requires both full Calendar permission and an available "On My Mac" source. Permission can be denied or restricted, and some macOS installations do not provide a local calendar source even when Calendar access is granted. When these requirements are not met, local copying is unavailable; the App does not automatically substitute an iCloud or other network calendar. You can continue using connected Google and CalDAV calendars without enabling local copying.

2. How Information Is Processed

Processing by the App. The App processes the information described in Section 1 on the Mac running the App and communicates directly with the connected services to:

Display your calendars and appointments in the App;
Synchronize appointments between the calendars you connect, including Google Calendar and CalDAV calendars;
Maintain optional copies of selected appointments in the local "Appointment Valet" calendar, using the detail levels you choose;
Keep the App signed in to the services you connected, and let you disconnect them;
Enable features that your subscription tier includes.

During normal App operation, this processing does not send your calendar data, account credentials, or Google tokens to Infoliage.

Processing by Infoliage. We process information you choose to send us for support, and crash reports Apple shares with us, to respond to you, diagnose defects, and improve the App, as described in Section 4. Retention of this information is described in Section 7.

Restrictions on Google user data. The following restrictions apply both to processing performed by the App and to any Google user data Infoliage receives through support correspondence or crash reports.

Our use of information received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements. We use Google user data only to provide or improve user-facing features that are visible and prominent in the App. We do not use Google user data to serve advertising. We transfer Google user data only (a) to provide or improve these features with your consent, including synchronizing events with calendars you choose, (b) as necessary to comply with applicable law, (c) for security purposes, such as investigating abuse, or (d) as part of a merger, acquisition, or sale of assets after obtaining your explicit prior consent. Any successor must comply with this Policy and the Google API Services User Data Policy. We do not allow humans to read Google user data unless we first obtain your affirmative agreement to view the specific data, access is necessary for security purposes, or access is required by law. We do not use Google user data to develop, train, or improve generalized artificial intelligence or machine-learning models. These restrictions apply to Google user data wherever it is addressed in this Policy, including Section 5.

3. Information Transmitted by the App

Calendar data flows directly between the Mac running the App and the services you connected, such as Google and your CalDAV server. Infoliage does not receive it.

For automatic mirroring between connected calendars, event details consist of the event name, location, and time. Other attendees are not copied; only the invitee is included. If you select a limited-detail copy, the App reduces the details according to your chosen settings. When you drag an event into the App for import, the App copies the event details in their entirety, except for substituting the invitee for the destination calendar. These dragged-event imports can therefore include other information from the original event, including its description and attendee information. The destination calendar's sharing permissions determine who can view the copied information.

Optional local Calendar copies are stored in macOS's Calendar data store, separately from the App's sandboxed container. The App writes them to the "On My Mac" source and does not upload these local copies to Infoliage or a cloud calendar. They can be accessed through Calendar and by other applications with appropriate Calendar permission. Copies you export or include in backups are subject to your own sharing and backup settings.

Other transmissions are limited to the following:

Apple. The App and macOS communicate with Apple for App Store downloads, updates, purchases and subscription management, and any data Apple collects under its own policies. See Apple's Privacy Policy.

The App does not send data to Infoliage servers. Subscription status is checked on that Mac with Apple's StoreKit APIs. The App does not include telemetry.

4. Crash Reports and Feedback

The App contains no third-party analytics, advertising, or crash-reporting SDKs. If you have chosen to share analytics with app developers in macOS (System Settings > Privacy & Security > Analytics & Improvements), Apple may send us crash reports through App Store Connect. We receive the standard diagnostic information about the application process at the time of the crash, such as the app and operating-system versions, exception information, and thread stack traces. If a report contains user information, we treat it with the same confidentiality and protections described elsewhere in this Policy, including the Google user data restrictions in Section 2. We use crash reports to diagnose and fix problems in the App. You can turn off this sharing in that setting.

You control any screenshots or logs you create and share. You are responsible for reviewing them, removing information you do not want to disclose, and having permission to share information about other people. The App does not automatically send screenshots to Infoliage. If you contact us for support, we receive the information you choose to send us, such as your email address and any screenshots or logs you include. We use it only to respond to you and improve the App, subject to the Google user data restrictions in Section 2.

We do not sell personal information. We do not share your information with third parties except:

Service providers that help us operate our business, under contracts that limit their use to providing services to us: Google provides our email for App support, privacy, and legal requests. The App does not send your Google Calendar data to our email provider on our behalf. If you email us screenshots, logs, or other information, our email provider processes that material to deliver and store your message.
Legal requirements. When we are required by law, subpoena, or valid legal process, or when we believe disclosure is necessary to protect the rights, property, or safety of Infoliage, our users, or others.
Business transfers. If Infoliage is involved in a merger, acquisition, or sale of assets, your information may be transferred as part of that transaction. Google user data may be transferred only after obtaining your explicit prior consent, as described in Section 2. We will give notice before your information becomes subject to a different privacy policy.
With your direction. When you tell us to share information, or when you connect a third-party service.

6. Your Choices and Controls

Local App data, stored credentials, and local Calendar copies must be removed separately on each Mac and in each macOS user account in which you used the App. Perform the applicable local cleanup steps below in each such account; cleanup in one account or on one Mac does not remove data from another. Provider-side revocation and deletion of events in hosted calendars are separate from this local cleanup.

Disconnect a Google account: Remove it in the App's account settings. This removes the account from the App's current account list and attempts to delete its stored Google tokens. Credential deletion can fail or be prevented by macOS access restrictions, even when the account disappears from the list. Stored credentials may remain and the account may reappear after restarting the App. Removing the account does not itself revoke Google's authorization; revoke the App's access separately at https://myaccount.google.com/permissions.
Disconnect a CalDAV account: Remove it in the App's account settings. This removes the account from the App's current account list and attempts to delete its stored credentials. As with Google accounts, deletion may fail or be prevented by macOS access restrictions, and the App may not display a deletion error. To prevent any remaining credentials from being used, revoke the app-specific password or change the password used by the App through your CalDAV provider, as applicable.
Delete local App data: Remove connected accounts before deleting the App. To remove stored preferences and sync data, delete the folder ~/Library/Containers/com.infoliage.Appointment-Valet after quitting the App. In this path, ~ refers to the home directory of the macOS user account running the App; repeat this cleanup in each account in which you used it. Deleting the App or this folder does not by itself remove credentials from the macOS Data Protection Keychain. Do not assume that removing an account from the App, deleting its container, or looking only in the login Keychain confirms credential deletion. For assistance identifying remaining App credentials, contact us at the address in Section 12. Provider-side revocation prevents further authorized access but does not erase local credential copies.
Withdraw Google access: Revoking access stops the App from reading or writing your Google data. Previously synchronized events remain in your calendars unless you delete them.
Control local Calendar access and copies: You can disable local copying in the App's mirror settings and revoke the App's Calendar permission in macOS System Settings under Privacy & Security > Calendars. Revoking permission, an administrator restriction, or deleting the App or its container does not by itself delete existing local copies. You are responsible for removing any remaining copied events, or the dedicated "Appointment Valet" calendar, through Calendar if you want them deleted. Disabling a local-copy rule can request cleanup of its copied events, but removal requires sufficient Calendar access and can fail.
Delete synchronized events: You are responsible for deleting previously synchronized events from each connected calendar where they remain. Disconnecting an account, revoking access, or deleting the App does not delete these events. Your calendar providers control any retained backups or other copies under their own policies.
Subscriptions: Manage or cancel your subscription in your Apple ID settings, under Subscriptions.

Because Infoliage does not hold the calendar data or account credentials used during normal App operation, we cannot retrieve or remotely delete them for you. To complete deletion of your App data and synchronized events under your control, remove the local App data, confirm that stored credentials have been removed, revoke the App's access at each provider, and delete the synchronized events from each connected calendar. The App's current disconnect behavior does not guarantee credential deletion. If you sent us information for support and want it deleted, contact us as described in Section 12.

7. Data Retention

Data stored locally on each Mac remains on that Mac until you delete it, and we do not control it. Local cleanup applies separately to each macOS user account in which you used the App. Stored credentials can remain if a deletion attempt fails or macOS prevents access, as described in Section 6. Local Calendar copies are stored outside the App's container and can remain after the App is removed or Calendar permission is revoked; remove remaining copies through Calendar as described in Section 6.

We retain routine support correspondence for up to one year after the request is closed. We may retain bug reports and crash diagnostics longer when needed to investigate defects and prevent their recurrence. We periodically review retained reports and delete or remove personal information when it is no longer needed. Technical descriptions and test cases that no longer identify individuals may be retained indefinitely. To request deletion of information you sent us, contact us as described in Section 12.

8. Security

The App stores credentials in the macOS Keychain, uses the App Sandbox, and communicates with Google and CalDAV servers over encrypted connections (HTTPS/TLS). CalDAV connections require HTTPS. No system is perfectly secure, and you are responsible for protecting the Mac on which you use the App and keeping your Apple ID and provider accounts secure.

9. Children

The App is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided information to us, contact us and we will delete it.

10. Your Rights

Depending on where you live, you may have rights to know, access, correct, delete, or port personal information, and to opt out of certain processing. Because we generally do not hold your personal information, most requests are handled through the controls in Section 6. To make a request, contact us at the address in Section 12. We will respond within the time required by applicable law.

California residents. Infoliage does not currently meet the revenue, data-volume, or revenue-from-data thresholds in the California Consumer Privacy Act (CCPA), as amended by the CPRA. Our annual gross revenue is below the applicable revenue threshold. We do not buy or sell personal information of California consumers or households, share it for cross-context behavioral advertising ("sharing" as defined by the CCPA), or derive revenue from selling or sharing it. We nonetheless voluntarily honor requests to know, delete, and correct personal information, as described in Section 6 and in this Section 10. The disclosures to service providers and transfers at your direction described elsewhere in this Policy are distinct from CCPA sharing for cross-context behavioral advertising.

Nevada residents. Nevada law gives residents the right to opt out of the sale of certain covered information. We do not sell covered information.

Third-party direct marketing. We do not disclose personal information to third parties for those third parties' direct marketing purposes.

11. Changes to This Policy

We may update this Policy. We will post the updated version with a new effective date and, for material changes, notify you in the App or by email if we have your address. Before using Google user data in a new way or for a different purpose than originally disclosed, we will notify you and obtain your consent to the updated Policy. Where applicable law or Google's policies require affirmative consent, continued use alone does not provide that consent.

12. Contact

Infoliage LLC 885 West Julian Street San Jose, CA 95126 Email: privacy@infoliage.com Website: https://infoliage.com