Privacy Policy
Last updated: October 18, 2026
This Privacy Policy explains what personal data T21 Film Studio LLC ("FIXER", "we", "us") collects when you use FIXER, why, who receives it, how long we keep it and what rights you have. It applies to all FIXER services: the web app at app.fixer-app.com (including FIXER Go and FIXER Workspace where we have opened them), the website fixer-app.com, the FIXER iOS and Android apps, FIXER Premiere (premiere.fixer-app.com and fixer-premiere.com), our APIs, e-mails and support (the "Services").
Controller: T21 Film Studio LLC, 100 Infinity Way, Mountain View, CA 94043, USA. Contact for privacy questions and requests: hq@fixer-app.com (subject "Privacy").
1. Summary
- We collect what you give us (account, profile, work, messages, deals, verification documents), what your device sends us (IP address, device and app data) and what partners send us (Stripe, Google sign-in, Apple and Google stores).
- We use it to run FIXER: your profile, search and matching, messaging, deals and payments, verification, safety and moderation, and support.
- We do not sell your personal data and we do not use it for targeted advertising. There are no advertising or analytics trackers in the FIXER web app (app.fixer-app.com) or on FIXER Premiere. Our marketing website fixer-app.com runs on our own servers and sets no cookies and no analytics. Only the old Premiere website fixer-premiere.com, which we are retiring, is still hosted by Wix, which sets its own cookies there (see the Cookie Policy).
- Some features use AI services from Google (and OpenAI, when we switch a feature to it), and video moderation uses Amazon Web Services. They process data for us to provide those features; Amazon Web Services may also use videos checked for moderation to improve its AI services (see section 4.2).
- You can see and edit your data in your profile, delete your account in Settings, and write to us for a copy of your data or any other request.
2. Data we collect
2.1 Data you give us
| Data | Examples | Where | |
|---|---|---|---|
| Account | name, surname, nickname, e-mail, password (stored only as a secure hash), account type (person or company), city, professions | sign-up, settings | |
| Profile and work | photo, banner, show reel, drops (short videos and photos), works and links (YouTube, Vimeo and others), experience, journal posts, "about me", day rate, availability and busy dates, social links, AI content labels you choose | profile | |
| Company | company name, type, banner and videos, business e-mail and domain, team members' names, roles and work e-mails, team audit log | company settings, teams | |
| Messages and activity | chat messages and attachments, comments, likes and reactions, favorites and folders, recommendations, network ties, searches, bulletin-board posts and the posts you share with others, job alerts and saved deals, BrainMatch phrases, Assistant requests, complaints and reports, support requests | when you use these features | |
| Deals and contracts | deals you post, applications, contract terms, prices, FIXER service fees and payouts, deadlines, the parties' names and mailing addresses (shown to the other party in the contract), drawn signatures (as an image), delivered files, dispute messages and evidence | deals | |
| Verification | phone number; a card check; photo of your ID document (passport, national ID or driving license) and a selfie holding it — or, when the check runs through Stripe Identity, only the result of Stripe's check (see 4) | verification | |
| Payout accounts (talent, FIXER Go runners) | legal name, date of birth, address, phone, e-mail, tax or social security number, bank account, ID document — you enter them on Stripe's own onboarding pages for the Stripe payout account used for payouts (see 4.2); FIXER does not receive them. We keep only the Stripe account ID and read its status and the last 4 digits of the bank account from Stripe | ||
| FIXER Go — runners (available in the open markets, only after FIXER approves your documents) | date of birth (checked once for 21+ and not stored; we keep only the confirmation), service area (rounded) and run filters, availability, vehicles (make, model, year, colour, class, photo, plate — stored encrypted, last 3 characters shown), documents you upload (driving license, vehicle registration, driving record, business registration and licenses, insurance certificates and policies with issuer, limit and expiry, motor carrier permit, workers' compensation; if FIXER Go opens in Ukraine, which it has not, also the ЄДР extract and ОСЦПВ and cargo policies) with their numbers stored encrypted, references (name, production, role, contact stored encrypted), U.S. work-authorization confirmation (no documents), acceptance of the Runner Agreement, declared trips ("On your way": start, end and times, stored encrypted), runs you took, your position and its reported accuracy when you tap "I'm here" or "Nobody at pickup", messages, counter-offers, photos you take at pickup and drop-off (we remove location and other metadata from them), your "Available now" status and until-time, the offers sent to you and your answers (passing never counts against you), and runs you stepped back from late or did not start by the end of the pickup window (used only to order who is offered a run first) | FIXER Go runner pass, runs | |
| FIXER Go — productions (available in the open markets, only after full verification) | runs you post (items, declared value, price, times, vehicle), stop addresses and map points, saved places, names and phone numbers of contacts at stops (phone numbers stored encrypted), access notes (stored encrypted), the receiver's name and the handoff code (we keep only a one-way code of it), your production insurance policies (file, issuer, limit, expiry), messages, reported problems; for jobs in the Los Angeles and San Francisco Bay Area pilot also the job description and the job kind, the prepaid order reference, your trusted runners, and the rental house, release confirmations (who confirmed, when, for which booked runner) and return check-in | FIXER Go | |
| Workspace | videos and photos you upload (we do not change or read their contents, so any location or camera data inside a file stays in it), titles, descriptions, filming dates, covers, albums, tags, highlights, and when you last opened an album | FIXER Workspace | |
| Calendar feed | a one-way hash of your private calendar link, when it was created and last fetched | Settings → Calendar | payout setup |
| Premiere | e-mail and payment status of your ticket or donation, and your name if you give it with a donation; your confirmation that you are 18+ and, before you first watch, that streaming starts now; name, e-mail, film details and message in the filmmaker form; e-mail for news | premiere.fixer-app.com | |
| Imports | links and files you give us to fill your profile, and an Instagram data export if you choose one (only posts and reels are read in your browser; your direct messages are never read) | profile import / AI fill | |
| Account deletion | the reason you give, if any | settings |
2.2 Data collected automatically
- Technical data: IP address, browser and device type, operating system, app version, language, time of requests, and server logs used for security and troubleshooting. If you sign up without confirming an e-mail code, our server log records your e-mail's domain and browser type for fraud prevention (kept 14 days).
- Location: with your permission, the app or browser sends your device location when it opens so that we can find the nearest city. We store only the city, not your coordinates. You can refuse and choose a city yourself. In FIXER Go we store the addresses and map points you enter for run stops, saved places and trips; if you tap "use my location" there, your device's location fills that field. We do not track your location in the background. Live location during a run (opt-in): a FIXER Go runner can switch on "Share my location" for a booked run; only then, and only while the run is active, the device sends an approximate position (rounded to about 100 m, at most every 20 seconds). We keep only the latest point, show it to the production of that run to estimate the arrival, and delete it when the runner switches sharing off or when the run ends in any way (delivered, cancelled by either side, ended with "Nobody at pickup", or closed by FIXER staff). Check-in and "Nobody at pickup" positions: when a runner taps "I'm here" at the pickup or the drop-off, or ends a run with "Nobody at pickup", the app sends the device's position at that moment (only if the runner allows location) together with the accuracy the device reports; we record it in the run's step log, with the distance to the pickup point and whether it was close and accurate enough to count as confirmed. Purpose: to decide whether pickup waiting and the en-route fee may be charged automatically or need a staff review, and to let FIXER staff settle a problem reported about the run (contract; our legitimate interest in fair fees and preventing fraud). The production of the run sees the step and its time, but not the coordinates; FIXER staff who review the run see them. They are kept with the run's records (section 5). At pickup and drop-off we may also record an approximate position with the handoff step, kept the same way. Purpose: the run the runner agreed to (contract).
- Usage: views and reactions on drops and reels, profile views counts, notifications you received and whether messages were read.
- Data we derive from your content: embeddings (numeric summaries of meaning) of profiles, deals, drops, works, BrainMatch phrases and saved Assistant searches, and AI-generated descriptions and tags of what drops and works look like, used for search, matching and the Assistant; and a perceptual fingerprint of each drop and show reel video (hashes of 8 frames; no face recognition), used to find the same clip at another member and suggest that you confirm you worked together.
- Device identifiers in the mobile apps. *Version 3.0 and later of the FIXER iPhone and Android app* (the web app in an app shell) has no analytics and no advertising ID; its push token is described below, and error reports (Sentry, section 4.2) apply to it as to the web app it shows. *Older versions (before 3.0)* collect a push-notification ID (OneSignal), Firebase app instance ID, the device's advertising identifier (IDFA on iPhone, advertising ID on Android), which Google Analytics for Firebase collects where the phone makes it available (on Android by default; on iPhone with iOS 14.5 or later only if you allow tracking when the app asks) — we do not use it to show you ads — and crash reports (Sentry) that include device model, OS version and the error. You can reset or delete the advertising ID, and on iPhone turn off tracking, in your phone's settings.
- Web push on a device: if you switch on notifications in the web app (Settings → Notifications), your browser gives us a push subscription for that device: an address at your browser's push service (for example Google, Mozilla, Apple or Microsoft) and two encryption keys, and we add a label such as "Chrome on Android" made from your browser type. We use it only to send you FIXER notifications; their text is encrypted, so the push service cannot read it. If you remove a device from your list, we keep a one-way hash of its address so that it is not added back automatically.
- Push on a phone (the FIXER app): if you switch on notifications in the FIXER iPhone or Android app (Settings → Notifications), the phone's operating system gives us a device token for the app (from Apple's push notification service on iPhone, from Google's Firebase Cloud Messaging on Android). We store the platform (iPhone or Android), the token (encrypted at rest; we also keep a one-way hash of it to recognise the device), the app version and when the app last reported it, and we label the device "iPhone app" or "Android app". We use it only to send you FIXER notifications; a notification contains only its short text and the screen it opens, never your e-mail or other account data. If you remove a device from your list, we keep a one-way hash of its token so that it is not added back automatically.
- Calendar feed: if you turn on your calendar link, the calendar app that fetches it sends us its requests (with its IP address, used only for rate limits in memory, not stored) and we record when the link was last fetched.
- Browser storage: see the Cookie Policy.
2.3 Data from others
- Stripe: payment status, the last digits and brand of your card, payout account status and verification results. Stripe never gives us your full card number.
- Google (if you sign in with Google): your Google account ID, name, e-mail and profile picture link.
- Apple (if you sign in with Apple in the iPhone app): your Apple user ID, your name and either your e-mail or the private relay address Apple gives us, as you choose.
- Apple and Google stores: purchase receipts and subscription status for in-app purchases.
- Public sources you point us to: when you ask us to import your work, we read the public pages you give us (for example your website, YouTube, Vimeo, Behance, IMDb) and public information about those works. When you use AI fill we may look up a public Gravatar image linked to your e-mail (we send only a one-way hash of the e-mail).
- Document checks for FIXER Go: to check a runner's or a production's documents we may confirm them with the insurer or agent that issued them or with a public register (for example the California Secretary of State), and we record how and when we checked.
- Other users: people can mention you in a deal, recommend you, add you to a network tie or a company team, report you, or send you messages.
Providing your data is voluntary, but without the data marked as required in a form (for example your e-mail to create an account, or verification documents for deals) we cannot provide that feature. We do not intentionally collect sensitive data such as health, religion or sexual orientation. Please do not put it in your profile. ID documents and selfies that you upload to FIXER are reviewed by a person; FIXER itself does not use automated face recognition and does not create biometric templates. When the identity check runs through Stripe Identity instead, the document photo and the live selfie go directly to Stripe, not to FIXER: Stripe checks the document and compares your face in the selfie with the photo on the document automatically. That comparison is biometric processing; Stripe asks for your explicit consent in its own verification screen before it starts, and you can decline and ask us for another way to verify at hq@fixer-app.com. Section 2.4 is our notice and retention policy for it.
2.4 Biometric data: the identity check with Stripe Identity
This section is our written notice, consent and retention policy for biometric data, as required by laws such as the Illinois Biometric Information Privacy Act (BIPA). It applies when you choose "Verify with Stripe" to verify your identity. It does not apply to ID photos and selfies you upload to FIXER for a person to review: no software compares faces in those.
- What is collected. A photo of your ID document and a live selfie. To compare them, Stripe makes a scan of face geometry from the selfie and from the photo on the document (a biometric identifier), and reads the data printed on the document. This happens at Stripe, our service provider. FIXER does not receive, create or store the images, the face scans or any face template. FIXER receives and stores only the result: verified or not, document type and country, whether the name on the document matches your profile and whether you are 18 or older, plus a keyed code derived from your name, date of birth and document country (not from your face) that lets us notice one person verifying two accounts.
- Purpose. Only to confirm that you are the person on a valid ID document and that you are 18 or older, so that FIXER can mark your account as verified (deals and FIXER Go require it) and to prevent fraud and impersonation. FIXER uses the data for nothing else. FIXER does not sell, lease, trade or otherwise profit from your biometric data. How Stripe handles it is described in Stripe's own notice at stripe.com/privacy and in its verification screen.
- Your consent. Before anything is captured, Stripe's verification screen asks for your explicit written consent (you give it electronically by agreeing on that screen) to the collection and use of your biometric data for this check. If you do not agree, nothing is collected: close the screen and ask us for another way to verify at hq@fixer-app.com. You can withdraw your consent at any time by writing to the same address; we then ask Stripe to delete your data (see below), and your verification may be removed.
- Retention and destruction schedule. Stripe keeps the images, the face scans and the data read from the document in FIXER's Stripe account only until we ask Stripe to delete (redact) them, and then deletes them. We ask Stripe to delete them (1) 30 days after the final decision on your check: accepted, rejected or canceled, or, when a person reviews the check, 30 days after that person's decision, never while the review is still open; (2) when your account is erased on its deletion date (see "When you delete your account" in 5), within hours of the erasure; and (3) in any event when the purpose is satisfied or within three years of your last interaction with FIXER, whichever comes first. Once we have asked, Stripe deletes the data itself, which can take a few days. Our own result flags and the keyed code stay while your account exists (see 5).
- Who receives it. Only Stripe, as our service provider. We do not disclose your biometric data to anyone else unless you consent, a law requires it, or a valid warrant or subpoena from a court requires it.
- Security. The images go from your device directly to Stripe, over an encrypted connection, and never pass through FIXER's servers. We keep the result data with the same care as the rest of your account data, and with at least the care we use for other confidential and sensitive information.
3. How and why we use data
| Purpose | Data used | Legal basis (EU/UK) |
|---|---|---|
| Create and run your account, sign-in, security of your account | account, technical data | contract |
| Show your profile and work to others; search, feed, recommendations, BrainMatch, Assistant | profile, work, activity | contract |
| Messaging, notifications and e-mails about your activity | messages, contact data, device IDs | contract |
| Deals, contracts, payments, payouts, disputes | deals, contracts, payment data | contract; legal obligation (tax and accounting) |
| Verification of people and companies | phone, card check, ID and selfie, business e-mail | contract; legitimate interest in preventing fraud and impersonation |
| Moderation and safety: checking uploads for explicit or illegal content, spam and fraud, handling reports | content, technical data | legitimate interest in a safe platform; legal obligation |
| AI features: AI fill, import, descriptions, smart reel, Assistant, AI content labels. On the web, every drop you upload and every photo you add to a new feed post is analysed by AI automatically right after upload: it drafts the text (you can change it) and estimates whether the media looks AI-generated. That estimate never sets a label; it can only send a drop you marked "filmed" to a person for review | the content and text you submit; for search, matching, descriptions and the Assistant also other members' public profile data (see 4.2) | contract; legitimate interest in giving members relevant search results and descriptions, and in honest AI content labels |
| Improving FIXER, fixing errors (including error monitoring with Sentry), statistics | technical data, error reports, usage (in aggregated form where possible) | legitimate interest |
| Promoting FIXER with content you made public, for example showing a public profile or drop on our website or social channels (Terms, section 7) | public profile and content | legitimate interest in promoting FIXER; you can object at any time by writing to hq@fixer-app.com, and we stop using that item |
| FIXER Go: approving runners, checking documents and insurance and applying each runner's cover limit, showing runs to runners whose filters match and offering them first to the nearest and most reliable runners, refusing jobs FIXER Go does not offer, booking, confirming rental releases, proof of pickup and delivery, payments and invoices, problems and disputes, "On your way" trip matching | FIXER Go data, verification status, payment data | contract; legitimate interest in safe, correctly insured runs and in preventing fraud; legal obligation (tax and accounting) |
| FIXER Workspace: storing your files and showing them to you; calendar feed: building your calendar | Workspace data; your contracts, runs and busy dates | contract |
| FIXER Premiere tickets, access links, donations, filmmaker proposals, newsletter | Premiere data | contract; consent (newsletter) |
| Legal claims, law enforcement requests, compliance | any relevant data | legal obligation; legitimate interest |
Automated decisions. Some decisions are made by software: automated moderation may hide or remove content (for example a photo, a video, a comment or your "About me" text) automatically, and a FIXER moderator then reviews it (Terms, section 8); spam and rate-limit checks may block an action; and the feed shows content that meets objective quality rules (for example a filled profile with a profession, or a verified business). Your content stays on your profile even if it is not in the feed. AI matches, search rankings and Assistant suggestions are only suggestions: FIXER does not use them to decide who is hired or paid, and companies make their own decisions. None of these decisions has legal effects on you; you can always ask a person to review one at hq@fixer-app.com. ID documents and selfies uploaded to FIXER are checked by a person. When the identity check runs through Stripe Identity, the document and the selfie (including the face comparison) are checked automatically by Stripe; FIXER accepts the result automatically only when Stripe verified the document and the selfie, the name on the document matches your profile and you are 18 or older, and every uncertain case (for example a name that differs from your profile, a missing date of birth, or an identity that seems to be verified on another account already) is decided by a person. You can ask a person to review a failed check at hq@fixer-app.com. In FIXER Go, software applies the rules described in the Terms (section 12A) — for example a runner cannot take a run above the limit of their checked insurance, and an expired document removes that ability the same day — while a person approves runners and checks documents. The phone, card and business e-mail steps are checked automatically (an SMS code, the card check through Stripe (nothing is charged), and a code sent to an address on the company's own domain; free and disposable e-mail providers are not accepted); you can ask a person to review a failed step at hq@fixer-app.com.
Marketing. We send only service messages (for example sign-in codes, deal and contract updates, team invitations). We do not send marketing e-mails without your consent. If we start, every marketing e-mail will have an unsubscribe link.
4. Who receives your data
4.1 Other users and the public
- Your public profile (name, nickname, photo, professions, city, about text, day rate, availability and busy dates, experience, recommendations, social links, show reel, drops, works, journal, your "Verified" or "Verified business" badge and company page) is visible to FIXER users. Your public business card (app.fixer-app.com/u/your-nickname) and link previews of it can be seen by anyone, including search engines; it shows your name, nickname, photo, banner, professions, city, about text, day rate, verification badges, show reel (or smart reel), drops, works, journal, the social links you added and your company team memberships. Your account e-mail, phone number, exact location, verification documents and payment details are never shown to other users; a contact you add yourself as a link on your profile (for example an e-mail address) is public.
- Messages are seen by the people you send them to. In a company team, messages sent for the company show who sent them, and company admins see team members' names, roles and work e-mails.
- FIXER Go: before a run is booked, runners see the area, the place name and an approximate point of its stops, and a runner is shown to the production as first name and initial; after booking, the booked runner sees the exact addresses, access notes and contacts of that run, and the production sees the runner's name, vehicle and the "documents checked" facts of their runner card. Your declared trips are never shown to anyone. Before booking, a production sees how many runners are covered for a value only as a range, never who; the exception is a runner the production invites (from the moment of the invitation, whether or not the runner answers) or who sends it a counter-offer: the production then also sees that runner's insurance line (liability limit per occurrence, any cargo limit, and the month and year it is valid until), but not the insurer or the certificate. Once a production has booked a runner, that production's managers can open the runner's current general-liability insurance certificate for that run through a short-lived link, which shows the insurer, the coverage limit and the expiry date; each view is logged. Other documents and document numbers are not shown to productions.
- Workspace files and albums are visible only to you. Your calendar link shows your calendar to anyone who has the link; keep it private, and replace or turn it off in Settings if it leaks.
- Deals you post are visible to FIXER talent members looking for work, and job alerts and the Assistant can suggest them. Applications, contracts, payments and disputes are seen by the company (including team members who act for it) and the talent involved, not by other users.
4.2 Service providers (processors)
They process data only on our instructions to provide their service to us, except where the table below says otherwise:
| Provider | What for | Data |
|---|---|---|
| Stripe, Inc. (USA) | card payments, the card check (no charge), deal payments and FIXER Go payments in U.S. markets, payouts to talent and runners (Stripe Connect, with Stripe's own onboarding pages), Premiere tickets and donations | name, e-mail, card and payment data; device, browser and IP data that Stripe's script collects for fraud prevention; for payout accounts the identity, tax and bank details (including bank account numbers) listed in 2.1, and the IP address and browser from which you accepted Stripe's Connected Account Agreement. For payouts Stripe also acts as an independent controller — see stripe.com/privacy. When the identity check runs through Stripe Identity, Stripe also receives a photo of your ID document and a live selfie, checks the document and compares the selfie with its photo automatically (with your explicit consent in Stripe's screen), and keeps them in FIXER's Stripe account until we ask Stripe to delete (redact) them (see 5). FIXER stores only the result flags (verified or not, document type and country, whether the name matches your profile, whether you are 18 or older) and a one-way keyed code derived from your name, date of birth and document country that only lets us notice one person verifying two accounts; FIXER never stores the images, your date of birth or your document number. We ask Stripe to delete (redact) the images and data of your check 30 days after the final decision on it, and when your account is erased on its deletion date (details in 2.4) |
| Amazon Web Services (USA, region us-west-2) | storage and delivery of photos, videos and files (S3, CloudFront), including private storage of identity documents, FIXER Go documents and photos, and Workspace files; video moderation (Rekognition); encrypted database backups | uploaded content, backups. AWS may also store and use the videos checked by Rekognition to improve its AI services, and may store them for that purpose outside us-west-2 |
| Hostinger (servers) | hosting of our web app, APIs, database and search | all data stored in FIXER |
| Twilio Inc. (USA) | SMS codes for phone verification (Twilio Verify: Twilio sends and checks the code) | phone number, the code request and its result |
| Google (USA) | Gemini AI for AI fill, import, descriptions (run automatically on drops and new feed-post photos uploaded on the web), the AI-generated-content check, smart reel, Assistant, BrainMatch and moderation of text and photos; Google sign-in; Firebase in the mobile apps (Android push delivery and app analytics); YouTube Data API and YouTube's public video and channel pages for importing your videos. Videos you give to AI features are uploaded to Gemini's file storage for the request | the text, images, video and links you submit to those features (including your sign-up e-mail for AI fill); for search, matching, the Assistant's suggestions, descriptions and moderation also the public profile texts, names, cities, drops, work thumbnails and deals of members; sign-in data; app analytics data |
| OpenAI (USA) | alternative provider for AI features and text moderation, used only when we switch a feature to it | the text and media you submit to those features |
| OneSignal (USA) | push notifications in mobile app versions before 3.0 | push ID, notification text (which can include the sender's name and the start of a chat message) |
| Sentry (Functional Software, Inc., USA) | error monitoring: finding and fixing failures in the FIXER web app, our servers and the older mobile apps. Reports are sent only once we switch Sentry on | device or browser and operating-system type, the error and the place in our code where it happened, the page or API path, the app version, and an internal account number. Before a report leaves our systems we remove names (in the fields that hold them), e-mail addresses, phone numbers, payment and identity data, addresses, locations, IP addresses, request contents, cookies and access tokens, and cut URLs down to their path (a page path can still contain a public profile nickname). We do not use Session Replay or performance tracing. Sentry keeps reports for 30 days on our plan, then deletes them |
| Our mobile app development contractor | administers the Firebase and Sentry projects used by the versions of the mobile apps before 3.0, and can see the app analytics and crash reports there | app analytics and crash data (no messages, documents or payment data) |
| Titan / Hostinger e-mail; Google (Gmail) | sending e-mails from app@fixer-app.com and our support inbox; Premiere form submissions are delivered to our team's Gmail inbox | e-mail address, message content |
| Wix.com (Israel/USA) | hosting the old Premiere website fixer-premiere.com, which we are retiring; the trailer on premiere.fixer-app.com is still streamed from Wix's video servers | IP address, Wix cookies on fixer-premiere.com (see Wix's privacy policy) |
| Your browser's push service (for example Google, Mozilla, Apple or Microsoft) | delivering web push notifications, if you turn them on | the device's push address and the notification, encrypted so that the push service cannot read it |
| Apple (USA) and Google (USA, Firebase Cloud Messaging) | delivering push notifications to the FIXER iPhone and Android app, if you turn them on; they act as processors of the notification and as independent controllers of their own push services | the device token and the notification (its short text and the screen it opens) |
| Vimeo (USA) | playing Premiere films and embedded videos; reading public details of Vimeo videos you import | IP address, viewing data (see Cookie Policy); the links you import |
| Apple and Google (stores) | in-app purchases and subscriptions in the mobile apps | purchase data (they act as independent controllers) |
| Automattic (Gravatar) | finding a public profile image during AI fill | a one-way hash of your e-mail |
| Zapier (USA) | internal notification about new sign-ups, only if we switch it on | user ID, e-mail, sign-up date |
The AI providers receive the data described above through their business APIs.
Maps. FIXER Go address search and driving distances use OpenStreetMap-based software (Photon and OSRM) that runs on our own servers, so no map provider receives the addresses you search. The "Navigate" button opens Google Maps with the stop's address or point, under Google's terms. Map data © OpenStreetMap contributors.
Calendar apps. If you add your calendar link to Google Calendar, Outlook or another calendar app, that app receives the link and fetches your calendar under its own terms.
YouTube API Services. FIXER uses YouTube API Services. With the YouTube Data API we read publicly available information about the YouTube videos, channels and playlists whose links you give us for import or AI fill: titles, descriptions, thumbnails, durations, publication dates, channel names and channel country. We use it to prepare your work cards and your profile draft, may send it to our AI providers for those features (see the table above), and keep it with your imported items and works for the periods in section 5. We also use the YouTube embedded player to play YouTube videos on FIXER (see the Cookie Policy). We do not connect to your YouTube account or read private YouTube data. How Google handles data is described in the Google Privacy Policy; YouTube's terms are at youtube.com/t/terms.
4.3 Others
- Professional advisers (lawyers, accountants) under confidentiality.
- Authorities, when the law requires it, or to protect the rights, property or safety of users, the public or FIXER.
- A buyer or successor if FIXER is involved in a merger, acquisition or sale of assets; they must respect this Policy.
5. How long we keep data
| Data | How long |
|---|---|
| Account, profile and content | while your account is open; see "When you delete your account" below |
| Messages | while your account exists; after you delete your account, messages you sent stay in the other person's conversation and show as from "Deleted user", and the attachments you sent are removed (except in conversations about a deal that has a contract) |
| ID document photos and selfies | stored privately and visible only to the FIXER staff who review them, through links that expire after 10 minutes (each staff access is logged); after approval, kept for 30 days and then deleted (we keep only the record of the check: the type of document, the result and its date); deleted within 30 days after a rejected verification (at once if you upload a new document) and within 30 days after you delete your account |
| Contracts, payments, payouts, credits and in-app purchase records | up to 7 years after the transaction, for tax, accounting and legal claims |
| Result of a Stripe Identity check (result flags and the keyed code; no images, date of birth or document number) | kept while your account exists; removed when your account is erased, and at the same time we ask Stripe to redact the images and data of the check it holds |
| ID document photo, selfie and the personal data read from them in a Stripe Identity check (held by Stripe, not by FIXER) | deleted at Stripe 30 days after the final decision on the check: we ask Stripe to redact the check 30 days after it was accepted, rejected or canceled, or, when a person reviews the check, 30 days after that person's decision (never while the review is still open); when your account is erased on its deletion date; in any event when the purpose is satisfied or within three years of your last interaction with FIXER, whichever comes first (see 2.4) |
| Restricted record of a deleted account that took part in a contract or a payment: the name on the account, e-mail, company name, account role, identity-verification status and date and the result of each verification step (no document images or files), and the ids of those contracts and payments | 7 years after the account is erased, then deleted automatically; visible only to FIXER administrators |
| Accounts that FIXER closed for breaking our rules, fraud or abuse | kept as evidence for as long as needed for legal claims, fraud prevention and law enforcement requests; not erased automatically (ID document photos and selfies are still deleted within 30 days after the account is closed; the record of the check stays) |
| AI fill drafts that you do not confirm | 7 days |
| AI fill requests that you confirmed (your text, files, e-mail, IP address) | 30 days after confirmation; the profile you approved stays in your account |
| Imported items that you do not publish | 30 days after your last change (items read from a YouTube channel or playlist: at most 30 days after the import) |
| Saved Assistant searches | 30 days |
| FIXER Go runner documents and production insurance policies, and their files | while you use FIXER Go; a runner document you replace yourself is deleted 30 days after the replacement, and one you withdraw at once. They are deleted, with their files, when your account is erased |
| FIXER Go run records (run details, stop addresses, proof photos, offers, the step log with the check-in and "Nobody at pickup" positions, messages) | photos you took at pickup and drop-off and other run files: 180 days after the run ends; receipts: 3 years after the run ends; if a problem was reported on the run, at least 1 year after it was decided; never while a problem is still open or the law requires us to preserve them. The run details, offers, messages and the step log are kept as the record of the run for accounting and legal claims; we have no fixed deletion date for them yet, and you can ask us at hq@fixer-app.com to delete or anonymise what the law lets us; see "When you delete your account" below |
| FIXER Go declared trips | the start and end points and detours are deleted when you cancel the trip or 24 hours after its leaving window; only counts stay |
| "FIXER only connects" confirmations (the box you tick before you post, book, take, counter, hire or accept: who, for which company, which run or contract, the text version, the time, your IP address) | the record as long as the run or contract record is kept; your IP address 3 years, then removed; when your account is erased, the link to you and the IP address are removed and only the anonymous record stays |
| Workspace files | while your account is open; a file you delete is removed 7 days later, and an unfinished upload about a day after its upload link expires; everything is deleted when your account is erased |
| Calendar link | until you replace it, turn it off or your account is erased |
| Web push subscriptions (push service address and encryption keys per device, device label) | until you switch notifications off on that device, remove the device from your list or sign out on it, the push service tells us the subscription no longer exists (or delivery fails 5 times in a row), or your account is erased; the hash of a removed device's address: 30 days |
| App push device tokens (platform, encrypted token and its hash, app version, when last seen) | until you switch notifications off on that phone, remove the device from your list or sign out on it, Apple or Google tells us the token is no longer valid (or delivery is refused 5 times in a row), or your account is erased; the hash of a removed device's token: 30 days |
| Upload AI checks | about 35 days |
| Google sign-up hand-over data | up to about 1 hour |
| Encrypted database backups | 30 days (rolling) |
| Server logs and failed background jobs | application logs 14 days; failed background jobs 30 days; other server logs are rotated automatically by date or size |
| Content removed after a report | a private copy for up to 1 year, or longer where the law requires it (for example, 1 year after a report to NCMEC), for legal claims and law enforcement requests |
| Premiere purchase records | as long as your access lasts and as tax law requires (kept in Stripe) |
| Premiere news sign-ups, filmmaker proposals and e-mails to support | news sign-ups: until you unsubscribe or ask us to remove them; proposals and support e-mails: kept in our mailbox as long as needed to handle them and keep a record of our correspondence, and deleted on request unless we need them for a legal claim |
When you delete your account. Your profile is removed at once from member search and the member directory, and your public business card (and its link previews) stops working. Right after your request we e-mail you a confirmation with the deletion date and a "Cancel deletion" link. The deletion date is the third day after the day of your request, at 00:00 UTC (so you always have at least 2 full days). Until then, other signed-in members can still open your profile directly (for example from a chat or a link), your drops can still appear in the feed, and you can cancel: with that link (no sign-in needed), in Settings in the FIXER iPhone or Android app, or by writing to hq@fixer-app.com (we can cancel only before the deletion date). On the deletion date your account is closed for good and can no longer be restored. If at that time you still have an unfinished contract, an unpaid deal payment, a payment started in the last 48 hours that has not gone through, or an open complaint against you, or the law requires us to preserve the data, we wait with the erasure until these are settled or the preservation ends. Then we erase or anonymise your personal data and delete your uploaded files (photos, show reel, drops, journal, works, identity documents, imported items). We keep records of contracts, deals, payments, payouts, credits and in-app purchases for tax and accounting (up to 7 years), linked to an anonymised account ("Deleted user"); deals you published and files attached to contracts stay part of those records. If your account took part in a contract or a payment, we also keep a restricted record for 7 years so that we can meet tax and accounting duties and handle disputes and legal claims: your name as on your account, e-mail, company name, account role, identity-verification status and date and the result of each verification step (no document images or files) and the ids of those contracts and payments. Only FIXER administrators can see it, and it is deleted automatically after 7 years. These steps apply to deletions you request; if FIXER closed your account for breaking our rules, fraud or abuse, we keep its data as evidence as described in the table above. Messages you sent remain in the other person's conversation as from "Deleted user". In FIXER Go we delete your declared trips, your "my runners" pairs, the text of your run messages and counter-offers, your run filters, the receiver names on your runs' proofs and, for a company, the contacts and access notes of its runs' stops; the runs, offers and the step log stay as the other party's record. Your Workspace and calendar link are deleted. Complaint and moderation records are kept in anonymised form, and private copies of content removed after a report are kept for up to 1 year for legal claims and law enforcement. Where the law requires us to preserve data (for example the contents of a report we make to NCMEC about child sexual abuse material, or records that law enforcement asks us to preserve), we may keep that data for as long as the law requires, even after you delete your account. Copies in encrypted backups disappear when the backups expire (30 days). Our providers keep their own copies for the periods in their own policies — for example Stripe (payment and payout records), Apple and Google (purchases), OneSignal (push IDs), Twilio (SMS logs) and the AI providers (request logs).
6. Security
We protect data with measures such as encrypted connections (HTTPS), hashed passwords, encrypted backups, access limited to staff who need it, private storage for identity documents, rate limits against abuse and reviews of our code for security issues. No system is completely secure; if a data breach affects you, we will notify you and the authorities as the law requires.
7. International transfers and where you live
FIXER is operated by T21 Film Studio LLC in the United States, and we do not have an establishment in the EU, the EEA, the UK or Switzerland. We have not appointed a representative there. People outside the United States, including in the EU, the EEA, the UK and Switzerland, may register, keep a profile and use FIXER, so we describe here how we treat your data. FIXER Go works only in the San Francisco Bay Area and Los Angeles, and payouts currently need a U.S. Stripe account (Terms, sections 10 and 12A), so for most members outside the United States the data we hold is the account, profile, messages, deals and verification data in section 2.
We do not say that the GDPR or the UK GDPR applies to us in every case, but we choose to follow their main rules for everyone who uses FIXER from the EU, the EEA, the UK or Switzerland: the legal bases in section 3, the rights in section 8 and the retention periods in section 5. If you are there, you give your data directly to us, and we and our providers (section 4.2) process it in the United States and other countries that may not offer the same level of protection as your own. When our providers process your data, we rely on the European Commission's Standard Contractual Clauses in their data processing terms (with the UK addendum and the Swiss amendments where they apply) or on the provider's certification under the EU-U.S. Data Privacy Framework and its UK and Swiss extensions. We rely on a transfer being necessary for your contract with us only for occasional transfers, for example when the other party to your deal is in another country. You can ask for a copy of these safeguards at hq@fixer-app.com (subject "Privacy").
8. Your rights
You can:
- access and edit most of your data in your profile and settings;
- delete your account: in the app, or on the web at app.fixer-app.com → Settings → Delete profile (this works for accounts created in the mobile apps too), or by writing to hq@fixer-app.com from your account e-mail;
- ask us for a copy of your data (including in a portable format), or to correct, delete or restrict it;
- object to processing based on legitimate interest, and withdraw consent at any time (this does not affect earlier processing);
- ask a person to review an automated decision;
- complain to a data protection authority, for example the authority where you live or work (in the EU, the EEA, the UK or Switzerland) or the California Privacy Protection Agency. Because we have no representative in the EU or the UK, please write to hq@fixer-app.com first; you keep every right to go to your authority.
Your right to object. Where we use your data on the basis of legitimate interest (section 3), you can object at any time, on grounds relating to your situation, by writing to hq@fixer-app.com (subject "Privacy"). We will then stop, unless we have compelling legitimate grounds that override your interests, rights and freedoms, or we need the data for legal claims. You can object to any use of your data for direct marketing at any time, and we will then stop that use.
California residents (CCPA/CPRA): you have the right to know what personal information we collect, use and disclose; to delete it; to correct it; to opt out of its "sale" or "sharing" — we do not sell or share personal information as those terms are defined, and we have not done so in the past 12 months; to limit the use of sensitive personal information — we use it (ID documents, account log-in details, the contents of messages between users, Social Security or tax numbers you give Stripe for payouts, FIXER Go runners' driving license numbers, the exact addresses of FIXER Go run stops, and your device's precise location if you allow it, which we use to find your nearest city and do not store, except that for FIXER Go runners the positions recorded at check-in and "Nobody at pickup" are kept with the run's records, see section 2.2) only to provide the Services and for security, as the law permits, and not to infer characteristics about you; and not to be discriminated against for using your rights. The categories of personal information we collect are those listed in section 2 (identifiers, customer records, characteristics of protected classifications (date of birth for payout accounts; age, sex and nationality shown on ID documents), commercial information, internet activity, geolocation (your device's location if you allow it, stored only as a city), audio/visual information, professional information, and sensitive personal information as described), for the purposes in section 3, disclosed to the recipients in section 4, and kept for the periods in section 5. You may use an authorized agent: the agent writes to hq@fixer-app.com (subject "Privacy") with your signed permission or a power of attorney, and, unless the agent has a power of attorney, we may ask you to confirm your identity and the request directly with us.
California "Shine the Light": we do not disclose personal information to third parties for their own direct marketing purposes.
Ukraine: if you are in Ukraine (FIXER Go is not available there), you have the rights of a data subject under the Law of Ukraine "On Personal Data Protection", including access, correction, deletion and objection, and you can complain to the Ukrainian Parliament Commissioner for Human Rights.
Other U.S. states (such as Colorado, Connecticut, Virginia, Texas, Oregon): you have similar rights to access, correct, delete and obtain a copy of your data and to appeal our decision.
How to make a request: write to hq@fixer-app.com (subject "Privacy"). If you have an account, write from its e-mail; if you do not (for example you only bought a Premiere ticket or sent us a form), tell us the e-mail and details we can use to find your data. We may ask for information to confirm it is you. We confirm receipt within 10 business days and reply within 28 days (so always inside the one calendar month of the GDPR and the 45 days of California and other U.S. state laws). Where the law allows (for example for complex or numerous requests), we may extend this period and will tell you why before the first period ends. If we refuse a request, we will explain why, and you can appeal by replying to our answer; we will decide the appeal within 30 days (extendable where the law allows) and, if we deny it, tell you how to contact your state Attorney General.
9. Children
FIXER is only for people 18 and older. We do not knowingly collect data from anyone under 18. If we learn that someone under 18 has an account, we will delete it. If you believe a minor uses FIXER, please tell us at hq@fixer-app.com.
10. Do Not Track and Global Privacy Control
We do not track you across other websites and do not sell or share personal data, so Do Not Track and Global Privacy Control signals do not change how we treat your data.
11. Changes
We will post any update to this Policy here and change the date at the top. If a change is material, we will tell you in the Services or by e-mail before it takes effect.
12. Contact
T21 Film Studio LLC
100 Infinity Way, Mountain View, CA 94043, USA
E-mail: hq@fixer-app.com (subject "Privacy")