PPMS Analysis Privacy Policy

1. Information PPMS Analysis processes

PPMS Analysis processes the information needed to provide the app features selected by the user:

• Uploaded PPMS data files and parsed dataset metadata.
• Plot configuration, notes, photos, remarks, project names, and exported .ppms project files.
• Session identifiers, recovery information, sharing permissions, chat messages, and presence activity used for collaboration.
• Browser-local preferences such as recent projects, autosave settings, and UI settings.
• When Google Drive is connected, Google account identifiers such as email address and Google account ID, OAuth access/refresh tokens, Drive folder IDs, and metadata for PPMS Analysis project files.

2. How Google user data is accessed and used

Google Drive access is optional. If a user chooses to connect Google Drive, PPMS Analysis uses Google OAuth to request the permissions configured for the production app. The current Drive integration is used to create, list, read, update, download, and delete PPMS Analysis project files and project history stored in the user's Google Drive.

PPMS Analysis is designed to use a narrow Google Drive file scope so that Drive access is limited to files created by or explicitly shared with the app, including the PPMS Analysis folder, PPMS Analysis .ppms project files, and metadata needed to operate project sync.

Google account email and account ID are used to show which Drive account is connected and to reconnect a user to an existing PPMS Analysis session associated with the same Google account. Google Drive data is used only to provide and improve visible user-facing PPMS Analysis features such as project sync, project loading, project version history, and Drive-backed saves.

3. Storage and retention

Project and session data may be stored in the browser, on the PPMS Analysis backend, and, when Google Drive sync is enabled, in the user's own Google Drive. OAuth tokens are stored on the PPMS Analysis backend so that the app can refresh Drive access after the user grants consent.

Users can disconnect Google Drive from within PPMS Analysis. Disconnecting removes the Drive connection token for that session from the PPMS Analysis backend. Files already saved in Google Drive remain in the user's Drive unless the user deletes them from PPMS Analysis or directly from Google Drive.

4. Sharing and disclosure

PPMS Analysis does not sell Google user data, does not use Google user data for advertising, and does not transfer Google user data to advertising platforms, data brokers, or information resellers. Data may be processed by hosting and infrastructure providers only as needed to operate PPMS Analysis, secure the service, comply with law, or provide the user-facing features requested by the user.

Shared workspace links are controlled by the session owner. A shared link may allow viewers or editors to see or modify the shared workspace content according to the permissions chosen by the owner. The owner's Google Drive library is not browsable by guests through shared links.

5. Security

PPMS Analysis uses HTTPS in production and applies access controls for sessions, shared links, and owner-only Google Drive actions. No online service can guarantee absolute security, so users should avoid uploading information they are not authorized to process.

6. User choices

• Users can use PPMS Analysis without connecting Google Drive.
• Users can export .ppms project files manually.
• Users can disconnect Google Drive in the app.
• Users can revoke PPMS Analysis access from their Google Account permissions page.
• Users can delete PPMS Analysis project files from Google Drive.

7. Children's privacy

PPMS Analysis is intended for scientific and research workflows and is not directed to children under 13.

8. Changes to this policy

This policy may be updated when PPMS Analysis changes how it accesses, uses, stores, or shares data. Material changes should be reflected on this page before the changed data use is applied.

9. Contact

For privacy questions about PPMS Analysis, contact the project maintainer through the public GitHub profile at github.com/Amirux-dev or through the support email displayed on the Google OAuth consent screen.