Privacy Policy

Data handling at a glance

• Public website: hosting and external content providers receive IP addresses and normal request metadata to deliver pages, fonts, charts and market quotes. The dashboard does not require a visitor account or request access to a visitor's Google Drive.
• Authorized operator storage, when enabled: project file contents and metadata are processed to save, retrieve and verify backups. The planned drive.file permission is limited to app-created or explicitly authorized files. Access and refresh tokens maintain that connection; Google passwords are never received.
• Recipients and protection: Google and the authorized automation environment process the disclosed storage operations. Secrets and private working files must stay out of public source code, website files and job logs. Google user data is not sold, used for advertising, or used to train the public forecasting models.
• Retention and deletion: the operator controls the retention of project files in Drive. Tokens are kept only while needed for the connection. Removing Google access stops future authorized access but does not erase existing files; delete those files separately and request removal of app-controlled copies through the privacy contact route. Provider-controlled technical logs follow the provider's retention settings.

The sections below explain these categories, their purposes, service providers, safeguards and deletion choices in detail.

1. Website information and its use

To deliver a page or public data file, hosting infrastructure receives the visitor's IP address, requested URL, request time, and technical browser or device information. Requests may also contain a referrer. This information is used for delivery, availability, error investigation and abuse prevention.

The dashboard's own page code does not create visitor profiles, set tracking cookies, use local storage for personal data, or embed advertising pixels, Google Analytics or session replay. A browser may cache public files. Infrastructure providers can maintain operational records under their own policies.

Public forecasts use market information and previously issued market predictions. A visitor's identity, browsing activity, private Drive documents or Google account information is not an input to the public forecasting models.

2. Google Drive access and data use

The intended Drive connection is for an operator who explicitly authorizes ETH Forecast to store and retrieve project files. Reading the public website never authorizes access to a visitor's Google account. Google handles the sign-in and consent process; ETH Forecast does not receive a Google password.

Data involved in an authorized connection

• Project file contents: files the app creates or the operator explicitly permits it to access, such as project-owned market-data backups, published forecast exports, research reports and operational checkpoints.
• File metadata: file and parent-folder IDs, names, MIME types, sizes and modification times needed to locate, upload, download and verify those files.
• Authorization data: granted permissions, access tokens, refresh tokens and expiry information needed to maintain the authorized connection.

The planned permission is https://www.googleapis.com/auth/drive.file, which supports app-created or explicitly authorized files. It is not permission to inspect all of a person's Drive. An existing folder ID alone does not grant access to unrelated files. The connection does not request Gmail messages, contacts, calendars, or an account's profile and email merely for file backup.

Purpose and limits

Authorized Drive data is used to upload, retrieve and verify project backups, restore the operator's project files, and maintain the records needed for the service. Private Google data and authorization credentials are not published as forecast files. Public market records deliberately published by the operator remain separate from private connection data.

AI and machine learning: Google Workspace APIs are not used to develop, improve or train generalized or non-personalized AI or machine-learning models. Private Google user data is not used to train the public ETH forecasting models. Market-model development uses separately collected market sources.

Only permissions needed by an implemented feature may be requested. Any future change in access, purpose or sharing must be disclosed here and in the authorization flow before the changed processing begins.

3. Sharing and service providers

ETH Forecast does not sell Google user data, transfer it to data brokers, use it for advertising or credit decisions, or provide it to third parties for generalized AI training.

When the operator enables Drive storage, Google processes the authorized file requests. The authorized automation environment, GitHub Actions, processes the project files needed for backup or restore. Access is limited to the operator and authorized project maintainers who need it for those operations. Human access to private Google data requires the account owner's permission, except where necessary for security or a legal obligation. Google account credentials and private Drive files are not sent to the public hosting bundle.

Service providers may process information on international infrastructure. Their own privacy policies and service settings govern records they control. Information may also be disclosed when required by law or necessary to investigate abuse or protect the service.

• Google: authorized Drive file storage and OAuth authorization; the dashboard also loads Google Fonts, which sends normal browser request information to Google.
• GitHub: source hosting, automation, project records and support requests. Public issues and repository files are visible to others.
• Vercel: public website hosting and operational request processing.
• jsDelivr: the dashboard's Chart.js library.
• Coinbase and CoinGecko: public ETH/USD quote requests made by the browser, with CoinGecko used as a fallback.

The font, chart and quote providers receive the browser's network address and normal request metadata; they do not receive the operator's Drive authorization tokens from this dashboard. This privacy page itself uses no external scripts or fonts.

4. Data protection

The public site uses HTTPS. An enabled Drive connection must use HTTPS for Google API requests and keep OAuth secrets and refresh tokens in the authorized automation environment's encrypted secret storage, with access restricted to authorized maintainers. Tokens must not appear in public HTML, JavaScript, source commits, downloadable forecast files or job logs.

Only files intended for public distribution may enter the public repository, automation artifacts or website. Private Google files must remain in private storage and temporary authorized processing space. Temporary downloaded private files must be removed when the job finishes. These controls are requirements for enabling the operator connection, not a claim that the planned integration is already running.

5. Storage and retention

