Privacy Policy

1. Our role and the business you work with

For information used to run our own business relationship with you, such as your RevX account, subscription and support correspondence, we decide the purposes of processing. When an organization stores information about its customers, staff or jobs in RevX, that organization controls that business information and we process it to provide the Service on its instructions.

Your organization’s authorized users can access records according to their assigned roles. If you are a customer or employee of an organization using RevX, contact that organization first about its use of your information. You may also contact us, and we will route or assist with your request as appropriate. We do not claim that your employer’s separate privacy practices are covered by this policy.

2. Information handled by the Service

We receive information from you, your organization, people who sign shared agreements, and service providers that return authentication or delivery results. Historical payment-processing results may also be retained where applicable; new card collection is unavailable for this launch.

• Account and organization information: names, business names, contact details, login credentials handled by the authentication service, user and organization identifiers, roles, security settings, and account preferences.
• Business records: customer names, email addresses, phone numbers, service and billing addresses, properties, appointments, job details, estimates, invoices, payment status, receipts, notes, tasks, pricing, and information that your organization enters about staff time, pay or commissions.
• Photos and documents: images you choose to capture or upload, captions, uploaded or linked business records, and document contents. Images uploaded through the job-photo upload service are re-encoded and embedded metadata is removed. A separately supplied external image URL remains subject to that external host’s practices; loading it can disclose your device’s IP address and request information to that host.
• Agreements and signatures: document contents and versions, typed or drawn signatures, signer name and email, electronic-signature consent and intent, timestamps, signing IP address and browser information, verification events, and a tamper-evident event record. A signature image is stored as evidence, not used by RevX for biometric identification.
• Payment records: amounts, status and method for payments or returns recorded as received or made outside RevX. Historical processor identifiers, refunds, disputes and masked saved-card information may remain where applicable. This release does not collect new card details; do not enter full card numbers or security codes into RevX records.
• Communications and assistant content: messages, recipients, delivery status and consent/opt-out records; assistant questions, conversation history, responses and requested actions. Do not place passwords, full card details, medical records or other unnecessary sensitive data in free-text fields.
• Technical and security information: IP addresses where recorded, browser or device information supplied with requests, access and audit events, error diagnostics, and essential session information. We use these to operate and secure the Service.

3. Permissions, location and local device storage

The iPhone app requests camera permission when you choose to take a job photo and lets you select an image from your photo library. You can decline access and continue using the other features. Uploaded photos become part of your organization’s business records. The current iPhone release does not request device contacts, microphone or location access, and does not track your background location.

Service addresses are entered as business records. Any separately enabled browser field-location feature requires the browser’s location permission and the field feature’s consent. It may record location during an active field session; stopping or revoking consent ends future collection. It is not part of the current iPhone location-permission flow.

We use essential web session cookies for sign-in and security. The mobile app stores session credentials in the operating system’s secure storage and stores limited preferences and pending-operation recovery information on the device. Sign-out removes the app’s active session credentials. We do not use advertising identifiers or cross-company advertising tracking in the current release.

4. Why we use information

We use information to provide the records and workflows you request; authenticate users and apply access controls; manage subscriptions and business payments; deliver configured messages and documents; support users; investigate failures and security incidents; prevent fraud and misuse; and meet applicable legal obligations. Where consent is required for an optional feature, you can decline it without losing unrelated functionality. We do not sell or rent personal information or use customer business records for targeted advertising.

5. Who receives information

Information is available to authorized users of your organization and to people you choose as recipients of a message, document or signature request. Treat shared document links as confidential. A recipient may keep a copy outside RevX.

We use service providers to process information needed for their assigned service. We require providers receiving personal information on our behalf to protect it consistently with this policy and the applicable service and data-processing agreements; they may not use it for unrelated purposes on our behalf. Some providers, including payment processors, also process information under their own legal obligations and privacy terms.

