Privacy policy
Last updated October 21, 2026
This privacy policy describes how DANIEL MARQUES PINTO CONSULTORIA EM TECNOLOGIA DA INFORMACAO LTDA, doing business as FileCrew, collects, uses, and shares personal information when you use the filecrew.app website, the FileCrew WhatsApp bot, and related services.
Information we collect
- Your WhatsApp number and account information.
- The messages and files needed to carry out your requests.
- Message usage linked to your WhatsApp number.
- Shared files, sharing titles, file metadata and optional password hashes. Sharing belongs to your WhatsApp identity.
- Checklists, their participants, and the files submitted for each item when you create or respond to a file request.
- Usage and technical information, such as request history, IP addresses, and browser details.
- If you sign in with Google, your name, email address, and profile picture.
- If you subscribe, your billing status and subscription dates from Creem. Payment details are handled by Creem.
How we use information
We use this information to:
- Interpret your instructions, run the operation, and send the result back.
- Collect files for a checklist and show the requester what has arrived.
- Track your monthly allowance and apply subscription access.
- Keep the bot working, including limits and abuse blocking.
- Reply if you contact us.
When we delete files used for editing
Files used for PDF and image operations are temporary. We delete them after delivering the result, except that Rotate pages, Remove pages and Reorder pages keep the original available for another edit until you clear your files or your session expires. Scheduled cleanup removes cleared and expired files.
Clearing hides files from your editing session immediately. A task already queued may retain the files it needs until it finishes. Temporary files remain subject to the maximum retention below.
Download links expire after 15 minutes. Temporary editing files are retained for no longer than 24 hours.
Shared files and links
Sharings expire after seven days by default, with choices up to 30 days from publication. Drafts expire after 24 hours. We store shared files separately from editing files and delete them through scheduled cleanup after cancellation, revocation or expiry. Storage lifecycle rules provide fallback deletion within 32 days for accepted files and one day for temporary uploads.
Sharing and file metadata remain for 90 days after expiry or revocation. Optional passwords are stored as salted hashes; temporary configuration and download cookies grant access only to the relevant sharing. Clearing editing files or disconnecting Google does not delete your sharings.
Anyone with the link can download unprotected files; protected links also require the password. You choose who receives the link. Revocation blocks new download authorizations, but previously authorized downloads may remain available for up to 60 seconds and files already downloaded cannot be recalled.
Files collected through checklists
Checklist files are kept in separate private storage. Requests accept submissions for seven days by default, with options up to 30 days from publication. Confirmed files remain available to the requester for 30 days after submissions close or expire. Reopening within the original 30-day maximum recalculates retention. Revocation stops sender access; it does not restart retention for an already closed request. The exact dates appear on the request. The requester can delete files earlier. Clearing an editing session does not delete checklist documents.
Files become visible to the requester only after you review and explicitly confirm sending them. Your declared name, selected items, filenames and documents are then shared with that requester. The requester's public name is self-declared and is not a verified identity. Other senders cannot access your delivery. The requester may keep their own copy after downloading it.
Your private continuation link and browser session authorize access to your delivery without a Google account. Anyone who obtains that link can access your delivery; a shared request link or password does not prove who sent a document. Replacement links invalidate earlier private links and sessions. Unconfirmed deliveries expire after 24 hours without upload activity, no later than the submission deadline. Replaced and removed objects are deleted by the cleanup job; failures are retried, with storage lifecycle rules as a fallback. Request metadata and review history remain for up to 90 days after the request ends. Originals are downloaded as attachments without automatic classification, conversion, inline preview or malware scanning.
Account and usage records
We temporarily store incoming messages and outgoing replies to recover interrupted requests. Incoming message content is removed when work finishes or reaches its retry limit. Reply content is removed after WhatsApp accepts the send or a status callback confirms it. Failed or uncertain replies may remain for inspection for up to 7 days. Temporary message receipts and delivery status events are retained for up to 7 days. Delivery events contain message IDs, timestamps, status, a hashed recipient identifier and numeric error codes, without message text or file contents.
We retain account and usage records while your account exists, and keep records as needed for billing, legal obligations, and abuse prevention. Deleting files or disconnecting Google does not delete your account records. You can request deletion as described below.
Phone registration and usage history stay tied to the number. Action records store the action ID, type and month, without message text or file contents. Clearing files or unlinking Google keeps the number’s usage history. Receipts with message IDs prevent duplicate processing.
Detailed operational records contain an internal user ID, month, allowance decision, operation, message or job ID, elapsed time, attempts and outcome. They are retained for 90 days independently of temporary jobs. Scheduler records are retained for 7 days. We avoid phone numbers, file names, file contents and provider error text in operational logs.
Expired operational records are removed by scheduled cleanup. Database backups managed by PlanetScale follow the retention policy configured with that provider and may temporarily contain previously deleted records. Before restoring service from a backup, we must reapply deletion requests and remove expired records.
Information sharing
We do not sell your personal information. We do not show ads, and we do not use your files to train AI models. Checklist submissions are shared with the requester, as described above. We also share data with the providers that run the service, only as far as they need to do that job:
- WhatsApp, run by Meta, carries the messages and files. Meta handles them under the WhatsApp terms and privacy policy, not this one.
- Cloudflare R2 stores files until we delete them.
- Vercel runs the app and processes requests.
- PlanetScale stores account, usage and operational records and manages database backups.
- Google handles sign-in if you choose it. Connecting Google Drive requires separate consent limited to files and folders you choose for FileCrew. We use that access only to save files you explicitly select. We store encrypted access and refresh tokens, the connected email and Google account identifier, your destination folder, and transfer metadata (filename, size, source identifier and, for browser results, a content checksum) until you disconnect Drive or delete your FileCrew account. Temporary authorization attempts expire after ten minutes and are removed by hourly cleanup. Browser results go directly to Google after you choose Save; confirmed request originals are streamed from our private storage. Saved copies follow the destination folder permissions and Google retention settings. Disconnecting, deleting or expiring a FileCrew request does not delete copies already saved in Drive. We do not use Google user data for advertising or AI training. Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
- Creem receives your account ID, name, and email to process payments and manage your subscription. Card details go directly to Creem.
- When account emails are enabled, Resend receives your email address to deliver welcome and subscription confirmation messages.
- When product analytics is enabled, PostHog receives usage events with pseudonymous identifiers to help us understand which workflows people complete.
- When workflow tracing is enabled, Axiom receives technical step timings, internal references and error codes to help us diagnose failures. These traces omit phone numbers, messages and files.
Data security
We take reasonable measures to protect your information. No method of storage or transmission is completely secure, and we cannot guarantee absolute security.
Your rights
You can disconnect your number on the account page. To access, correct, or delete your number and request history, email hello@filecrew.app from the address on your account, or tell us the number if you use only WhatsApp. We verify control of the account or number before acting on a request and respond within applicable legal deadlines. Some records may need to be retained for billing, legal obligations, or abuse prevention.
Children's privacy
FileCrew is not for anyone under 18. We do not knowingly collect personal information from children. If you believe a child has used the service, email us and we will delete the data.
Changes to this privacy policy
We may update this policy. Continued use of the service after we post an update means you accept the changes.