Google Drive files: operator-owned project files remain in the authorized Drive account until the owner removes them or ends the backup arrangement. Backup retention is determined by the operator's selected files and settings. Disconnecting OAuth does not delete files already stored in Drive.

Authorization data: connection tokens are retained only while needed for an enabled connection. On disconnection, the operator removes the stored refresh token and any app-controlled private working copies. Google may expire or revoke a token independently.

Public research records: market datasets and forecasts intentionally published for audit and comparison can be retained for the project's lifetime. These are not a database of visitors or their private Google files. Copies already downloaded by others, public Git history and public blockchain transactions cannot be erased by this website.

Technical and support records: hosting and automation providers retain technical logs according to their policies and settings. The operator retains support correspondence only as needed to handle a request or meet applicable obligations, then deletes app-controlled copies. Provider-controlled backups or records can remain subject to their own retention schedules.

6. Disconnecting and requesting deletion

1. Open Google Account connections, select the ETH Forecast connection and remove its access. This stops future access through that authorization.
2. For an operator-run connection, disable the associated Drive backup or restore step and remove its stored OAuth token from the automation's secrets.
3. Delete unwanted project files in Google Drive and empty Drive's trash if you want them permanently removed, subject to Google's or a Workspace administrator's retention rules.
4. Use the privacy contact route below to request access, correction or deletion of information under the operator's control. Revoking access alone does not remove previously stored copies.

The operator may need proportionate confirmation that a request comes from the account or data owner. No password, OAuth token, wallet key or identity document should be supplied in a public issue. Where a legal obligation requires retaining a record, the operator will explain the applicable limitation.

Visitors can also clear browser caches or use browser controls to restrict external requests; this may affect charts, fonts or quotes.

7. Google API Limited Use

ETH Forecast follows the Google API Services User Data Policy, including its Limited Use requirements, for information received from Google APIs and any permitted transfer of that information.

Google authorization is used only for the disclosed project-storage functionality. It does not authorize unrelated profiling, marketing, data resale or generalized AI-model training.

8. Optional donations

The dashboard displays public donation addresses and lets a visitor copy an address. It does not ask for a wallet connection, private key or card details. A donation made using a separate wallet creates a public blockchain transaction containing addresses and amounts. The website cannot erase blockchain records. Following an external link is subject to that site's privacy practices.

9. Privacy contact and requests

Contact the ETH Forecast maintainer, wscha231, through the project support page. A public request should contain only a request for private contact, not personal records or credentials. GitHub may require an account to submit a request.

For a Google authorization, you can also use the app's User support email displayed on Google's consent screen for private correspondence. Include only the information necessary to identify the request and explain what you want accessed, corrected or deleted.

10. Changes to this policy

The date above identifies this version. Material changes will be announced on this site. Changes to Google data access or use will be disclosed before the new processing begins, with renewed consent where required. A future visitor account, subscription, payment or analytics feature will require an updated notice.

한국어 요약 · 개인정보처리방침

EtherForecast(ETH Forecast)는 GitHub 계정 wscha231이 운영하는 이더리움 연구 예측 사이트입니다. 시행일 및 최종 수정일은 2026년 9월 14일입니다. 현재 방문자 회원가입·Google 로그인·개인 Drive 연결 기능은 없으며, 예측 열람에 개인정보 입력이 필요하지 않습니다.

사이트 제공 과정에서 호스팅 업체 등이 IP 주소·요청 시각·브라우저 정보 등 기술 정보를 처리할 수 있습니다. 차트·글꼴·시세를 불러올 때 외부 제공업체에도 일반적인 접속 정보가 전달됩니다.

운영자용 Google Drive 백업·복원은 준비 중입니다. 연결 시 명시적으로 허용한 프로젝트 파일의 내용·파일명·ID·수정 시각과 인증 토큰을 저장·복원 목적으로 처리합니다. 방문자의 Drive나 무관한 파일 전체를 열람하지 않습니다. Google Workspace API를 범용 또는 비개인화 AI·머신러닝 모델 개발·개선·학습에 사용하지 않으며, Google 개인정보를 공개 ETH 예측 모델의 학습에 사용하지 않습니다.

인증정보와 비공개 Drive 자료를 공개 사이트에 게시하지 않으며, 판매·광고·데이터 중개 목적으로 이용하지 않습니다. 필요한 처리는 Google 및 승인된 자동 실행 환경에서 이루어집니다. 파일은 소유자가 삭제할 때까지 보관되며, 연결 해제 시 인증정보와 운영자가 관리하는 불필요한 비공개 복사본을 삭제해야 합니다. 제공업체가 관리하는 로그·백업에는 해당 업체의 보관 정책이 적용됩니다.

Google 계정 연결 관리에서 접근을 철회할 수 있습니다. 접근 철회만으로 기존 Drive 파일이 삭제되지는 않습니다. 개인정보 문의·열람·정정·삭제 요청은 운영자 문의 경로를 이용하세요. 공개 GitHub 요청에는 비공개 연락 요청만 남기고 개인정보·비밀번호·토큰을 기재하지 마세요. Google 인증 화면의 사용자 지원 이메일도 비공개 문의에 사용할 수 있습니다.