• Hosting and infrastructure: Netlify (web application hosting, content delivery and server functions); Supabase (database, authentication and file storage).
• Supabase provides account authentication and/or managed database and private file storage, as configured for this Service.
• New customer card collection and saving cards are unavailable. Stripe may continue processing historical payment settlement, refunds, disputes, card removal and separately agreed prior RevX subscriptions. RevX retains the related payment records needed for reconciliation; manual entries record payments received or returned outside RevX.
• Resend delivers configured business email, such as agreement signing messages, completed agreement copies, reminders and permitted marketing messages. This does not mean that payment receipts are automatically emailed.
• Sentry receives limited server-error diagnostics, such as the error category, route pattern, request method and time, to help repair failures. Our reporter excludes request bodies, user identity, raw error messages and stack contents. The provider also processes the network information needed to receive these reports.
• Upstash stores short-lived security counters used to limit repeated requests. RevX hashes the caller key before sending it; the key may be derived from an email address, account identifier or request capability. Hashing does not make these identifiers anonymous. The provider also processes the server connection information needed to operate the service.
• Google/Gmail processes messages and attachments you send to our support or privacy email address, together with addressing and delivery information. Support correspondence is separate from CRM records and follows the retention criteria below.
• When you enable optional AI, the selected generation provider and OpenAI’s mandatory safety-screening service receive the text and relevant accessible CRM information described in the AI consent screen. OpenAI is a separate safety processor even when another generation provider is selected. See the AI section below.

6. Optional third-party AI

The Assistant can send your messages and relevant CRM records you are permitted to access to an external AI provider. These may include customer contact details, job information, estimates, invoices and business summaries. The consent screen identifies the actual provider, model and destination before sharing begins. The available generation providers include Anthropic, OpenAI, DeepSeek and Moonshot (Kimi). For this release, a custom configuration can use only the fixed OpenAI endpoint; other stored custom destinations cannot run. OpenAI also performs mandatory safety screening of user requests, provider turns and tool arguments, accessible CRM results, follow-up text and app-built summaries. This screening sends text, not job photos or uploaded files; provider credentials are not included in that content.

You must explicitly agree before RevX sends these requests. Declining keeps the rest of the app available. A change to the generation or safety configuration, key or disclosure requires a new consent choice. You can revoke future sharing on the Assistant screen. Revocation cannot retrieve data already delivered to the provider or erase copies retained under that provider’s applicable terms.

Your organization is responsible for approving its chosen provider’s privacy, security, retention and data-use terms before enabling it. No provider-independent promise of zero retention or no model training is made here. Contact your organization or the provider about information already sent. The assistant displays application-built summaries of retrieved CRM information and bundled help, rather than arbitrary provider prose. Chat does not change records or send messages; creation requests open forms for you to review. Explicitly scanned follow-up suggestions are screened before storage, display and any approved send. Safety screening may reject ordinary wording or miss a problem; use Support to report concerns and review results before relying on them.

7. Other disclosures and processing locations

We may disclose information when reasonably necessary to comply with law or lawful process, establish or defend legal claims, prevent fraud or harm, or protect rights and security. In a proposed or completed merger, financing or asset transfer, relevant information may be disclosed with confidentiality protections and any notice required by law.

Our configured service processing locations are: Netlify server functions run in Ohio, United States (us-east-2), with globally distributed content delivery, request routing and provider operations. Supabase core database, authentication and stored files are in US East, North Virginia (us-east-1), with operational logs in the European Union and global support/CDN processing as described in its provider terms. Resend sends email from North Virginia and stores email data in the United States. Google/Gmail support correspondence and Stripe payment-provider processing may involve global infrastructure and operations. Upstash counters use Washington, D.C. (iad1); Sentry uses US data storage, subject to each provider's separate operational and support processing. Optional AI sends text to the business-selected AI provider and to OpenAI for mandatory content moderation; this configuration does not guarantee a particular processing country for those AI services.. Your organization’s separately selected AI or other provider may process information in additional locations disclosed by that provider. Where applicable law requires a transfer mechanism or other safeguards, those must be in place for the relevant processing.

