Information we handle
- Account and access information: name, email, password hash, login sessions, company memberships, roles, invitations and security events. Authentication uses cookies; passwords are stored as hashes.
- Company records entered by authorized users: divisions, customer and supplier contacts, addresses, projects, schedules, tasks, notes, files, estimates, invoices, expenses, imports, categories and payment records. Imported data can include financial history supplied by the company.
- Workforce information: worker identity and contact details, assignments, time entries, corrections, rates when entered, time-off requests and review history. Optional location sharing is described below.
- Customer-document information: the shared document version, recipient details, access and delivery records, verification challenges, typed signatures or decisions, consent and payment status. A private document link gives viewing access to whoever receives it; only the designated recipient can record a verified decision.
- Assistant and support information: messages you send, assistant replies and reviewed proposals, saved action receipts, usage and cost metadata, and the reports or replies you choose to send to support.
- Technical information: request and security metadata needed to operate the service, and page and visit information handled by hosting or analytics services where enabled.
How information is used
We use information to authenticate users, enforce company and role boundaries, provide the workflows the company requests, maintain reliable records, process authorized document and payment actions, deliver requested communications, investigate problems and prevent misuse. Support reports are available to the requester and approved support operators; support does not automatically grant access to private assistant transcripts.
Company administrators and authorized managers can see records allowed by their roles. Employees and subcontractors have restricted access. Company selection and authorization are checked on the server. Infrastructure administrators retain the access necessary to operate the service.
The application does not implement advertising or sale of workspace records. Sharing a customer document, exporting a calendar or sending a message is an explicit workflow and may give the chosen recipient a copy.
Business calls and voicemail
When calling is enabled, ParadoxOS and Twilio process business and caller phone numbers, division routing, device registrations, call status and duration, consent events and service usage. Authorized users can see their division inbox and call history. Browser calling needs a visible registered browser; an unavailable browser can route calls to the configured phone backup.
Administrators may upload or record division greetings, or enter text for basic text-to-speech. Recording a greeting uses the microphone only for that greeting. Greeting audio is stored privately in the application database. Twilio receives greeting text or temporary access to selected greeting audio to play it during a business call. A device voice preview can differ from the voice used on the telephone call.
Human-call recording is optional and off by default. A company may choose an announcement with an opt-out or an explicit keypad permission step. In announcement mode, the caller hears “This call may be recorded, press 1 to opt out” before recording starts. Answering staff receive a recording notice unless that participant has already heard it. Opting out at the notice continues without human-call recording. Companies remain responsible for appropriate notice and lawful consent; issuing a notice is not proof it was heard or understood.
Twilio stores call audio. Authorized division administrators can play it privately, request a stop or delete it. Call audio, available transcripts and extracted details default to 30-day retention. Before expiry, an administrator may mark a completed call Keep indefinitely; that keeps its available audio, transcript and notes until deletion is requested. It does not recover content already expired or deleted. Audio is hidden at expiry or a deletion request; provider deletion may be delayed by an outage or backlog.
Voicemail is separate. After an unanswered call, the caller may choose to leave a private voicemail of up to two minutes. A caller who opts out of AI or call recording can still voluntarily leave voicemail. Earlier recordings keep their saved deadlines unless deliberately preserved. Call history, notice and choice events, usage, audit records, provider metadata and backups have separate retention. Twilio recording metadata may remain after audio deletion.
Optional AI call answering
AI call answering is off by default and enabled separately for each division. AI can answer first or serve as backup after the team. The assistant identifies itself as AI. Before connecting to Retell, the caller hears “This call may be recorded, press 1 to opt out.” Pressing 1 at that notice bypasses AI and call recording and routes to the configured backup or voicemail. During AI answering, callers can press 1 or ask to leave AI or stop recording. The assistant requests a handoff; keypad recognition and tool processing can take time.
Retell and its configured speech, language-model and voice providers process the conversation in real time. Twilio carries the call and stores the app-controlled recording. ParadoxOS supplies the division’s approved business facts and imports available transcripts, call analysis and short extracted details such as caller name, business, town, request, urgency and callback preferences. These are private division records retained for 30 days unless manually preserved before expiry. It does not import Retell recording URLs or tool logs. The configured per-call storage policy asks Retell to retain basic call attributes instead of recordings or transcripts; contact memory is disabled. Retell still processes content to answer and produce notes, and provider terms, logs and backups have their own retention.
The assistant can answer public business questions, take a message and try the configured team. It cannot authenticate a caller from caller ID, access private customer records, promise prices or dates, book work, take payment or send messages. A request for a person rings the backup while AI remains available; if nobody accepts, the assistant can offer to take a message.
AI calls include recording after the announcement. Pressing 1 or objecting to AI or recording disconnects the assistant before the unrecorded handoff. The application waits for recording and AI disconnection to be confirmed; if that cannot be confirmed, it does not bridge a potentially recorded human conversation. Authorized administrators can also request Stop or delete audio. Recordings, transcripts and notes remain available for 30 days unless manually preserved before expiry. Provider deletion can lag behind the application’s access cutoff.
AI-generated notes can be wrong; verify them before acting. A callback preference is not text-message consent. AI setup does not enable human-call recording, texting or automatically enroll a company in paid service. The older optional call assistant uses Twilio and Google speech processing, Vercel AI Gateway and OpenAI when specifically configured; provider logs for that path are separate from app notes.
AI assistant
When the assistant is enabled for your company and login, the application sends your message, a bounded history of that conversation and relevant authorized context to Vercel AI Gateway and the configured model provider, currently OpenAI. Context can include a selected or name-matched project, linked customer, schedule details, task titles and notes, and your owner display name. Avoid passwords, private access links and sensitive personal information in prompts. The current context builder does not include financial transaction records, but anything you type yourself can be sent.
Chats are resumable for seven days after the last sent message, subject to a hard limit of 30 days from creation. At that hard limit, application reads and reviews deny the content. An hourly maintenance job removes expired transcript and copied proposal content in bounded batches; outages or a backlog can delay physical removal. IDs, timestamps, usage and security metadata remain. Applied changes remain in the ordinary company records and their audit history.
Unsent drafts stay in browser memory during navigation and are lost on reload. Developer transcript review requires a separate named, scoped and expiring authorization checked on each read. Application cleanup does not promise removal from infrastructure backups or provider-held copies; those follow the provider’s applicable terms and retention settings. AI output can be incorrect. Review a proposed change before applying it.
Workforce location and weather
The crew location checkbox starts unchecked. Device location is requested only when a worker chooses to share it during a clock event. ParadoxOS does not continuously track a device or request background location. A company can require a location notice and review a missing-location exception; denied or unavailable location does not manufacture coordinates or prevent recording worked time.
Shared coordinates, accuracy and capture time are limited to the worker’s own receipt and the authorized company review console. Location retention defaults to seven days and can be configured by the company between one and 30 days. Expired coordinates are hidden on reads and removed by scheduled or manager maintenance, while time, consent status, exceptions and audit history remain. Employers are responsible for appropriate notices and employment policies.
Project weather uses approximate coordinates from a locally resolved US ZIP area sent to the National Weather Service. The forecast request does not send a customer’s street address, name, project ID or notes and does not request device location.
Payments and bank connections
Stripe handles payment details in its secure payment interface when an eligible invoice is paid. ParadoxOS stores the invoice, requested amount, provider references, payment status and reconciliation or adjustment records. It does not collect raw card numbers in its own payment form. An invoice signature or a browser return from checkout does not by itself mark an invoice paid.
Stripe Financial Connections supports an optional operating-bank transaction feed. A company’s authorized Owner or Admin must verify a fresh authenticator code and give separate connection consent. Bank credentials and account selection are handled in Stripe’s interface. Linking alone does not enable imports: each selected account must be mapped and its transaction subscription explicitly confirmed. A bank connection is separate from invoice payment and does not grant access merely because this policy is published.
For an account that the company subscribes and enables, ParadoxOS receives provider account references and display details, transaction dates, descriptions, signed amounts, currencies, status and update references. Imports follow the company’s reviewed daily or monthly app schedule. This integration requests transaction data, not balances or ownership reports, and does not initiate bank payments. Original signed amounts remain unclassified for review; they cannot post to the financial ledger while their direction is unverified.
Pausing or disconnecting retains previously collected transaction history, import decisions and audit records. Stopping app imports or letting a pilot policy expire does not by itself cancel Stripe’s transaction subscription; the authorized company user must separately pause that subscription or disconnect. Stripe’s own processing, retention, terms and fees also apply. Plaid connections remain unavailable. Existing bank statements manually imported by a company remain company records.
Service providers and disclosures
The service uses Vercel for hosting, applicable analytics, file storage and AI Gateway; Neon for the application database; Stripe for enabled payment services; Forward Email for configured outbound email; OpenAI for enabled assistant models; Twilio for configured business calling, voicemail and optional call recording; Retell and its configured model and voice providers for the AI receptionist; and Google through Twilio for enabled AI-call speech recognition and text-to-speech. Providers receive the information needed for the features being used and may process it in locations outside your own jurisdiction. Their terms and notices also apply to their processing:
- Retell privacy policy
- Vercel privacy notice
- Neon privacy notice
- Stripe privacy policy
- Forward Email privacy policy
- Twilio privacy notice
- Twilio and Google speech-processing information
- Twilio AI and machine-learning terms
- OpenAI privacy policy
We may disclose relevant information to the company’s authorized users, recipients you choose, service providers supporting the requested feature, or when reasonably needed to respond to lawful requests, protect the service or resolve a dispute.
Cookies, analytics and security
Cookies support authentication, company selection and private document access. Browser storage and memory can retain interface preferences and temporary drafts. Vercel Analytics can receive page URLs and technical visit information on routes where it is enabled. The application excludes customer-document, bank-management, import, invitation and certain account-security routes from its analytics component; hosting still handles requests needed to serve those pages.
The public application uses HTTPS. Server-side authorization, scoped queries and controlled private document access help protect information. This policy does not certify every infrastructure or device control, promise universal regulatory compliance, or guarantee that a system is free of risk. Do not share passwords, verification codes or private document links in support reports.
Retention, requests and choices
Outside the assistant and location limits above, ParadoxOS does not apply one universal automatic deletion deadline. Business, financial, time, signed-document and audit records can remain after an item is archived or access is revoked. Retention depends on the company’s operational needs, recordkeeping obligations and the service’s security and dispute needs. Provider backups and logs have separate retention; we do not claim immediate deletion of every copy.
You can ask about access, correction, export, deletion or a privacy concern. For records controlled by your employer or another company, contact that company first. For application operation, use your private ParadoxOS support conversation or email contact@paradoxicalsw.com with the subject “ParadoxOS privacy”. We may need to verify your identity and authority before acting. A request is reviewed rather than automatically erasing shared business records; applicable recordkeeping, security and other people’s rights may limit deletion. Do not email credentials or full financial documents.
You can decline optional device location, avoid using the assistant, close private document access in your browser and ask your company administrator to change or remove authorized access. Closing access does not erase an existing signed document or settled payment.
Updates
This policy describes the application at the effective version above. We will update this page when the described processing changes. New bank-feed collection or materially different sharing requires its relevant notice and setup before activation.