Effective October 6, 2026
Operator and scope
FieldSeen LLC, based in Oklahoma City, Oklahoma, operates the FieldSeen mobile application, web application, website, and related property-inspection services (the “Service”) for customers in the United States. In this Privacy Policy, “FieldSeen,” “we,” “us,” and “our” mean FieldSeen LLC. Privacy questions and requests can be sent to support@fieldseen.com.
This policy covers the FieldSeen service and information supplied by account holders, company members, accountless inspection participants, report recipients, website visitors, people contacting support, and business contacts we email about the Service. An owner or tenant may be recorded by a property manager without having a FieldSeen account.
We receive information directly from people using or contacting the Service; from property managers, workspace members, and other users who supply records about owners, tenants, properties, and inspections; from sign-in and service providers; and from devices and service operations as described below. FieldSeen manages account administration, support, and service-security decisions. A customer who supplies property or inspection records decides why those records are collected and who should receive them; FieldSeen hosts and processes those records to provide the requested service. Our responsibilities and the customer’s responsibilities depend on the particular activity and applicable law. This policy does not replace a property manager’s own privacy notice or any required data-processing agreement.
Accounts and workspaces
We process your email, account identifier, authentication and session information, profile name, onboarding settings, and product-tour progress to register you, confirm your email, sign you in, handle access requests, and identify your work. Phone number and profile photo are optional. The password you enter is passed by the FieldSeen client to Supabase Auth for authentication; it is not stored in property or inspection records. If you choose Google sign-in, Google and Supabase exchange sign-in information, including your Google account identifier and the email/profile information provided through that flow. If you choose Sign in with Apple, Apple and Supabase exchange your Apple account identifier and the email address Apple provides, which may be a private relay address if you choose Hide My Email; Apple shares your name only the first time you sign in, and we save it as your profile name. We do not store Apple sign-in tokens.
Company accounts include company name, optional logo, settings such as an inspection interval, inspection checklists, membership roles, invitations, and ownership-transfer history. A company owner can set a company inbox to receive replies to owner report emails; we email a one-time code to that inbox to confirm it before it is used. Current company members can see teammate names, emails, roles, and profile photos. Portfolio records are available according to workspace permissions; employees can read tenant contact information on properties they can access. Adding an owner contact, ownership entity, or tenant does not create an account or grant workspace access.
A company owner can remove a teammate from the company. Removal ends that person’s access to the company, discards inspection drafts they had in progress there, and revokes any pending invitation to their address; completed inspections, reports, and photos stay with the company. FieldSeen keeps a restricted record of each removal: the removed person’s account identifier, email address, and role, who removed them, when, and how many drafts and invitations were affected. Removal does not delete the removed person’s FieldSeen account.
For supported sensitive actions, such as account deletion and company ownership transfer, a password entered in the verification form is sent to a FieldSeen server function and passed to Supabase Auth to verify the requesting account. It is not saved in FieldSeen’s action records. Those records contain account and session identifiers, the requested action and target, a request identifier, verification method, confirmed email, expiry, attempt count, and result so we can prevent misuse and handle retries. A verification deadline is not a deletion deadline for those records. Restricted FieldSeen administration also uses Supabase authenticator verification; this is separate from ordinary customer sign-in.
You can reset a forgotten password through the recovery link we email you; changing a password from within a signed-in session is currently unavailable. Accounts that sign in with Google or with Apple verify a sensitive action by signing in with that provider again. You may contact support@fieldseen.com about access or deletion without completing an unavailable in-app flow. Sending a request does not by itself establish identity or confirm deletion; we must verify authority and resolve the request through an appropriate supported process.
Property and inspection information
Owner and tenant records may include names, email addresses, phone numbers, property or unit relationships, and invitation status. Property records include addresses, coordinates, names, structures, buildings, units, cover photos, source identifiers, and archive state. Ownership records may describe an individual, LLC, trust, or corporation and related people, roles, primary contacts, and optional ownership percentages. These records are supplied by users; FieldSeen does not independently verify ownership or occupancy.
Inspections contain the property/unit, inspection type, room names and order, conditions, notes, photos, attribution, device and operation identifiers, save/sync status, and timestamps. Notes and photos are optional inputs, although completing an inspection requires its required area observations. A workspace can keep one checklist for each inspection type, made of named rooms and items. An inspection started with a checklist keeps its own copy of that checklist and records an answer for each item (OK, Issue, or N/A) and a note for each issue. Room reuse copies names and order into a new inspection. Comparison reads two completed inspections and displays their evidence; manual area matches are temporary and are not a saved comparison report.
Signatures are optional. A signature entry records the signer’s role (inspector or tenant), typed name, drawn signature image, the time the device reported, the time our server recorded it, and how it was captured: on the inspector’s device, at the end of a tenant-completed inspection, or through an emailed signing link. A tenant’s entry also records the acknowledgment statement shown to them, an optional comment, and the tenant record it was matched to, if any. When no tenant signs, an inspection can instead record the reason (tenant not present, declined to sign, unreachable, unit vacant, or other), an optional note written by staff, and who recorded it. A signing request records the tenant’s name and email address, who sent it, when, and its status. Workspace members who can view the inspection can see these entries, and they are printed in the report, including a tenant’s comment and any staff note. After an inspection is completed, entries cannot be edited or removed; the only later additions are a tenant’s signature or decline through a signing link and a recorded reason for no signature. FieldSeen does not verify a signer’s identity and does not store a signer’s IP address or browser details with a signature.
Selected or captured photos are processed on the device into resized JPEG or WebP images for upload. This processing removes source metadata such as embedded GPS/EXIF from the generated image; the visible image and separate property, author, and timestamp records can still identify people and places. FieldSeen does not delete originals in your photo library. Profile images and company logos are also prepared on-device.
CSV import reads a selected file on your device for review and sends the approved property, building, and unit structure to our database. The raw CSV file is not uploaded by this workflow. Import source identifiers do not connect FieldSeen to a property-management provider.
The Service is for property-condition documentation. Do not submit passwords, payment-card details, government identification numbers, or unnecessary medical or other sensitive personal information in notes, photos, imports, or support messages. The current Service does not include AI model training, facial recognition, tenant scoring, or automated housing-decision features.
Onboarding and access administration
Authorized FieldSeen administration can find accounts and workspaces using names, email addresses, and identifiers, view property counts and import history, and import a reviewed property, building, and unit structure for a selected customer workspace. Import history records the workspace, administrator, request identifier, time, source, and imported counts. The import tool processes the selected CSV on the administrator’s device and sends the approved structured records, rather than uploading the raw CSV through that tool. If you separately send a file to support, that copy is part of the support correspondence described below.
Founding customers can optionally attach their property list to a setup request: one CSV or Excel (.xlsx) file, or up to 10 photos of a paper list, which are prepared on the device like inspection photos. Attached files go to a private storage area kept apart from your workspace records, are checked for their type and for unsafe content such as macros, formulas that run commands or fetch web content, and links to other files, and are used only to set up your properties. Files that fail the check are removed and are not shared. The founder is notified of each setup request by email through Resend, including the file names, sizes, and links to the checked files that expire after seven days; authorized administration can issue new links that expire after five minutes. Anyone holding an unexpired link can open the file. A copy the founder saves while setting up your properties is kept only as long as needed for that setup.
We maintain workspace access status, complimentary-access grants and their expiry or revocation, internal administrative reasons, and action history identifying the administrator, request, and time. The system can record subscription status separately from complimentary access. These are access-administration records. Paid-plan payments are handled as described under “Subscriptions and payments.” Internal reasons and administrator identifiers are restricted administrative data and are not included in the ordinary customer access summary.
Subscriptions and payments
Only a workspace owner can subscribe to a paid plan or manage its billing. Subscribing and managing billing take place on Stripe-hosted pages that open in your web browser. Stripe collects and processes your payment-card or other payment details, billing name, email address, and billing address, and uses the billing address to calculate applicable sales tax. FieldSeen does not receive or store full card numbers or card security codes.
FieldSeen stores the Stripe customer and subscription identifiers linked to the workspace, the plan, the billed unit quantity, billing periods, invoice and payment status, cancellation and grace-period status, and billing adjustments. We use these records to provide paid access, calculate charges, detect and refund duplicate subscriptions, alert FieldSeen administrators to billing problems, and resolve billing questions. Stripe sends FieldSeen subscription, invoice, and payment events; Stripe’s own processing, including fraud prevention, is governed by its privacy policy.
Billing and payment records can be kept after cancellation, workspace deletion, or account deletion where needed for tax, accounting, dispute, fraud-prevention, or other legal purposes, including the Stripe customer record and records Stripe holds under its own retention obligations.
Camera, photo selection, location, and maps
Camera access is optional and is used while you capture inspection photos. Photo selection gives FieldSeen the files you select, not access to your whole address book or a background photo-library scan. You can decline camera access and use supported file selection, or work without photos. Permission choices are managed through your device or browser settings.
With permission, FieldSeen reads foreground device location to center the map. The operating system may provide precise or approximate location. FieldSeen does not keep a device-location history in its database or use background location. A local flag remembers a location-permission attempt. Denying location still permits manual map navigation and address search.
Mapbox receives address-search text and request information, and supplies optional satellite imagery. OpenFreeMap supplies the standard map tiles and fonts using OpenStreetMap data. Requests disclose IP address and the requested map area to the serving provider; that area may reflect your device location when the map is centered there. The search bias is a fixed Oklahoma City location, not your device's current coordinates. Providers process request information under their own applicable notices.
Invitations and report access
Company invitations record the invited email, company, role, inviter, status, token hash, and timestamps. They expire after seven days and acceptance requires sign-in with the matching verified email. A valid link or code can reveal company identity, invited role, expiry, and an optional company logo before sign-in. Acceptance consumes the invitation; it may also be revoked before acceptance.
Tenant inspection invitations record the tenant name and email as an attribution snapshot and grant access to one inspection without an account. The link expires after 14 days and allows resume until completion, revocation, expiry, tenant removal, or property archival. Anyone holding it may act through that invitation; possession is not independent identity verification. The completed report identifies tenant-submitted work using the invitation information.
A signing request emails a tenant a one-time link to one completed inspection. Without an account, anyone holding the link can view that report and sign or decline once; possession is not independent identity verification. The link expires 14 days after it was last sent. Sending it again replaces the earlier link, and it stops working once it is used, cancelled, or closed by staff.
Owner report emails contain a link to the saved PDF. The recipient need not sign in: anyone holding the link may open it while valid. The link lasts seven days from the recorded successful send; an authorized user can request renewed access. Access can also stop if the delivery is revoked or the server's current record/recipient checks fail. FieldSeen records link access times and counts for delivery operations. Link access does not prove who read the report.
A tenant who signs is emailed a private link to the PDF that carries their signature. It goes to the address the signing link or inspection invitation was sent to or, for a signature made on the inspector’s device, to the email on the matching tenant record when there is one. When a tenant declines through a signing link, or staff record that a tenant declined or could not be reached, a copy of the report can be emailed to that tenant in the same way. These links need no sign-in, can be opened by anyone holding them, and last seven days from the recorded successful send; they also stop working if the inspection or property is archived.
Private PDF download URLs issued after access checks last 60 seconds. Other private photo URLs can last up to one hour; invitation-preview logo URLs last five minutes. Previously issued URLs may remain usable until expiry after a role or access change. Expiry prevents later authorized retrieval through that link; it cannot erase a downloaded copy. Protect invitation codes and report links as confidential information.
Reports, messages, and support
Our server generates saved PDFs from completed inspection records, including property/unit context, observations, checklist answers, photos, signatures and recorded signature outcomes, timestamps, preparer attribution and, when available, profile/company branding. When a signature, decline, or reason for no signature is added after completion, the report is generated again and saved as a new version. Completed evidence and saved report versions are not rewritten by later profile edits. Users with access can export reports and choose where to save or share them. Sending to an owner uses the property's linked owner and reviewed email address.
Resend processes invitation, inspection-completion, owner-report, signing-request, signed-report and report-copy, founding-offer reminder, and account authentication emails, including one-time verification codes, recipient details, message content, access links, and delivery metadata. Completion emails go to eligible company owners/admins. The staff member who sent a signing request is emailed when the tenant signs or declines. Founding customers are emailed a reminder about a week before their complimentary access ends. When someone creates an account on their own, rather than joining a company through an invitation, FieldSeen’s founder is emailed that account’s name, email address, sign-in method, workspace, founding-customer status, and any campaign tags recorded with a founding claim, so he can welcome and help set up new customers. Provider acceptance means the email provider accepted a message; it does not confirm inbox delivery. FieldSeen does not currently offer push or local notification alerts or an email-notification preference center.
The website walkthrough form sends the name, email address, unit range, and optional company name and note you enter to FieldSeen. It also records the page you submitted from and, when present in the page address, campaign parameters such as utm_source, utm_medium, utm_campaign, utm_term, and utm_content, so we can tell which campaign or listing led to the request. If you arrived from a FieldSeen Google ad, it also records the Google Ads click identifier (gclid, gbraid, or wbraid) that Google added to the page address, and when that visit happened. When you arrive through a campaign link or ad, the website keeps these parameters in your browser’s local storage for up to 90 days so a request you submit on a later visit can still be linked to it; a newer campaign visit replaces them, and nothing is saved for visits without campaign parameters. We use these details to reply to you, arrange and prepare a walkthrough, and understand which marketing channels and ads lead to requests. When a request is saved, the website also tells Google Ads that a walkthrough request was made, as described under “Device storage, logs, cookies, and tracking.” Your name, email address, company, unit range, and note are not sent to Google. The request is stored in our Supabase database and a notification containing it is sent to support@fieldseen.com through Resend. Submitting the form does not create an account or confirm a booking. Support and privacy requests contain the contact details, message, attachments, and diagnostics you choose to send, and are available to people handling the request and their email providers. Do not send passwords, invitation codes, private report links, or unnecessary tenant information. Sync diagnostics can be viewed and copied on-device; there is no automatic upload of that debug report.
FieldSeen is currently operated by its founder, who personally monitors support@fieldseen.com and handles support and privacy requests. Messages and attachments you send are processed through the email service used for that mailbox.
FieldSeen does not send promotional email campaigns to account holders, tenants, owners recorded in a workspace, or report recipients. Account, invitation, inspection-completion, signature, report-delivery, founding-offer reminder, and support messages serve the operational purposes described above. FieldSeen may email property managers, landlords, and other rental businesses that are not customers to introduce the Service. For this we use business contact details, such as a company name, contact name, role, business email address, and location, gathered from publicly available sources such as company websites and business listings, and we record which messages were sent, when a reply arrived, and a short excerpt of the reply. These emails are sent from FieldSeen’s own Google mailbox, not through Resend. Each one identifies FieldSeen as the sender, carries our mailing address, and says how to opt out: reply “stop” and we will not email that address again. We keep a do-not-contact record so that an opted-out or bounced address is not emailed again, and you can ask support@fieldseen.com to stop or to remove your other details at any time. We do not use information that customers store in FieldSeen, such as tenant or owner contacts, for this outreach. If we introduce promotional emails to account holders, we will explain the relevant use of contact information and provide a way to unsubscribe from marketing. A marketing unsubscribe will not by itself cancel an account or stop necessary service communications.
Service providers and other sharing
Supabase supplies authentication and authentication emails, databases, private file storage, and server functions. It receives account, company, contact, property, inspection, report, operational, and security data. The current database project is hosted in the United States (AWS us-west-2). Supabase Auth sends authentication emails (account confirmation, password reset, and one-time verification codes) through Resend.
Vercel hosts the public website and web app and provides the website analytics described below. Mapbox and OpenFreeMap serve mapping requests; OpenStreetMap is the map-data source, rather than a separate FieldSeen account provider. Their delivery infrastructure may include other providers, including Cloudflare. Google processes optional Google sign-in and, through Google Workspace, the mailbox FieldSeen uses for outreach email, and Google Ads provides the conversion measurement on the public website described below. Apple processes optional Sign in with Apple and, if you choose Hide My Email, relays our emails to you. Stripe processes subscription payments, invoices, refunds, and sales-tax calculation for paid plans. Apple processes iOS distribution and any App Store/TestFlight information you provide under Apple's terms. Where the Android app is offered through Google Play, Google processes that distribution and any Google Play information you provide under Google's terms. Native Capacitor plugins provide device functions; installing a plugin does not itself create a separate cloud copy of your inspection data.
These providers and their subprocessors may process information in the United States and other countries, including through global delivery infrastructure and support operations. Their applicable notices and service agreements govern their processing. We do not promise that all information stays in one country or that all providers have identical retention periods.
Workspace members and report recipients receive information as described above. Authorized FieldSeen personnel and service providers may access information to operate the service, address support requests, or investigate problems. We may also disclose information where required by law or reasonably necessary to address fraud, misuse, or threats to people or the service. Any proposed business transfer involving personal information requires appropriate notice and compliance with applicable obligations.
Device storage, logs, cookies, and tracking
FieldSeen uses browser/WebView local storage for authentication persistence, an installation identifier used in offline synchronization, recovery state, and deletion-retry markers. The installation identifier is not an advertising identifier and can remain after signout. Web company-invitation continuation, tenant links, and report links use per-tab session storage. In the iPhone and Android apps, company-invitation continuation uses app-origin local storage with a fixed seven-day validity window so it can survive app termination; acceptance, explicit exit, and ordinary signout clear it. Local-storage records are not the encrypted inspection database.
The app also keeps a small profile display cache in local storage containing your account identifier, display name, a reduced profile-photo image, its version, a freshness time, and a cache coordination marker. It does not contain your email, phone number, password, roles, or signed photo URLs. The app rejects snapshots older than seven days when restoring this cache and attempts to clear it on signout, account changes, and confirmed deletion. This is not a timer that remotely erases an unopened device or its backups. Owner and team directory caches, including teammate photo URLs, are held in the signed-in app’s memory rather than this profile record.
Property metadata snapshots in IndexedDB can be displayed for up to 24 hours; this is a freshness limit, not a guarantee that bytes disappear at 24 hours. Photos and signed URLs also use temporary memory and browser-controlled caches. Browser and operating-system storage can retain files after FieldSeen stops displaying them.
Staff offline inspections use IndexedDB in the browser and an encrypted SQLite database with app-private prepared-photo files in the iPhone and Android apps. Accountless tenant drafts use a separate invitation-scoped IndexedDB store, including on supported WebView surfaces. Offline data includes property context, notes, observations, checklist answers, photos, signatures captured before completion, timestamps, checkout identifiers, pending operations, and limited error history. Browser IndexedDB is not application-encrypted.
Our hosting, authentication, mapping, and email providers may process request IP addresses, user-agent/device information, request times, errors, and delivery/security logs. FieldSeen also stores operational records such as invitation events, report access, sync replay information, and ownership/deletion receipts. Company activity views summarize inspection records; they are not a complete security audit log.
The FieldSeen iPhone, Android, and web apps do not integrate advertising, advertising identifiers, cross-app tracking, analytics SDKs, or a crash-reporting SDK. The public website at fieldseen.app uses Vercel Web Analytics to measure how the site is used: pages viewed, the referring site, campaign parameters in the page address, general device, browser, operating system, and country information, and named website events such as selecting Start free, opening the sample report, or submitting a walkthrough request. Vercel Web Analytics does not use cookies; Vercel derives a short-lived, hashed visitor value from request information to count visits, and FieldSeen sees aggregated reports rather than a profile of an identified person. The website also records campaign parameters and Google Ads click identifiers from the page address and keeps them in local storage for up to 90 days, to link a walkthrough request to the campaign or ad that led to it, as described under “Reports, messages, and support.” The public website at fieldseen.app also loads the Google tag for Google Ads conversion measurement, so we can see which ads lead to walkthrough requests. The tag sends Google the page address, the referring page, your IP address, and browser and device information, and, when a walkthrough request is saved, a conversion event that contains no form details. Google sets its own first-party cookies on fieldseen.app (for example _gcl_au and _gcl_aw) that remember an ad click for up to 90 days. We turn off ad personalization signals for this tag and do not use it for remarketing or to build advertising audiences. The tag is not used in the FieldSeen apps, and it does not load when your browser sends a Global Privacy Control signal; you can also block it with your browser’s cookie or content-blocking settings, which does not affect the form. Google processes this data under its own terms and privacy policy. FieldSeen does not implement a sale of personal data or targeted-advertising workflow. If we add remarketing or advertising audiences, or send customer details such as email addresses to an advertising platform, we will update this policy before doing so. Apart from the Google tag described here, we use browser storage for the functions described in this policy, not advertising cookies. Hosting, sign-in, or payment providers may use their own necessary cookies and technical logs, including on Stripe-hosted checkout and billing pages. Provider-level email measurement and operational processing are distinct from app advertising; see provider notices and contact us with questions. Blocking storage can prevent sign-in, invitation continuation, and offline saving.
When you select a founding customer program link on the public website after arriving from a campaign link or a FieldSeen Google ad, the link carries those campaign parameters, the Google Ads click identifier (gclid, gbraid, or wbraid), the time of that visit, and the page you landed on to the FieldSeen web app. The web app removes them from the page address, keeps them in your browser’s local storage for up to 14 days while you sign up, and records them once with your founding claim. We use them to see which campaigns and ads lead to founding signups. For a signup with a gclid, authorized FieldSeen administration uploads that click identifier, the name of the conversion, and the time of your signup to Google Ads so the signup is counted as a conversion for that ad click. Your name, email address, and workspace details are not sent to Google. The recorded campaign details are kept with your founding claim and are deleted with it.
The FieldSeen apps do not change their data-handling behavior in response to a browser Do Not Track signal and do not implement a separate Global Privacy Control signal handler. The public website does not load the Google Ads tag when a Global Privacy Control signal is present. The absence of these handlers does not permit selling information or using it for targeted advertising; no such FieldSeen workflow is currently implemented. Mapping, hosting, sign-in, and email providers receive the requests described in this policy and may associate technical information across their own services as described in their notices. Apart from the Google Ads conversion measurement on the public website described above, FieldSeen does not embed an advertising network, and it does not use one to track your activity across unrelated websites.
Retention and deletion
Uncompleted inspection drafts expire 30 days after they begin. Server jobs remove expired drafts and queue private evidence for cleanup. Storage deletion is asynchronous and can require retries. This deadline does not erase data from an offline device at that moment. Tenant links can expire before the associated draft's deadline.
Founding setup files are deleted 30 days after upload, and sooner when the account or workspace that attached them is deleted. Abandoned uploads are removed after a day. Deletion is asynchronous and can require retries; links issued earlier stop working once the file is deleted. The setup request itself, the founder’s notification email, and the properties created from the list follow the lifecycles described elsewhere in this policy.
Property, owner/entity, completed inspection, and report records do not have a general automatic deletion deadline. Archiving hides or changes the visibility of records; it does not delete them. Completed inspections and saved PDFs are preserved as historical records. Editing or deleting a contact does not rewrite old attribution snapshots or report bytes. Contact us about access, correction, export, or deletion that the interface does not provide.
Checklist answers, signature entries, signature images, and recorded reasons for no signature are part of the completed inspection and are kept with it. Signing requests and the delivery records for signing and report-copy emails are deleted when the inspection is deleted. Editing or deleting a tenant contact, or deleting the account of the person who signed or recorded an entry, does not change the name printed on a recorded signature. Changing or deleting a workspace checklist does not change an inspection already started with it. Member-removal records are kept until the company is deleted.
Signout clears the account's portfolio cache and session state on that client, but preserves unsynchronized inspection drafts and evidence so work is not lost. It does not delete cloud records, clear every browser/OS cache, or remove data from other devices. Local inspection cleanup follows server-confirmed completion or deletion. Failed cleanup can leave data for a retry. Protect devices used for inspections; clearing app/browser data or uninstalling may destroy work that has not synchronized.
Account deletion removes your sign-in identity, personal profile, personal-workspace records, and your membership. A company with only you as a member is deleted with its records. A company owner with teammates must first transfer ownership to another eligible current member. Shared company records, photos, inspections, reports, contacts, and historical preparer attribution remain for that company when an individual leaves or deletes their account. Transferring ownership changes administrative authority, not historical authorship. Before deleting anything, account deletion cancels any subscription for your personal workspace and for companies in which you are the only member, closes open checkout pages, and voids unpaid invoices; if that cannot be confirmed with Stripe, the deletion does not proceed.
Account/database deletion and file cleanup are separate steps. Private storage objects are queued for removal, and the requesting client retries local account-data and temporary-PDF cleanup after confirmed deletion. An interrupted request may require status resolution before cleanup. Other devices, guest invitation stores, provider backups/logs, and recipient-held copies are not remotely erased by this local cleanup. Reopen affected devices or contact support if cleanup remains unresolved; do not assume signout or a server response wiped every copy.
Native PDF sharing downloads a temporary app-cache file. FieldSeen attempts to remove it after sharing, cancellation, or failure and retries leftovers on the next share; confirmed account-deletion cleanup also attempts removal. Interruption or failure can leave a file until later cleanup or OS eviction. Saved exports, original library photos, email attachments, delivered messages, and copies held by recipients or chosen sharing destinations remain under their control. We cannot retract them by expiring a link or deleting an account.
Operational invitation, delivery, replay, ownership-transfer, and deletion-receipt records have separate lifecycles; some replay-prevention receipts currently have no automatic expiry. Support correspondence and provider logs or backups can remain after active-record deletion. There is no single verified deletion period covering those systems. Retention depends on the applicable system, service settings, operational needs, and legal obligations; contact us for a request concerning a particular record. FieldSeen is not a substitute for your own required record-retention or backup process.
Profile display caches, verification records, import history, and access-administration history have the separate lifecycles described above. Some operational records remain until the relevant account or workspace is deleted; others are retained to resolve retries or prevent repeated actions. Preserving an inspection’s history is not, by itself, a blanket exception to applicable deletion or correction rights. We assess requests concerning retained company records, historical attribution, support copies, and operational records under the applicable obligations and the rights of affected parties.
Website walkthrough requests are kept while we respond to them and manage any resulting customer relationship, and for a reasonable period afterward for business records. You can ask support@fieldseen.com to delete a request you submitted. Website analytics are held by Vercel in aggregated form under Vercel's retention settings.
Security
FieldSeen uses access controls, private storage buckets, authorized server operations, encrypted network transport, and expiring file URLs. Native staff inspection storage is configured for encryption and prepared photos use an app-private directory that is excluded from cloud backup. These controls do not establish that every cache or device backup is encrypted or excluded from backup. No system guarantees against unauthorized access, loss, or delayed cleanup.
Your choices and rights
You can update supported profile fields, decline optional permissions, review recipients before sharing, export available PDFs, and start a supported account-deletion request in Profile → Account details. Deletion requires identity verification; if your sign-in method cannot complete that verification, or you cannot access your account, contact support@fieldseen.com. Sign-in is not required to read this policy or contact support@fieldseen.com for access, correction, export, or deletion assistance. There is no self-service full-account data export.
If a company supplied or controls your records, contact that company about its inspection and retention decisions; you may also contact FieldSeen. Tenant participants and recorded owner/tenant contacts do not need a FieldSeen account to make a privacy request. Tell us the request and enough context to identify the relevant records, without sending passwords or access links. We may verify identity and authority, and coordinate with the responsible company. Applicable rights and exceptions depend on your location and circumstances; we do not promise that deleting a login also deletes company-controlled evidence.
Depending on applicable law, you may also have rights to object to or restrict certain processing, withdraw consent for processing based on consent, use an authorized agent, or appeal a denied request. Contact support@fieldseen.com and describe the right or concern; an appeal may be sent to the same address with “Privacy appeal” in the subject. We will handle requests within the time required by applicable law and explain a denial or applicable extension. We will not unlawfully discriminate against you for exercising a privacy right. You may also raise a complaint with the privacy or consumer-protection authority responsible for your location. Turning off a device permission stops future access through that permission but does not automatically delete information already submitted.
Eligibility, changes, and contact
FieldSeen is a business property-inspection service and is not directed to children under 13. If you believe a child has provided personal information, contact support@fieldseen.com so we can review and delete it as appropriate.
We may update this policy as FieldSeen changes. We will update the effective date and provide additional notice or seek consent where required by applicable law. Privacy questions and requests can be sent to support@fieldseen.com.