Delete your Field Blink account.
Use the form below to request permanent deletion of your Field Blink login, your user record and the personal data tied to your login — your sessions, tokens, app preferences and the personal cache on your devices. Operational records you captured on behalf of your organization (orders, attendance, shop visits, shop registrations, shop photos and the route GPS they reference) are the property of the organization that onboarded you, remain under their control, and are not modified by this request: your name and employee code continue to be the original attribution on those rows.
Important · B2B context, please read first
Field Blink is a B2B platform — operational data belongs to your organization.
Field Blink is sold to companies; their administrators onboard their own field force — DSRs, TSOs, ASMs, merchandisers — onto the system. Records those users capture during the course of work, including orders, attendance, shop visits, shop photos, shop registrations and the route GPS they reference, are the property of the organization that operates the route, not of the individual user. Account deletion removes your login and the personal data tied to it (your user record, sessions, tokens, app preferences and device-side cache); it does not delete your organization's operational history, and it does not scrub, anonymize or replace your name or employee code on those records. Requests to amend or expunge operational records must go through your organization's administrator, who is the data controller for those records.
§ 00
Overview
Field Blink is committed to giving you control over your login and the personal data tied to it — your user record, your sessions and tokens, your app preferences and the personal cache on your devices. This page is the single, web-accessible entry point for requesting that we permanently delete your user account together with that personal data, in line with the Google Play Store account-deletion requirement, the EU General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA / CPRA) and the Pakistan Personal Data Protection Act.
Field Blink does not modify the operational records you appear in — orders, attendance, shop visits, shop registrations, shop photos or the route GPS they reference. Those rows are the property of the organization that onboarded you onto Field Blink, and your name and employee code on those rows remain as the organization captured them, with the original attribution preserved. This is described in detail below.
Because Field Blink is a B2B platform — you were onboarded by an organization's administrator to do work on their behalf — the records you produced during the course of work are not yours to delete individually. The organization that onboarded you is the data controller for those records. This page covers what is in scope for an individual account-deletion request, and what is not.
You do not need to be logged in to submit a request. If you are logged in, we will additionally verify ownership of the active session.
§ 01
What we delete
When your deletion request is confirmed, the following are removed from production systems and from our backup recovery window within thirty days:
Your login & user record
Username, employee code, email, name, role, profile photo and org assignment on the user record itself — removed from authentication and lookup tables. After deletion, your name and employee code may still appear on past orders, attendance, shop visits, shop photos or route GPS that you captured; those rows are owned by your organization and are not modified in any way.
Sessions, tokens & device binding
Password hashes, refresh tokens, push tokens, Traccar tracking IDs, device binding keys, client mutation IDs and any active sessions — revoked and rotated. Your phone stops being able to sign in.
Personal preferences & app state
Theme settings, saved filters, draft entries, last-viewed shop and other per-user UI state cached locally or on the server.
Personal data on your devices
We issue a remote-wipe of your offline sync queue; the SQLite cache PowerSync holds on your phone is purged on next launch. Uninstalling the mobile app accelerates this.
§ 02
What we retain — and why
The records below are kept because the organization that onboarded you is the data controller for them, because the law requires it, or because keeping them with no link to you lets us keep the product honest. None of these records identify you by name once the request has been honoured.
2.01
Operational records you captured (company property)
Orders booked, returns logged, payments collected, attendance timestamps, leave requests, shop visits, shop registrations (new outlets you onboarded) and shop photos. These are the records of the organization that onboarded you onto Field Blink — they are needed for that organization's route-to-market analytics, distributor settlement, payroll processing, statutory tax records and audit trail. Field Blink cannot delete these at an individual user's request; they belong to the organization, not to you.
2.02
Background GPS on operational records
GPS coordinates recorded for attendance, shop proximity checks and route tracking are retained as part of the operational record. They are no longer linked to your name after deletion is processed — the log records the beat, the device identifier (anonymized) and the timestamp.
2.03
Financial & tax records
Filed invoices, payments and credit/debit notes must be kept for the statutory period required by your jurisdiction's tax law (typically 5–7 years). This applies regardless of any individual account-deletion request.
2.04
Aggregate product analytics
Non-identifying aggregate route statistics may be kept for product improvement — no link back to you.
2.05
Redacted audit trail
A redacted record of the deletion event (timestamp, request ID, no personal fields) is kept so we can prove the request was honoured.
If you want operational records amended, restricted or expunged (for example, a wrongly-attributed order, a shop onboarding you'd like corrected, or a photo you'd like removed), direct that request to your organization's administrator. They are the data controller for those records; Field Blink processes the data on their instructions and cannot act on a user's individual request to delete it.
§ 03
How the request works
- 01
You file the form
Submit the request below. You receive an on-screen acknowledgement and a confirmation email to the address on file. If no account matches, we still acknowledge receipt and ask for the identifier you used at sign-up.
- 02
We verify your identity
We send a one-time verification link to the email on the account. If your email is no longer reachable — for example you have already left the organization — coordinate with a current administrator or write to us and we will route the verification through them.
- 03
We revoke your login
Authentication tokens are rotated, active sessions killed, device bindings dropped, your phone and any other device in your name is signed out. Your user record is removed from lookup and authentication tables. Your name and employee code on historical orders, attendance, shop visits, shop photos and route GPS are <strong>not modified</strong> — those records continue to show the original attribution, because they are the property of your organization.
- 04
We notify your organization
As a courtesy and for their own offboarding, we notify the organization that onboarded you that your account was deleted on this date. We share no personal detail beyond the fact that the deletion occurred and the request reference.
- 05
We issue a written close-out
You receive a deletion receipt by email listing the categories removed, the categories retained under your organization's control, and the date the right-to-be-forgotten was satisfied for your user record. We keep a redacted audit entry (no personal fields) for our own accountability.
§ 04 · The request
Submit a deletion request.
Tell us how to find the account. Every field marked with a red asterisk is required. If you don't have all the details, send what you have — we'll ask for the rest by email.
Submission writes to privacy@fieldblink.com · processed during business hours, Mon–Fri, in your region.
§ 05
After submission
Within three business days of submitting the form, you will receive an acknowledgement email from privacy@fieldblink.com with a request reference number. If we cannot locate the account from the details you supplied, we will write back asking for the identifier you used at sign-up — we will not delete any data until identity is verified.
Once verified, the deletion runs in three phases: live identity is revoked and your user record is removed within seven days; your app preferences and on-device cache are wiped within fourteen days; the organization that onboarded you is notified of the deletion event (without further personal detail) within seven days, so they can complete their own offboarding. Operational records you appear in are not modified at any stage — your name and employee code continue to be the original attribution on those rows.
You will receive a written close-out when the right-to-be-forgotten is satisfied for your user record. If you change your mind before the request is processed, reply to the acknowledgement email with your request reference and the word CANCEL. After login revocation, the deletion is final.
§ 06
Questions
If you have any questions about this page or the process it documents, please reach our privacy desk at:
You can also read the full Mobile Privacy Policy for the broader context on how Field Blink collects, uses and stores data — including the B2B context in which field force users are onboarded by their organization.
§ 6·A · Operational-data requests
For orders, attendance, shop visits, shop registrations, shop photos or route GPS — talk to your administrator.
Your organization's administrator is the data controller for those records: orders you booked, attendance you logged, shop visits you recorded, shop registrations (new outlets you onboarded), shop photos you uploaded and the route GPS they reference. Field Blink processes the data on the organization's instructions, and cannot act on a user's individual request to delete it. Account deletion does not anonymize, scrub or replace your name or employee code on those records either — attribution is preserved because the organization needs it for payroll, audit and dispute resolution. If you want a record amended, restricted or expunged, direct that request to your administrator — they will tell the privacy desk what to do.