1) Controller & contact
RasterForge is operated by Morten Fjord & Malthe Dahl in Denmark. We act as the controller for personal data processed via the Service.
Contact: privacy@rasterforge.com
2) Data we collect
Account data
- email address and account identifiers
- authentication/session tokens
- credit/usage counters (e.g., number/size of runs)
Workspace & content data
- uploaded files (e.g., GeoTIFF/PNG imagery)
- derived artifacts you choose to save (renders, masks, vectors)
- AOIs/bounds, CRS information, render recipes
- prompts (clicks/boxes/text), layer names, timestamps
- field validation campaigns, uploaded validation geometries, answers, GPS coordinates, accuracy, heading diagnostics, and observation timestamps
Technical & log data
- IP address, user agent, basic request logs (security/abuse prevention)
- error logs and performance diagnostics
Beta access requests
- contact details, organization, role, and workflow details submitted through the request access form
- hashed anti-abuse signals used to limit spam and duplicate submissions
- review status and admin notes used to decide whether to invite a requester
3) How we use data
We process data to:
- create and manage accounts
- store and restore your workspaces (so you can resume later)
- run segmentation on our backend (SAM 3) and return results to you
- save field validation observations so you can compare real-world checks with model outputs or uploaded boundaries
- enforce credits/limits and prevent abuse
- review invite-only beta access requests and send related transactional email
- debug errors and improve stability
Legal bases (EEA/UK)
- Contract: to provide the Service you request
- Legitimate interests: security, abuse prevention, debugging
- Consent: optional analytics, if we add any
4) Storage & processors (Cloudflare D1 + Cloudflare R2)
We use Cloudflare as our primary infrastructure provider:
Stores uploaded imagery and saved artifacts (e.g., renders, masks).
Stores account records, workspace metadata, field validation observations, pointers to stored objects, and usage/credit counters.
Data location
Cloudflare services may process data in different regions depending on configuration. For D1, Cloudflare supports restricting database storage to certain jurisdictions (such as the EU) when the database is created. If we enable that, we will describe it here.
Sharing
We do not sell personal data. We share data only with service providers acting on our behalf (primarily Cloudflare) and when required by law.
5) Retention
- Workspace data is kept until you delete it or delete your account.
- Field validation observations remain workspace data and can include user-linked location records.
- After deletion, we may retain limited backups/logs for up to 30 days for recovery, security, and debugging.
- Basic logs are typically retained for 14 days.
- Pending or waitlisted beta access requests may be kept while the beta is active. Declined or spam requests may be retained for up to 180 days, and anti-abuse hashes for up to 30 days.
6) Security
We use reasonable security measures (TLS in transit, access controls, least-privilege). No system is perfectly secure. Don’t upload data you can’t afford to have exposed.
7) Your rights
Depending on your location, you may have rights to access, correct, delete, or export your data, and to object or restrict certain processing.
To request help, email privacy@rasterforge.com.
8) Changes
If we update this policy, we’ll change the “Last updated” date and post the new version here.