8. Retention and account deletion

We retain active account and business information while needed to provide the Service. Retention also depends on the record type, the organization’s instructions, security needs and applicable legal obligations. We do not promise indefinite storage or a complete backup through the standard data-export feature.

You can initiate an authenticated deletion request in the iPhone app at More → Delete account, or on the web at Settings → Privacy & account → Request deletion. An owner’s request covers the organization and its associated users and business data. Another team member’s request covers that user’s sign-in, profile and personal settings; company-owned business records may remain under the organization’s control where appropriate. You do not need to send a separate email or call support to initiate the request.

We aim to complete verified requests within 30 days and send a completion notice. If a legal retention requirement or an unresolved payment affects your request, we will explain what is retained and the next steps.

Deletion requests are processed by the RevX operator, rather than an automatic deletion timer. We use your account email for timing, any necessary explanation of retained records, and the completion notice. The in-app request is sufficient to start this process.

Retention exceptions and periods: We retain only records needed for an identified tax or accounting duty, an active legal claim or preservation duty, a security or fraud investigation, or an unsettled payment, for as long as that specific reason applies. We explain any exception that affects a deletion request. Support and privacy correspondence is retained as needed to resolve and document the request, confirm completion and address an active complaint; unnecessary content is removed when those purposes end. Company-owned business records associated with a departing team member remain controlled by that organization. Independently controlled provider records may remain under the provider terms and applicable legal duties. Any retained data is restricted to the reason for retention and removed or de-identified when that reason ends.

RevX currently uses Supabase Free and does not provide a managed backup service, guaranteed recovery window or guaranteed file recovery. Account deletion removes active CRM records separately from any provider-controlled backups or security copies, which follow the applicable provider retention process and legal obligations. Any backup or export controlled by RevX that contains deleted data is restricted from ordinary use and must have completed deletion requests reapplied before restored data becomes available. We do not promise that every provider backup or recipient copy is erased within the account-deletion target.

Removing your account and records from the active RevX database, authentication service and file storage is separate from expiry of provider backups or security logs. Email delivery records, support correspondence and provider security or payment records may have different retention and deletion periods under the provider’s applicable terms or legal obligations. We manage deletion requests for information in our provider accounts and explain any applicable retention exception or provider deletion delay. Our account-deletion target is not a promise that all provider or recipient copies disappear on that schedule.

Deletion from RevX does not erase copies already delivered to recipients, records another business independently controls, payment-processor records required by law, or external AI/provider copies subject to their own obligations. Contact the relevant recipient or controller about those copies. We keep only the minimal deletion record needed to record completion and prevent improper restoration.

9. Your choices and privacy requests

Depending on applicable law, you may have rights to access, correct, delete or obtain a copy of personal information, restrict or object to processing, withdraw consent, or appeal a decision on a privacy request. Withdrawing consent affects future processing and does not undo prior lawful processing. We do not discriminate against people for exercising applicable rights.

Send requests concerning information we control to omarsalim.hq@gmail.com. We may reasonably verify your identity and authority before acting. If we cannot fulfill all or part of a request, we will explain the applicable reason and any available next steps within the timeframe required by law. For organization-controlled records, contact that organization; we assist it with verified requests.

Use the unsubscribe control in marketing emails to stop that marketing. Necessary account, security and transaction messages may still be sent. Production SMS is not available in this release. Camera/photo permissions can be changed in device settings; optional AI sharing can be revoked in the Assistant.

10. Security, children and policy updates

The Service uses encrypted network connections in production, account access controls, tenant isolation, and protected storage of mobile session credentials. No service can guarantee absolute security. Report suspected unauthorized access promptly to our support contact.

RevX is intended for business users aged 18 or older. It is not directed to children, and we do not knowingly collect children’s personal information for their own use of the Service. If you believe a child has provided information improperly, contact us.

We may update this policy as the Service or legal requirements change. We will publish the revised policy with its effective date and give any additional notice or obtain consent required for a material change. Contact our privacy address above with questions.