Skip to main content

Privacy Policy

last revised on 30 August 2024

This Privacy Policy outlines how and why personal data is processed, collected, stored, and shared when using services officially operated and provided by GeyserTimes as well as how personal data can be requested and deleted.

Processed Data

The following data is only processed locally on the user’s device and not sent off device:

DataPurposeSource
Approximate location (optional)Calculation of sunrise and sunset times for scheduled dark themeDevice with permission for approximate location
Precise location (optional)Suggestion of nearby geysers for geyser inputDevice with permission for precise location

Collected and Stored Data

The following data is transmitted off a user’s device and stored:

DataPurposeSourceRetention Period
IP addressSecurity and fraud preventionDeviceUp to 24 hours and until next login for GeyserTimes accounts
Name (only with account)Attribution and credibility of data, account managementUser inputLifetime of GeyserTimes account
Email address (only with account)Communications, account managementUser inputLifetime of GeyserTimes account
Phone number (only with account, optional)Verification, communicationsUser inputLifetime of GeyserTimes account
Account name (only with account)Unique identifier for attribution and credibility of data, account managementUser inputLifetime of GeyserTimes account
Timestamp of account creation (only with account)Credibility of dataDeviceLifetime of GeyserTimes account
Timestamp of last login (only with account)Security and fraud preventionDeviceLifetime of GeyserTimes account
Database Content (optional)Collection and dissemination of geyser-related dataUser inputForever
Timestamps of contributions (optional)Tracking of content historyDeviceForever
Chat nickname (optional)Unique identifier for attribution of chat messagesUser inputForever
Chat messages (optional)Communications on webcam chatUser inputForever
Crash logs (optional)Diagnosis and fixes for bugs and crashesDevice with permission for Firebase CrashlyticsUp to 90 days
Diagnostics (optional)Performance improvementsDevice with permission for Google Analytics for FirebaseForever (aggregated reporting only)
Page views (optional)Prioritization of development, analyticsDevice with permission for Google Analytics for FirebaseForever (aggregated reporting only)
Firebase installation IDSynchronization of dataDevice using Firebase Cloud MessagingUp to 180 days after session expiration

Shared Data

The following data is transferred to a third party:

DataPurposeThird Party
Name (only with account)Attribution and credibility of dataPublic (with account)
Phone number (only with account, optional)SMS messagingTwilio
Account name (only with account)Unique identifier for attribution and credibility of dataPublic
Timestamp of account creation (only with account)Credibility of dataPublic
Timestamp of last login (only with account)Security and fraud preventionPublic
Database Content (optional)Dissemination of geyser-related dataPublic
Timestamps of contributions (optional)Tracking of content historyPublic
Chat nickname (optional)Unique identifier for attribution of chat messagesPublic
Chat messages (optional)Communications on webcam chatPublic
Crash logs (optional)Diagnosis and fixes for bugs and crashesGoogle (Firebase Crashlytics)
Diagnostics (optional)Performance improvementsGoogle (Google Analytics for Firebase)
Page views (optional)Prioritization of development, analyticsGoogle (Google Analytics for Firebase)
Firebase installation IDSynchronization of dataGoogle (Firebase Cloud Messaging)

Server Location

The server used by GeyserTimes for hosting its website and providing its services is located in Hillsboro, Oregon, United States of America and operated by OVH US LLC. An additional server used by GeyserTimes for backing up the database and its contents is located in New York City, New York, United States of America and operated by DigitalOcean.

External Services

The following external services are used:

ProviderPurpose
Firebase Cloud Messaging (Privacy Policy)Synchronization of data
Twilio (Privacy Policy)SMS messaging
National Park Service (Privacy Policy)Webcams
PixelcasterStreaming webcam
National Weather Service (Privacy Policy)Weather forecast
United States Geological Survey (Privacy Policy)Temperature loggers
University of Utah (Privacy Statement)Seismograms
Yellowstone National Park Static Webcam ArchiveWebcam archive
Google Maps (Privacy Policy)Maps
Google Fonts (Privacy Policy)Fonts
Font Awesome (Privacy Policy)Icons
Donorbox (Privacy Policy)Payment processing for donations
Stripe (Privacy Policy)Payment processing for donations
PayPal (Privacy Statement)Payment processing for donations
reCAPTCHA (Privacy Policy)Fraud prevention
Firebase Crashlytics (Privacy Policy)Crash logs
Google Analytics for Firebase (Privacy Policy)Diagnostics and page views

Cookies and Similar Technologies

GeyserTimes uses cookies and similar technologies to process, collect, store and share data as described above. Additionally, third-party cookies and similar technologies may be used by providers of external services as described above.

Access Request for Personal Data

Users can request a copy of their personal data undergoing processing by contacting the GeyserTimes support (email: support@geysertimes.org). Please note that requests for access to personal data should be sent from the email address associated with the GeyserTimes account.

Account Deletion

Users can delete their account and the associated personal data within the account settings or by contacting the GeyserTimes support (email: support@geysertimes.org). Please note that requests for account deletions should be sent from the email address associated with the GeyserTimes account.

When an account is deleted, all personal data, including name, email address, and username, will be removed, but a remnant of the account will remain. More specifically, the account name will be renamed to ghost<user id> and the name will be renamed to Deleted User #'<user id>. Since GeyserTimes does not allow anonymous contributions, any contributed data will be attributed to the remnant account.