F2F F2F privacy notice
This website and the F2F app
This marketing website does not use Google Analytics, advertising pixels or analytics cookies. Language is carried in the page URL. Our hosting provider uses Cloudflare security protection, which may set a short-lived __cf_bm cookie to distinguish automated traffic from real visitors; it expires after 30 minutes of inactivity. The application is a separate service: sign-in, account administration, field responses and location handling are covered in the application sections below.
When you contact us
If you email us, we receive your email address and the information you include so we can answer and follow up your request. Please do not include passwords, verification codes or unnecessary personal information about other people. Hosting and email services also process technical information needed to deliver and protect their services.
Questions about your information
Contact support@dialognorge.no for questions about access, correction, export or deletion. If your information was collected in a campaign, include the organisation’s name so the request can be directed to the organisation responsible for that campaign. You may also contact the relevant data protection authority.
Account and identity scope
F2F stores the organization name, country, optional website or public reference, reporting timezone, first-administrator identity details, and legal acceptance metadata needed to create and support an account.
One verified WorkOS identity or email maps to one F2F global identity. That identity may later hold memberships in more than one commercial account, but customer data stays scoped to the actively selected commercial account and customer organization.
Operational data handled in the service
F2F stores user account data, customer configuration, response data, seller location data, and audit or support events needed to run, secure, and review the service.
Archived users may remain in retained operational history so prior actions, seat history, and support evidence stay attributable even after active access ends.
Seller location and offline handling
Seller location is handled as current or last-known active location for the selected customer organization. F2F does not describe continuous background tracking, route history, or route playback.
Pending unsynced responses may be stored locally on the device until they sync. Clients must keep that local storage limited to pending F2F payloads and must not import or replay legacy D2D offline payloads into F2F.
Retention, anonymization, and support
F2F does not collect personal national identification numbers in any jurisdiction. Response and contact data is kept in an anonymization-ready shape so direct donor or buyer details can later be removed while approved non-PII reporting dimensions remain available for historical statistics.
Privacy, export, and deletion questions are handled through Dialog support at support@dialognorge.no. Legal acceptance records and account-control evidence are retained as operational records for security, support, and commercial review.