Privacy Policy

Effective October 5, 2026 · Operator: SSP · 한국어

This policy covers SSP, a Windows desktop photo-workflow application, its optional Google Calendar integration, local photo operations, and this information website. Contact: bms7732@naver.com.

1. Information accessed or stored

• Account and authorization: the connected account's email address, OAuth access and refresh tokens, and local account identifiers.
• Calendar list: accessible calendar names, identifiers, access roles and information needed to choose calendars. Names and identifiers of selected calendars are saved in local settings.
• Selected calendar events: event titles, identifiers, dates, times, locations, cancellation status and descriptions. SSP extracts photography details such as locations, explicitly identified bride and groom names, name candidates, and role-labelled contact details. Full event descriptions are not retained in the event storage file.
• Local photo workflow: user-selected photo files, capture metadata, folder paths, photographer settings, and operation and backup records. Files are processed in user-selected PC, external-drive or NAS locations.

2. Purposes

SSP identifies connected accounts, lets users select calendars, displays photography schedules and uses user-reviewed dates, locations and customer names to associate photo groups and prepare local folder names. Extracted contact details are displayed for the user's review; SSP does not automatically contact anyone. Local workflow data supports photo copying, organization, backups, verification and recovery.

3. Permissions and consent

Google connection is optional. Sign-in and authorization take place on Google's pages in the system browser. SSP does not receive or store Google passwords. It requests only calendar.calendarlist.readonly to list calendars for selection and calendar.events.readonly to read events and descriptions from user-selected calendars. It does not request calendar creation, editing or deletion, Gmail access, or Google Drive file access. Importing photos, entering schedules manually and backing up photos work without Google connection.

4. Storage and security

Settings, schedules and operation records are stored on the user's PC. The default app-data location is %LOCALAPPDATA%\SSP; a configured alternative data directory is used where applicable. Tokens are encrypted with Windows DPAPI, tied to the Windows user account. Google authorization and API requests use HTTPS. Event files, folder names and operation or backup records are not separately encrypted by SSP. Users manage access and security for their selected NAS, shared folders and backup destinations.

5. Sharing and Limited Use

SSP has no feature that uploads calendars or photos to the publisher's servers. It does not sell Google data or photos, or use them for advertising, credit decisions or general-purpose AI model training. Google communications are used for authorization, token refresh and calendar retrieval. User-directed backups or shared folders may contain photos, photography folder names and operation records.

SSP's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. If support requires reviewing data, the purpose and necessary scope will be explained and the user's explicit consent obtained first.

6. Retention, disconnecting and deletion

Local schedules, settings and operation records remain until the user deletes them; SSP sets no automatic expiry. Disconnecting Google or uninstalling SSP does not erase all existing local schedules, photo folders, operation records or backups.

• Disconnect: disconnecting an account in SSP deletes that account's local sign-in token and account-list entry. Existing schedules and photos remain.
• Revoke Google access: remove SSP under Google Account third-party connections. Further retrieval requires renewed authorization. Revocation does not delete data previously stored on the PC.
• Delete stored schedules: close SSP, preserve needed records, and delete events.json from the app-data location. Reconnecting or refreshing can retrieve events again. Hiding an entry is not deletion.
• Delete all app data: close SSP and preserve any necessary operation and recovery records before deleting the app-data directory. This removes local settings, connections, schedules, operation history and recovery records; it does not delete photos or backups in other locations.
• Other copies: folder names, .ssp records in photo folders and copies on drives, NAS or shared folders must be managed separately. Preserve necessary recovery and backup records before removing them.

The publisher cannot remotely access or delete files on a user's PC or NAS. Contact support for guidance on the scope and procedure of local deletion.

7. Website and support

This information website provides no user registration, calendar sign-in, photo upload or added visitor-analytics scripts. Its hosting provider may process technical access logs, including IP addresses, to serve and secure the website. Email addresses and information voluntarily sent in support requests are used to respond and provide follow-up support. Deletion of support correspondence can be requested by email.

8. Changes and contact

Changes to processing are reflected in this page and its effective date. Before adding previously undisclosed Google data access or use, SSP provides notice and obtains required consent.

Operator: SSP
Privacy and product support: bms7732@naver.com