Privacy Policy

1. Overview

This policy explains how People by Super Simple™ (previously Super Simple Contacts) for Mac, iPhone, and iPad, its optional Raycast, Alfred, and MCP integrations, and this website handle information. “We,” “us,” and “our” refer to Dialect Agency Inc.

2. Contact data in the app

Contact cards, groups, notes, photos, phone numbers, email addresses, postal addresses, relationships, and other contact fields are processed and indexed on your devices. The local database and search index support fast search, offline access, editing, duplicate review, imports, exports, recovery, and printing.

We do not operate a hosted contact relay or maintain a cloud copy of your contact database. Connected providers refresh directly from your device. Optional local MCP shares requested contact information with your desktop assistant, as described in Section 6.

Apple Contacts

If you grant access, the app reads and writes Apple Contacts through Apple’s Contacts framework. You control Contacts permission in system settings.

Imports and exports

Files you import remain under your control. Files you export are saved to a destination you select. Once exported, those files are governed by the storage location and sharing choices you make.

3. Google and Microsoft accounts

When you connect a Google or Microsoft account, authorization and sync requests go directly from your device to the provider you selected. We do not operate a proxy for those requests.

• Google contacts use the Google People API.
• Microsoft personal and work contacts use Microsoft Graph.
• Persistent OAuth credentials are stored in the system Keychain.
• Connected accounts refresh while the app is active, saved edits sync automatically by default, and optional review or local-only policies are available per account.

Google sign-in uses the provider’s standard native-app loopback flow. The provider pages and token exchange use HTTPS. At the end of sign-in, your browser returns a short-lived authorization response over unencrypted HTTP to a temporary listener bound only to 127.0.0.1:47632 on your Mac. The listener closes when sign-in finishes or is canceled and is not reachable from another device.

Your use of a connected account is also subject to that provider’s privacy policy and account controls. You can revoke access through the provider and remove the connection from the app.

Google user data

Data accessed. If you choose to connect Google Contacts, People by Super Simple™ requests your Google account identifier and email address so it can identify the connected account. Through the Google People API, it accesses only the contact information needed for the app’s visible contact-management features: names, nicknames, email addresses, phone numbers, organizations, departments, job titles, postal addresses, birthdays, notes, important dates, URLs, relationships, instant-messaging identifiers, contact photos, contact-group names and memberships, Google contact identifiers, change metadata, and synchronization tokens. The app does not request access to Gmail, Google Drive, Google Calendar, or unrelated Google services.

How data is used. Google user data is used only to provide or improve user-facing features that you choose to use: displaying and searching your contacts, editing contact cards, organizing contacts and groups, finding possible duplicates, importing and exporting contacts, maintaining an offline index, serving optional on-device Alfred and Raycast searches and requests from an AI client you connect through MCP, refreshing changes from Google, and sending your saved creates, edits, group changes, photo changes, or deletions back to your Google account under the sync policy you select. People by Super Simple™ does not create or use aggregated, anonymized, or derived datasets from Google user data.

Storage and protection. Durable contact records and synchronization metadata are stored in the app’s sandboxed local database and search index on your devices. The database is not separately encrypted by People by Super Simple™; it relies on Apple’s App Sandbox and the device and file-protection features configured on your Apple device. Provider-hosted contact photos displayed through Apple’s system image components may be temporarily cached inside the app sandbox to speed repeat display. Authenticated provider requests and responses are handled by a shared, ephemeral networking session that does not use a URL cache.

Persistent OAuth access and refresh tokens are stored in Apple’s system Keychain and may synchronize through iCloud Keychain according to your Apple Account settings. Provider communication is encrypted in transit using HTTPS and goes directly between the app and Google. Google contact records are not copied into the app’s private CloudKit metadata database. If you authorize local AI access, requested Google contact fields go directly to your configured desktop assistant; People does not relay them through a developer-operated server.

