FastContract Privacy Policy
Last updated: November 6, 2026 · Effective when first published for the Service
FastContract is operated by HubtersAI, LLC, at 2261 Market Street STE 67721, San Francisco, CA 94114, United States (“FastContract”, “we”, “us”). Contact support@fastcontract.app for privacy, security, support, or rights requests. This Policy covers our iOS and Android app, invitation and review pages, contact-card pages, PDF verification, and related services. It covers account holders, guests, contacts, and people whose information another user supplies.
1. Information we handle and why
We collect information you provide, information another participant provides about you, information from sign-in and payment providers, and technical information generated when you use the service.
| Information | Uses |
|---|---|
| Email, display and legal names, account IDs, sign-in provider, verification and session records | Create and secure accounts, verify invited email addresses, authenticate guests, prevent abuse, and recover access. |
| Profile details, date of birth, phone, address, country, jurisdiction, currency, avatar, and reusable signature | Populate documents and profiles, support eligibility and identity checks, and apply your preferences. |
| Saved identity entries, including ID type, number, issuing country, expiry and selected photos; verification submissions, government-document photos, selfie, consent and review records | Maintain the identity details you save and, separately, perform requested identity verification through authorized human review. These are sensitive records. |
| Business details, registration or tax identifiers, representatives, authority documents, authorization reviews, team membership and roles, logos and company stamps | Operate business profiles and shared workspaces, assess submitted authority evidence, and prepare branded records. |
| Contacts, profile-detail requests and responses, card-sharing choices and card links | Maintain your FastContract contacts, request details, and share selected profile information. Contacts can be entered by you, supplied by another user, or created through agreement and contact-card workflows. |
| Drafts, AI instructions and conversation history, templates, imported PDFs and extracted content, annotations and signing fields, party details, revisions, invitations and messages | Create, import, synchronize, collaborate on, deliver and manage agreements, short agreements and factual confirmations. |
| Signatures, acceptances, confirmations, representative capacity, consent wording and version, timestamps, document fingerprints, verification status, user agent and hashed signing IP evidence | Record intent and the version acted on; generate documents, certificates and integrity checks; investigate unauthorized activity and preserve transaction evidence. |
| Obligations, due dates, completion requests, attachments, photos or videos and other evidence, responses, changes and history exports | Track performance and preserve the shared fulfillment record. |
| Voice recordings and transcripts | Transcribe speech you choose to record; local processing is attempted first, with cloud fallback subject to your permission. |
| Subscription account IDs, purchase and entitlement status, renewal and expiration information | Check purchased access, restore entitlements and apply plan limits. Apple and Google process store payments; we do not receive full payment-card credentials from those purchases. |
| Where payment features are enabled: amounts, currency, payer/payee identifiers, Stripe customer and connected-account references, payment and refund status, invoices, settlement and conversion records, wallet entries, payout status and bank summaries, disputes, evidence and settlement proposals | Provide agreement funding, payment reconciliation, release, refunds, disputes and payouts, or simulate those operations in clearly identified testing. Stripe directly collects payment credentials and payout onboarding information. FastContract receives operational results, verification requirements and limited bank details such as bank name and last four digits. |
| Support messages and attachments, notification preferences, inbox state, push tokens and delivery receipts | Answer requests and send verification codes, invitations, agreement notices, reminders and optional push notifications. |
| IP addresses, user agents, request times, device/app/platform details, error and security events, AI usage/quota records | Deliver network services, enforce limits, diagnose failures, and protect accounts and infrastructure. |
Payment features are available only for supported accounts, countries and transactions. Live payment and payout onboarding can require financial, identity and tax information requested directly by Stripe. Do not submit real payment or bank credentials in flows marked test or development. Document-feature availability does not mean payment processing is supported in your country.
We do not need continuous location, your advertising identifier, or background microphone access for the inspected features. Installing a library does not itself mean we upload the corresponding category of data.
2. AI and recordings
Before sending AI text, selected files or cloud-transcription recordings, the app asks permission to share relevant content with OpenAI. Your choice is saved for your account on that device. You can decline or change it in Account → AI settings. Turning AI off blocks new requests; it cannot recall information already sent. When you permit and request an AI draft, explanation, edit, suggestion, or document import, relevant instructions, document text or file content, and conversation context can be sent through our backend to OpenAI. The result may be stored with your draft or conversation. AI consultation and inspection can use OpenAI’s web-search tool, which may send derived queries to search services and retrieve public sources. Do not put unnecessary private identifiers into research requests. Review what you submit and avoid unnecessary sensitive information. Identity-verification uploads are handled through their separate verification workflow; do not paste them into AI requests.
Text-generation requests use store: false. This setting does not guarantee that the provider retains no information. Provider abuse-monitoring and endpoint-specific retention can still apply. We do not use these inputs to train our own AI model. See OpenAI’s API data controls for its applicable terms and retention settings.
Dictation first attempts on-device Whisper transcription. The app downloads its model from Hugging Face; the host receives ordinary download/network metadata, not your recording through that download. If local transcription fails, the app asks before uploading the recording through our API to OpenAI. Declining prevents that cloud upload. A permitted choice may be remembered during the dictation session. The app attempts to delete temporary recordings after transcription or failure. An interrupted app or operating-system backup may leave local copies; remove app data or contact support if needed. The model remains locally until removed by the app or device storage controls.
Stopping a request can stop the client from waiting without stopping processing already underway. AI output is subject to human review and does not decide your legal rights or a participant’s performance.
Safety reports and blocked participants
We store your blocked participant email addresses and safety reports, including the reported account or agreement reference, your description, and a copy of a reported feedback comment when applicable. Authorized support and review personnel use these records to investigate abuse, restrict new interactions, hide abusive comments and handle appeals. We do not send your report to the reported participant automatically. Safety reports and review history may remain after account deletion where needed for security, disputes or legal obligations; account links are removed when the account is deleted. Blocking preserves existing contractual records and does not cancel agreements or payment obligations.
3. Who receives information
- People you transact or collaborate with: recipients, signers, invited collaborators and authorized business team members receive the documents, participant details, messages, shared evidence and transaction status their access permits. Signed documents and their evidence can preserve details even after your profile changes.
- People with a shared contact card: sharing a card or QR link can disclose your name, verification indicator, and the personal/business contact fields exposed by that card. Treat the link as shareable; recipients can retain information already received. Revoking a link cannot recall their copies.
- PDF verification users: depending on the sender’s verification setting, file holders or authenticated participants can obtain limited integrity and verification results. Verification can also be disabled. The public file-check workflow hashes the selected PDF locally and sends its fingerprint rather than the full PDF. Sending someone the document itself is a separate disclosure.
- Cloudflare: hosts API requests, authentication-related services, D1 database records and private R2 objects; also processes ordinary network/security metadata.
- OpenAI and Hugging Face: process AI requests or deliver the local model as explained above.
- Resend: receives email addresses and email contents for codes, invitations, updates and reminders.
- Expo, Apple and Google: deliver push notifications. Push delivery includes device tokens and routing data such as agreement/notification references and recipient email. Notification bodies are generic, but device and provider settings affect lock-screen visibility.
- Apple, Google and RevenueCat: support sign-in, app-store transactions and subscription entitlement management, as applicable.
- Stripe: processes enabled payments and Connect onboarding, status, refund, dispute and payout operations when you use those flows. Stripe applies its own terms to information it collects directly; see its Privacy Policy.
- Authorized support and review personnel: access records as needed to answer support requests, review identity or authority submissions, address payment cases, and investigate abuse.
- Legal recipients and business successors: information may be disclosed where necessary to comply with law or valid process, protect rights and security, seek professional advice, or complete a business transfer with legally required safeguards and notice.
We do not sell personal information or use it for targeted advertising or cross-context behavioral advertising in the inspected service. We do not use your private contacts to send unrelated promotions. Independently chosen sharing, exports, and third-party services are also subject to the recipient’s practices.
4. Permissions, local storage and your choices
Camera access supports capture of identity materials, attachments and QR scanning; photo/media and file selection support materials you choose to attach; microphone access supports dictation; notification permission supports optional push delivery. You can deny or revoke permissions through iOS or Android settings, although the related feature may be unavailable.
The app stores authentication credentials in secure device storage and keeps local drafts, conversation history, preferences, pending attachments and cached files. Cloud draft synchronization stores copies on our servers. Local copies, exports and device backups are separate from server records. Protect your device and remove copies you no longer need.
Use in-app notification preferences and available email unsubscribe controls to change optional delivery. Necessary authentication, security and transaction communications may still be sent when needed to provide the service. Avoiding AI, recording, optional profile fields or payment testing prevents the corresponding optional submission, but does not erase records already lawfully created.
Optional device authentication for signing
In Account → E-signature → Require authentication to sign, you can enable an additional confirmation step using Face ID, Touch ID or a supported Android fingerprint or face authenticator. It is off by default and applies to your account on that device, not automatically to other devices or website sessions. Enabling or disabling it requires confirmation. You can cancel a confirmation without signing; if biometrics are unavailable or cannot complete, an email-code alternative is available.
The operating system performs the biometric comparison. FastContract does not receive, store or transmit your device’s enrolled face or fingerprint images or biometric templates. The app receives an authentication result and uses it locally to allow or stop the requested action; that biometric result is not uploaded or added to the agreement’s signing evidence. The account-specific preference is kept in secure device storage. Turning the setting off does not remove biometrics enrolled in your device settings or alter completed agreements.
If you choose email confirmation, our backend and Resend process your account email, code-delivery content and verification/security records, as described above. Codes expire after ten minutes and are single-use with limited attempts; expiry is not a promise that all related delivery or security records are immediately deleted. Keep your device and email secure. Device authentication does not establish legal identity, representative authority, or a cryptographic signature backed by a registered device key. It is separate from the optional identity-document and selfie review, which involves the sensitive uploads and separate notice described in this Policy.
5. Retention and deletion
We retain information to provide the requested service, protect transaction integrity, resolve disputes, prevent fraud and meet applicable legal obligations. The following describes current behavior, rather than promising a deletion period that has not been implemented:
| Category | Current deletion behavior |
|---|---|
| Account, private profile and contacts, reusable assets, private cloud drafts, templates and support uploads | Account deletion removes private account data and queues associated files for removal. Failed storage removals are retried. Shared transaction evidence is treated separately below. |
| Shared/versioned agreements and evidence | Deletion can preserve agreements with an issued document version, signatures or fulfillment history, including some unsigned shared records. Account ownership is replaced with a deleted-account reference; shared records become read-only. Original party text, signatures, consents and evidence can remain to protect other participants and legal claims. No universal automatic expiry is currently implemented. |
| Identity verification evidence | Withdraw verification consent in Settings → Privacy & data to cancel verification, remove the verified badge and queue evidence deletion. Scheduled cleanup also selects finalized verified/rejected/cancelled requests 30 days after their last update and abandoned draft requests 30 days after creation. Cleanup removes verification photos and sensitive submission snapshots, with retry for file failures. Under the current verification notice, approved legal name, date of birth, country, ID type and number, issuing country and verification time remain in a private, read-only verified record while verification is active. Linked verified fields and the saved ID can be locked against changes; contact support for corrections. Consent and review receipts can also remain. Withdrawal or account deletion removes the private verified record; shared signing evidence is separate. A request still pending review is not covered by that finalized-request timer. |
| Separately saved profile IDs and photos | These are distinct from verification-request copies. Removing verification evidence does not necessarily delete the original saved ID entry and its photos. Remove saved IDs separately or delete the account; previously included shared agreement details remain in those records. |
| AI control records | Scheduled cleanup removes expired transient request/deduplication entries and usage/quota records older than 90 days. This does not delete AI conversations stored as user content. |
| Audio | Temporary local file deletion is attempted after transcription/failure; interrupted-operation and backup copies can remain. Provider handling is separate. |
| Other logs, notices, authorization reviews, payment records and backups | Retained according to service, security, dispute and legal needs; a complete category-specific automatic expiry schedule has not yet been implemented. Ask support for a deletion or retention assessment. Providers retain their own records under their applicable terms and legal duties. |
To delete your account, use Settings → Privacy & data → Delete account, or the web account-deletion page. Identity verification is required to prevent unauthorized deletion. Uninstalling the app does not delete server data. Account deletion does not cancel an Apple or Google subscription; cancel it through the store separately.
Deletion on one device cannot remove exports, another participant’s independent copies, other devices’ local files or device backups. We may restrict or preserve specific records when law, fraud prevention, a legal hold or another participant’s rights require it. Contact support to request review of retained information. We will explain applicable exceptions when responding to a verified request.
6. Privacy rights and contact
Depending on applicable law, you may request access, correction, a copy, deletion, restriction or objection, withdraw consent, use an authorized agent, appeal a decision or complain to your competent privacy regulator. Email support@fastcontract.app, including if you are an invited recipient without an account. We may verify your identity and authority without requesting unnecessary sensitive information. We respond within applicable legal time limits and do not penalize you for exercising protected rights. Withdrawal does not invalidate prior lawful processing or rewrite an executed agreement.
If California privacy law applies, the categories, sources, purposes and recipient types appear in Sections 1–3. These can include identifiers, financial/commercial information, internet activity, audio/visual content, professional details and sensitive information such as government identifiers and account credentials. We use sensitive information for requested services, verification, security and legal purposes rather than unrelated profiling. We do not offer financial incentives for personal information. We do not sell or share information for cross-context behavioral advertising, including information about children. Applicable California access, correction, deletion, sale/sharing opt-out and sensitive-information limitation rights remain subject to statutory conditions and exceptions. Contact support to exercise or appeal a request.
The service does not currently respond to browser Do Not Track signals. This does not override any legally required recognition of opt-out preference signals.
7. Security and international processing
We use safeguards such as authenticated and role-based access, private file storage, restricted downloads, session expiry and document fingerprints. These do not guarantee security or make a document anonymous. A signing IP hash is still transaction evidence and can be personal information. Report suspected compromise to support@fastcontract.app.
FastContract is operated by HubtersAI, LLC, a United States company, and acts as the controller of personal information used to operate accounts, secure the Service, administer verification and provide the purposes described here. A business customer may independently control information it puts into its agreements; its own obligations and privacy practices remain applicable. Stripe, Apple and Google may act independently for their own payment, compliance and account purposes.
Our providers operate internationally, and information may be processed in the United States and other countries where they operate. Protections can differ from those in your country. Where applicable law requires safeguards for a restricted international transfer, we must use a lawful mechanism, such as applicable standard contractual clauses, an adequacy decision or another legally permitted safeguard or exception. You may ask support for information about the mechanism applicable to your data. Agreeing to this Policy is not blanket consent to international transfers.
Additional information for the EEA, United Kingdom and Switzerland
Where these laws apply, we rely on performance of a contract for the services you request; legitimate interests in security, fraud prevention, support, service reliability and protection of transaction records, balanced against your rights; compliance with legal obligations; and consent where required, including optional identity-verification processing and permission-based features. Where information requires an additional sensitive-data condition, we obtain explicit consent or rely on another applicable statutory condition before that processing. You may withdraw consent without affecting earlier lawful processing. Declining necessary information may prevent the related feature, but optional consent is not a condition of unrelated services.
You may request access, correction, deletion, restriction, portability or object to legitimate-interest processing, and complain to your local supervisory authority. Contact support@fastcontract.app to exercise these rights or ask about lawful bases and transfer safeguards. We do not make solely automated decisions with legal or similarly significant effects. Other regional privacy rights apply where the law grants them; Delaware law in the Service Terms does not displace mandatory local privacy or consumer protections.
8. Adults, changes and contact
FastContract is intended for people 18 or older and is not directed to children. Do not create an account for a child or submit a child’s sensitive information. If you believe we have collected a child’s information improperly, contact support so we can investigate and take required action.
We will post revisions with a new date and provide notice or request consent where required, before using information for materially different purposes. Contact support@fastcontract.app or HubtersAI, LLC, 2261 Market Street STE 67721, San Francisco, CA 94114, United States about this Policy.