GearDomain Privacy Policy
Who we are
GearDomain is operated by Fabian Pourmand (the operator). The GearDomain service for film crews consists of the iOS and Android apps (not yet publicly released), the web app at app.geardomain.app and this website. Contact support@geardomain.app about this policy or your information.
Organizations decide what inventory and crew information they enter and who may access it. If an organization entered your information, you may contact it or ask us for help.
Account and inventory information
We store your email, display name, account credentials, organization and membership role. We store the inventory information your organization enters, including equipment names, models, serial numbers, purchase details, notes, photos, kits and label identifiers. Checkout records can include borrower names, projects, dates, returns and condition notes, as well as signatures and condition photos taken at check-out and check-in. Signatures and condition photos are visible to members of the organization and can be redacted on request.
We use these records to run accounts, share inventory within an organization, track checkouts, associate labels with equipment and generate label sheets and inventory reports. Borrowers named in these records may not have GearDomain accounts. Enter only information you have authority to use.
When an organization's owner or admin creates an invite, GearDomain can email the invite link; if no email goes out, the app tells them to send the link themselves, including when the address previously bounced or the daily email limit is reached.
When you create an account with an email address and a password, we send one confirmation mail to that address with a link that works for 24 hours; the app can send it again, at most four times a day for one account. You can use the account during those 24 hours; after that, signing in asks you to confirm the address first and sends a fresh link. An account whose address is never confirmed, and that has no other members, no linked Google or Apple sign-in and no paid plan, is deleted 7 days after that period, together with the organization it created. If someone else created an account with your address, you can ignore the mail; once that account's 24 hours are over, signing in with your Google or Apple account for that address replaces it.
If you are an owner or admin of an organization, GearDomain emails you a short summary each morning at 7:00 in the organization's time zone when gear is due back that day, overdue, due for service or low in stock. It names the items and the people holding them, and it is not sent when there is nothing to report. You can turn it off for yourself in Profile.
GearDomain's operator can see account and usage information for every organization: the organization's name, its members' names, email addresses and roles, sign-up dates, the date of the organization's latest activity, and counts of its members, items and photos. We use this to run and support the service. The administrative page we use for this does not display the inventory an organization enters, its photos, its checkout records or its signatures.
The apps also keep local information needed for sign-in, preferences and offline inventory work. Changes made offline reach the server when synchronization succeeds.
Finders without accounts
You do not need an account to submit a report through a found-item page for a recognized label. The current form requires a phone number or email address. Your name, message and typed location are optional. We save the submitted details with the item, organization, label code, submission identifier and time so the organization can handle the report. Contact details are unverified and are not displayed on the public page.
When a report arrives, we email a notice to the organization's notification address or, if it has not set one, to its owner's account email. The notice contains a link to the item and never contains your name, contact details or typed location; and does not include your message.
For abuse prevention and rate limiting, we derive a salted hash from your IP address using the server's FINDER_IP_HASH_SALT. Finder reports store that hash rather than the raw IP address. A hash is still an identifier; it is not a promise of anonymity. Hosting services receive network information when handling a request. The form does not request GPS location.
Submitting a report does not change an item's checkout or confirm that the organization has read or answered it.
Requesters without accounts
When you submit through a request link, we collect your name and phone number or email, the project name and note you choose to provide, selected gear, requested dates and submission information. Salted IP hashes help limit abuse.
Phone numbers and email addresses are kept separately in request_contacts. Only the organization's owners and admins can read that contact field through the staff service; it is not included in ordinary sync data or request events. Other authorized members can see request information such as your name, project, dates and gear to arrange handover. Your name and project may become part of the checkout record.
The request status link lets its holder view request progress and, when permitted, cancel the request. Keep it private. GearDomain does not process rental payments through request links.
Intake text and image processing
Talk to Inventory is a text box. You can type into it or use your phone keyboard's own dictation. The GearDomain app does not record audio and does not request microphone access. Keyboard dictation is a feature of the keyboard provider, not of GearDomain; it follows the device provider's settings and processing practices and does not necessarily keep all processing on the device.
The text you submit is read by GearDomain's own server with rule-based parsing and a match against your organization's own gear catalog, to suggest equipment details for your review. We do not send this text, audio or inventory information to any AI text provider. Items you import become inventory records. This feature is optional.
Reading a photo of a gear list happens on your device. The web app reads the photo in your browser with a text reader served from GearDomain's own site, the iPhone app uses Apple's on-device text recognition, and the Android app uses Google's ML Kit text recognition on the phone. The photo and the text read from it are not uploaded; only the items you choose to import are saved. On Android, Google's on-device text and code reader, which the label scanner also uses, sends Google performance and diagnostic data such as the device model, app version, timing and errors, never photos or the text read from them.
Public pages and private downloads
When public contact is disabled, the found page says only that the item is registered on GearDomain and names no organization or item; when it is enabled, it shows the organization name, item name, category and, if applicable, that it is on a job. The current page uses a placeholder instead of an item photo. It does not publish serial numbers, prices, borrower details, project names or finder submissions.
Request links expose the gear selected for sharing and the availability information the organization enables. A shared link is intended to be accessible to anyone who has it.
Photos, label PDFs and generated reports use private storage and temporary signed download URLs. Anyone who obtains a valid signed URL may be able to download its file until the URL expires. Treat these URLs and downloaded reports as private; expiry does not remove copies already downloaded or printed.
Providers and data location
GearDomain runs in production on the following providers, except Apple and Google, whose role begins once the apps are released:
| Provider | Role and information handled | Location |
|---|---|---|
| Supabase | Postgres account, organization, inventory, checkout, signature, finder and request records; private storage for equipment and condition photos, label PDFs and generated reports | US West (Oregon) |
| Render | Delivery of the website and the web app, and running of the API and public pages: the application server, which processes authenticated operations, public forms, reports and intake text parsing | US West (Oregon) |
| Apple and Google | App distribution, from when the apps are publicly released, and device/platform services, under their own applicable privacy terms | As set out in their own privacy terms |
| Resend | Sending of transactional email from no-reply@geardomain.app (team invites, finder-report notices and daily summaries; no marketing email): the recipient's email address and the message content. When Resend reports that an address bounced or complained, GearDomain keeps a one-way hash of that address so that it stops emailing it; the address itself is not stored in that list. | United States |
| Stripe | Payments for paid plans through Stripe Checkout and the Stripe Customer Portal: name, email, payment details, plan and organization identifier | Where this data is held is set out in Stripe's own privacy policy |
| Backblaze | Encrypted nightly backup copies of the database and of equipment photos, readable only with a key the operator keeps offline. Database copies are removed after about 9 days; a deleted photo's backup copy is removed about 38 days after the deletion | US West (us-west-004) |
Requests to Render and Supabase pass through those providers' own delivery networks, which can handle them outside US West. Independent backups are stored encrypted at Backblaze, as the table says. Apple and Google are platform providers and are not necessarily our sub-processors for all their activities.
Stripe is our payment provider for paid plans. When you buy or manage a plan, Stripe receives your name, your email address, an identifier of your organization and the plan you choose, and the payment details you enter on Stripe's own pages: a card, or another payment method Stripe offers, such as Apple Pay, Google Pay, Link or PayPal. When Stripe asks for it, Stripe also receives your billing address. GearDomain never receives your full card number or security code, and does not keep your payment details or your billing address. We keep the organization's plan, its billing status, the end of its current billing period and Stripe's references for the customer and the subscription. When an organization on a paid plan changes owner, we give Stripe the new owner's name and email address so that receipts reach them. Stripe handles this information under its own privacy policy: stripe.com/privacy.
Cookies and browser storage
The reviewed application code does not set advertising, tracking or session cookies. It does use browser storage: the web app keeps its sign-in token in localStorage, which can survive closing the browser, and removes it on sign-out. While you use the web app, changes you make that have not reached our server yet are also kept in that browser's localStorage, so that reloading or closing the page does not lose them. They can include item details and notes, borrower, requester and project names, and the signer's name and signature drawing from a check-out or return; photos are not kept this way. These changes stay in that browser, also after you sign out, until they are sent the next time you sign in there, are discarded, another account signs in in that browser, or the account is deleted; anyone who can use that browser profile can read them, so sync or discard them before you sign out on a shared computer. When you ask the web app to delete your account, it also keeps a proof of that request in localStorage; see Retention for what it contains and when it is removed. The found page uses sessionStorage for a submission-receipt timestamp, not the submitted form contents. Unsent finder form contents stay in page memory.
This is therefore not a session-storage-only web app. Browser storage is distinct from cookies. The request-link design proposes remembering requester details, but the reviewed request-page implementation does not implement that behavior.
Retention
Inventory records, checkout history, labels and photos remain while retained by the account or organization. Signatures and condition photos are retained with the checkout record and can be redacted on request. Deleting an item can mark records as deleted for synchronization rather than immediately erase every database row. Photos marked deleted are scheduled for permanent cleanup after 30 days; abandoned photo uploads after 24 hours.
When you ask the app to delete your account, it keeps a proof of that request on the device until it learns the outcome or removes the proof as described below. The proof is the sign-in token the app sent with the request; the token names your user ID, email address, organization ID and role, when you last signed in with your password, and when the token was issued and expires. On a phone the proof is kept in the device's secure store; in the web app it is kept in that browser's localStorage. The app removes it when the server confirms the deletion and the app has removed that account's data from the device; when the server answers that the account still exists, refuses the request, or you sign in to that account again on that device; or when the server does not accept the token as a valid sign-in token of its own. The app checks on the request when it starts and, while no one is signed in, when it regains a connection; while another account is signed in on that device, it does not ask the server. A proof still kept 180 days after the request is removed at the next check without being sent, and the app then no longer asks the server whether that deletion went through. When the proof is removed without an answer from the server, a short record of the request (your user ID and its time) stays on the device.
Generated label PDFs and inventory reports are scheduled for deletion after 24 hours by the hourly cleanup process. Their download URLs also expire. Actual removal occurs on a successful cleanup run. This rule covers generated report files, not finder reports or the underlying inventory records.
Requester phone or email records are purged after 90 days from request closure. If a request never closes, cleanup uses 90 days after its requested end time. This deletes the separate contact record, not the requester name, project, note, IP hash, request history or resulting checkout records. Those require separate retention and deletion handling.
Finder-report IP hashes are scheduled for erasure 24 hours after submission. Complete finder reports, including contact details, messages, typed locations and record metadata, are scheduled for deletion 90 days after submission. Hourly cleanup normally completes each action within one further hour; failures or backlog can delay completion. A specific legal preservation requirement may delay deletion of the affected data. Request earlier deletion at support@geardomain.app. The same review is needed for remaining request records, operational logs and support correspondence; no fixed deletion deadline for them is represented here. Encrypted backups run every night. Deleted photos leave the backup copies after the backup retention period, about 38 days.
Access, export, correction and deletion
an account can be deleted in the app (Crew tab > your name under You > Delete account); organizations the user alone owned are deleted with their gear, photos and records; organizations shared with others keep their custody records, signatures, checkout names and maintenance history as the organization's business records, with the user's reservation requester name replaced by Former member; the user's email and login are removed at once. If the app could not learn the outcome of your deletion request, it asks our server later, as described under Retention. When the server answers that the account still exists, the app signs you back in on that device; if the sign-in token in the proof of the request has expired, it instead tells you that the account was not deleted, showing the email address with its local part masked: the first character, then ***, then @ and the domain (a one-character local part shows as *).
Deleting your account at once cancels the paid plan of any organization deleted with it; the period already paid is not refunded. The billing record Stripe holds for you (the customer record, any saved card and past invoices) stays with Stripe under its own retention rules. Email support@geardomain.app to have a saved card removed.
Authorized organization members can export inventory through the inventory/insurance report in PDF or CSV. It contains the report's equipment fields; it is not an export of every account, finder, request or checkout record. Contact support@geardomain.app for access to other personal information, corrections or deletion, including if you are a finder, requester or borrower without an account.
We may need to verify your identity and coordinate with the organization responsible for a shared record. Removing a member or uninstalling the app does not by itself erase the organization's inventory. Applicable privacy rights and lawful exceptions still apply. Ask us about any information that cannot be deleted and why.
Children
GearDomain is intended for people aged 13 and over, including people submitting finder reports or gear requests without an account. In countries where the digital consent age is higher than 13, a person under that age needs a parent's or guardian's permission to use GearDomain. If you believe someone under 13 has provided personal information, contact support@geardomain.app so we can investigate and arrange deletion where appropriate.
Changes and contact
We will update the effective date when this policy changes and provide notice of material changes before they take effect. Privacy questions and requests go to the operator, Fabian Pourmand, at support@geardomain.app.
Changes on 2026-10-16: this policy names the operator; states the providers GearDomain runs on today and their locations in place of the earlier hosting plan, including that requests can pass through those providers' delivery networks outside US West; notes that the apps are not yet publicly released and that payments run in Stripe's test mode; states that no independent backup runs yet; and every copy of this policy now includes the Stripe paragraphs already shown on the website. It also names Resend, which sends GearDomain's two kinds of email: team invites and finder-report notices to organizations.
Changes on 2026-10-23: new accounts made with a password confirm their email address. The account section describes the confirmation mail, the 24-hour period, the resend limit and the deletion of unconfirmed accounts 7 days after it.
Changes on 2026-10-22: payments for paid plans are live. Stripe now takes real payments for them through Stripe Checkout, and plans are managed in the Stripe Customer Portal; the Stripe entry in the providers table says so. Later the same day: nightly encrypted backups to Backblaze (US West) began; the providers table names Backblaze and the retention of the copies, and the sentence saying no independent backup runs is gone. Also on 2026-10-22: the website and the web app moved from Vercel to Render, which already ran the application server; the providers table no longer lists Vercel, and the Render entry covers the delivery of both.
Changes on 2026-11-03: owners and admins can get a daily summary email of what is due back, overdue, due for service or low in stock, with a switch in Profile to turn it off; the account section describes it and the Resend entry in the providers table names it.
Changes on 2026-11-13: the intake section describes reading a photo of a gear list on the device (in the browser, with Apple's text recognition on iPhone and Google's ML Kit on Android) and the performance data Google's on-device reader sends on Android.