Privacy policy
This policy describes the private, operator-managed Perp Shadow Capture Archive application and this public information website. It does not apply to unrelated services on the parent domain.
Data handled
- Archive content: selected recordings of public market data, associated manifests and integrity information.
- Google authorization: OAuth client configuration, access and refresh tokens, and account information needed to check that the intended account authorized access.
- Archive operations: application-created folder and file identifiers, filenames, sizes, checksums, transfer results and error information.
- Website requests: hosting and network providers may process ordinary connection information, such as IP address, requested URL and time, to deliver and secure this website.
Trading secrets, account passwords, unrelated personal documents and the entire project checkout are not part of the intended archive payload. Operators must inspect archive scope before upload.
Google Drive scope and purpose
The application uses only drive.file: access to files created by this application or explicitly made available to it, rather than account-wide Drive access. It uses that access to create archive folders, upload files, inspect their metadata and read their contents for verification. It does not use Google user data for advertising or sell it.
Use and transfer of information received from Google APIs must follow the Google API Services User Data Policy, including its Limited Use requirements. This notice does not represent Google certification or verification of this application.
Storage, sharing and security
Archive files are stored in the authorized Google Drive account. OAuth configuration and tokens are stored on the operator's private server with access restricted to the administrator. The application does not intentionally publish tokens in source code, reports or archive payloads.
The application does not make archive files public as part of upload. Existing Google Drive sharing remains under the account owner's control. Google processes files and authorization under its own policies. The hosting provider processes requests to this public site; no archive or OAuth token is served by this site. No application analytics, advertising scripts, forms or cookies are included here.
Access restrictions and integrity checks reduce risk but cannot guarantee that any system is immune to compromise, interruption or data loss.
Retention and deletion
Archive files remain in the authorized Drive account until the owner or an explicitly authorized retention process removes them. The current validation does not enable automatic cloud deletion. Local source files must not be treated as disposable solely because upload finished; verification and a separately approved retention policy are required.
Authorization tokens are retained while access is needed. Operational records may be retained to diagnose failures and demonstrate integrity. Removing cloud files does not automatically remove local source copies or past operational records.
Revoke access or request removal
Revoke the application through Google Account connections to prevent future authorized API access. Revocation alone does not delete existing Drive files. The owner can remove those files in Google Drive and should contact the project administrator through the private channel used to arrange access for server-side token or operational-record removal. Do not send passwords, tokens or private keys through this public website.
Changes and contact
The effective date is shown above. Material changes to data use or authorization scope should be explained before requesting new consent. This project has no public sign-up or support form. Authorized users can contact the project administrator through their existing private project communication channel.
摘要：仅处理获准归档文件及必要授权信息；不申请全盘访问。可在 Google 账号撤销访问，已有云端文件需自行删除或联系项目管理员处理。上传完成不等于完整性验证完成。