Sharing and transfer. We do not sell Google user data or share it with advertisers or data brokers. Transfers to an AI client you connect are described below; diagnostic processing is described in Section 7. We do not use Google user data for advertising, credit or lending decisions, surveillance, or training generalized or personalized artificial-intelligence or machine-learning models. Data is sent back to Google when the app performs the synchronization you request. Other intended transfers occur when you direct a visible feature, such as exporting contacts, approving a transfer to another account, or invoking an optional Alfred, Raycast, or MCP integration that you have connected to the app. Alfred and Raycast receive requested contact fields locally on your Mac. Local MCP sends requested fields to your desktop assistant, which may send them to its AI provider under that client’s privacy settings. Review the client’s data use, retention, and training controls before enabling access. These integrations are described in Section 6.

Retention and deletion. Cached Google contacts, groups, account details, synchronization metadata, recently deleted records, and related local linking decisions remain on your devices while the Google account is connected. Choosing Disconnect removes those database records, queued changes, the local account record, and the OAuth token from the app. It also clears the shared response cache and requests deletion of the connected-account metadata and related linking decisions from its private iCloud metadata stores. Disconnect before removing the app if you want People to clear its local account data. Removing the application alone should not be relied on to erase Keychain or iCloud records. You can also revoke People by Super Simple™ from your Google Account controls. Records stored by Google remain governed by your Google account and are changed or deleted when you save an edit under automatic sync or approve it under the optional review policy.

4. iCloud metadata and feature notifications

People by Super Simple™ may use your private CloudKit database and iCloud key-value storage to synchronize app-owned metadata across your devices. This metadata includes smart groups, contact-linking decisions, and connected-account descriptors such as provider, provider account identifier, display name, email address, and a label you assign. Contact cards, provider credentials, and provider synchronization tokens are not copied into these iCloud metadata stores.

This metadata is associated with your iCloud account and handled through Apple’s infrastructure, encryption, retention, and account controls. Contact-management metadata is stored in your private database, not a public database.

Optional new-feature notifications

In version 1.0.2, if you turn on new-feature notifications, People requests system notification permission and uses Apple’s CloudKit and push-notification services to deliver release announcements, including while People is closed. Your on/off choice and the time it changed are saved locally and synchronized through iCloud key-value storage. Apple manages the account-associated announcement subscription and device delivery information. People does not send your contact database as part of notification setup.

Release announcements contain public feature text and a version number in a public CloudKit database. This is separate from your private contact-management metadata. You can turn announcements off in People Settings or control delivery on an individual device in system notification settings. A saved opt-out may need People to reconnect to iCloud to finish removing the announcement subscription.

5. Subscriptions and purchases

Version 1.0.2 will provide a 30-day free trial without a purchase and saves only its start and last-observed dates in the system Keychain, with iCloud Keychain synchronization where available. Purchases, subscription status, billing, renewal, cancellation, and refunds are handled through Apple and your Apple Account. We do not operate a payment server or receive your complete payment-card information.

Apple may provide transaction status needed for the app to unlock subscription access. Apple’s own privacy terms govern its handling of purchase information.

6. Mac integrations and AI access

Raycast and Alfred

The optional Mac integrations search the app’s existing on-device index through a versioned, read-only service while People by Super Simple™ is running. Neither integration reads the app’s database directly, maintains another contact database, or receives provider credentials.

The integration service binds only to 127.0.0.1, so it is not reachable from other devices or the internet. Its launcher routes return search results and requested contact details over unencrypted HTTP on the Mac’s loopback interface. Alfred and Raycast access keys cannot authorize contact changes or MCP requests.

The app generates separate 256-bit access keys for Alfred and Raycast, stores them in this Mac’s system Keychain, and checks them in memory on every contact request. You pair an integration by copying its matching key from the app into that integration’s configuration. Raycast stores its key as an encrypted extension preference; Alfred stores its key in the workflow configuration. Other local software without a valid key cannot query contact data through the service. Software that can read an integration’s configuration, or observe the key while you copy it, may be able to use that key. You can regenerate both keys in the app’s settings, and quitting People by Super Simple™ stops the service.

Local AI access with MCP

Version 1.0.2 will include a local Model Context Protocol (MCP) service on Mac. In Settings → AI Connections, read the sharing notice and choose whether your assistant can read or change contacts. The Install for Claude action will provide a desktop extension for Claude Desktop, without editing a configuration file or copying a separate key. Advanced configuration remains available for other compatible desktop assistants. No Python, separate People account, browser sign-in, or hosted contact relay is required. Keep People open and your Mac awake, with an active trial or subscription. Ordinary browser chats and mobile assistants cannot connect to this local service.

Your assistant’s connection setup includes a private access credential. Protect connection packages and copied configuration: software or people who obtain them may use those permissions. The original credential stays in this Mac’s Keychain and is separate from Alfred and Raycast keys.

The Claude extension launches a standalone native helper using its private credential file; advanced configuration uses the app’s native MCP mode. Both communicate with People over authenticated HTTP bound to 127.0.0.1:47631. This unencrypted loopback connection stays on the Mac. The native mode does not directly open the contact database or receive contact-provider credentials. Requested account information, search results, and supported contact details go directly to the desktop assistant. Binary contact photos and provider metadata are omitted. People does not route this data through a hosted People service.

The service and contact edits operate on your Mac. When you ask for contacts, People returns the requested information to your assistant. The assistant may send, store, and process it with its AI provider under their privacy and retention policies. Review those policies and controls before connecting. Local MCP does not mean all AI processing stays on your Mac. Google-sourced contacts must not be used to train generalized AI or machine-learning models; client settings do not override the Google Workspace data-use restrictions.

AI access and contact changes are separate global controls, both initially off. They apply to every assistant using the current configuration. Permitted edits save locally immediately without another confirmation in People, then follow the account’s automatic, review-before-sending, or local-only sync policy. Upload review does not delay the local save. MCP does not offer contact deletion, merging, group editing, or CSV export.

Turn off AI access to pause every assistant, or turn off contact changes to retain read-only access. Reset access for all assistants invalidates every previous MCP installation and configuration; install or configure the connection again to reconnect. This does not affect launcher keys, undo saved edits, or remove information already retained by an assistant or AI provider. Use those services’ deletion and retention controls for their copies. See setup and troubleshooting.

7. Crash diagnostics

People uses Sentry to receive crash reports and related technical diagnostics so we can investigate failures and improve reliability. These reports can include stack traces, app and operating-system versions, device information, a random installation identifier, session-health information, and technical context around a failure, including automatic app and network breadcrumbs. Sentry processes diagnostics on our behalf; this is separate from connected-account sync and optional AI access.

We disable Sentry’s default personal-information collection and app-hang tracking. On iPhone and iPad, screenshot and view-hierarchy attachments are also disabled. We do not intentionally attach your address book or contact cards to crash reports. These settings do not establish that every possible diagnostic field is free of personal information. Please avoid sending contact exports, credentials, or sensitive contact details when reporting a problem.

Diagnostic reports are retained in our Sentry project under its configured retention settings and access controls. For questions about diagnostic data or deletion, contact us below. Sentry describes its handling of service data in its Privacy Policy.

8. This website

This website does not use advertising cookies, tracking pixels, behavioral analytics, or contact forms. It is hosted by Vercel, which may process routine technical request data such as IP addresses, browser headers, and security logs to deliver and protect the site. Vercel handles that information under its Privacy Notice.

9. Retention and your control

Local app data remains on your devices until you remove it, delete the app and its data, or use the relevant system controls. Provider records remain subject to your Apple, Google, or Microsoft account settings. Private iCloud metadata remains subject to your iCloud controls.

You can disconnect providers, revoke their authorization, manage Apple Contacts permission, disable or revoke MCP access, turn off feature announcements, delete exported files, and manage your Apple subscription from the corresponding account or system settings. Information already shared with an AI client or provider remains subject to its retention and deletion controls.

10. Security and children

We use platform security features such as the system Keychain, App Sandbox, Apple device and file protection, private CloudKit databases, and encrypted HTTPS provider connections. The temporary Google sign-in callback, launcher integrations, and local MCP bridge use the unencrypted, device-only loopback connections described above. Your separately selected assistant may use HTTPS connections to its AI provider. No method of storage or transmission can be guaranteed to be completely secure.

People by Super Simple™ is a general productivity tool and is not directed to children under 13. We do not knowingly collect children’s personal information through a developer-operated service.

11. Changes to this policy

We may update this policy when the product, law, or our practices change. We will post the revised policy here and change the effective date. Material changes will be communicated through an appropriate product or website notice when required.

12. Contact

For privacy questions or requests, contact privacy@supersimplecontacts.com.

Dialect Agency Inc.