1. Who we are and when this policy applies
REDA One LLC, 5 Independence Way, Suite 300, Princeton, NJ 08540, United States (“REDA”, “we” or “us”), operates this website and contracts for REDA AI subscriptions as an authorised global reseller. The product IP belongs to Vedi Technologies, #207 City Center, Amravati Enclave, Panchkula, Haryana, India 134107. Contact legal@reda.one about privacy and individual rights.
This policy distinguishes website and business relationship information, the customer’s Salesforce records, external AI processing and any information supplied directly to REDA for product support. REDA determines the purposes of its own website and business relationship records. Supplying the app does not by itself classify REDA as a processor for every activity in a customer’s Salesforce organisation.
Roles for any processing on a customer’s behalf depend on the actual activity, receiving services and account arrangements. Where REDA acts as a processor, it must follow the applicable instructions and legal requirements. The MSA data provisions and any applicable agreed data-protection terms govern those activities. This policy does not waive obligations imposed by law.
2. Website visits and business enquiries
Information you provide. We process the contact and business details you send when requesting a white paper or trial, discussing a pilot, emailing us or seeking support. These may include your name, business email, company, role, message and information about the process you want to improve. Please avoid sending sensitive customer records in a general enquiry.
How we use it. We use this information to respond, arrange discussions, manage the relationship and provide requested services. Where applicable, we rely on legitimate interests in handling business enquiries and securing our services, steps requested before entering a contract, contractual necessity for an individual contracting with us, legal obligations, or consent where required. Marketing permission is separate from asking for help or a meeting. You may object to direct marketing at any time by contacting us or using an unsubscribe option provided in a message.
Enquiry routing. When an enabled website form is submitted, the details go to REDA’s own Salesforce organisation through Salesforce Web-to-Lead. Email and support enquiries are handled through the communication services used for that relationship. An enquiry does not give REDA access to your Salesforce organisation.
Connection information. Hosting services receive technical request information needed to deliver the website, such as IP address, requested resource and browser information. We use this for website delivery and security. Providing enquiry details is voluntary; without sufficient contact information we may be unable to respond.
We do not sell or rent personal information. We do not use website enquiries to make solely automated decisions with legal or similarly significant effects on you.
3. Website services and cookies
This website is hosted by Netlify. Fonts are served with the website’s own files. The hosting service receives connection information even when a page does not set analytics cookies.
On a first visit, the website uses a supported browser language, with English as the fallback. Links to a specific language keep that language. A language you choose in the menu is saved in this browser until you change it or clear website storage; if storage is unavailable, the choice cannot be remembered for future visits.
YouTube demos. The demo page uses YouTube-hosted videos. Posters are served with this website; clicking Watch or Play requests YouTube playback and loads its player and player API. There is no separate permission screen, and no YouTube player loads on page arrival. Playback connects your browser to Google, which receives technical connection and playback information and may use cookies or other storage. We use YouTube’s privacy-enhanced embed domain; this does not mean that playback sends no information to Google. Google’s Privacy Policy applies. You can instead follow a direct YouTube link.
Use Cookie preferences to change or withdraw permission for embedded YouTube videos. A saved choice is kept in browser local storage for up to six months. Playback starts when you select a demo, subject to your browser’s playback settings. After withdrawing permission, selecting another demo requests playback again. Withdrawing permission stops and removes an open player; it cannot erase information already sent to Google or storage controlled by Google. Manage provider cookies and storage through your browser. If browser storage is unavailable, your choice applies only to the current page. The caption language initially follows the selected website language, then a supported browser language, with English as the fallback; your selection within the player is not stored by this website. The website does not currently embed Google Analytics, Wistia or Calendly. Following an external link takes you to a service governed by its own privacy notice.
Form security. Contact and white-paper forms use Google reCAPTCHA to help prevent spam. The widget loads automatically when a request form is shown, connecting your browser to Google. Google receives technical information for the check and may use cookies. Its Privacy Policy and Terms of Service apply. If you prefer not to load it, you can email sales@reda.one instead.
Nova website assistant. Nova connects to our Salesforce-hosted chat service when you choose “Ask Nova”, and reconnects when restoring an open chat as you move between pages. Messages you send and relevant technical connection information are processed to provide the conversation. Relevant message content is also sent to the AI provider used by Nova. Conversations and any enquiry details you choose to provide may be recorded in our Salesforce organisation. Please do not enter sensitive or confidential information. The selected website language helps select the welcome text, with your browser language as a fallback; you can change the language in the chat. A language you select is remembered in session storage for this browser tab. The widget stores an opaque conversation token in browser local storage, or session storage where supported cross-tab coordination is unavailable, to resume your chat after navigation or reload. The transcript is retrieved from our chat service rather than stored in browser storage. The service controls session expiry; “End chat” ends the session. Whether the panel is open is remembered for this browser tab. If browser storage is unavailable or cleared, chat continuity may be lost. You can contact us directly instead of using Nova.
Optional voice input. In supported browsers, Nova’s microphone button converts speech into an editable message. It starts only when you select the microphone and grant any permission requested by your browser. Your browser or its speech-recognition service may process audio online under its own privacy terms. The website does not upload audio to the Nova chat endpoint; the text you choose to send is processed as a chat message. You can stop dictation, edit the text before sending, or type instead. Closing Nova or leaving the tab stops dictation.
White-paper downloads. Temporary storage in your browser tab records the requested paper ID and submission time to show the matching downloads and avoid starting the same download twice. After you return from the request form, a session cookie remembers access to the white-paper library across tabs. These markers contain no name, email or other form details. Access lasts for this browser session, with a maximum of 24 hours; browser session-restore settings may retain session cookies. You can clear access using “Reset access on this browser” beside your downloads. We record the first request in Salesforce; subsequent downloads during that visit are not added to your Lead record. Requesting a white paper does not subscribe you to a newsletter.
4. Salesforce records and connected experiences
The REDA AI managed package operates in the customer’s Salesforce organisation. Conversation history, incident records, credit usage and configuration records created by the package reside there under the customer’s access, retention and backup arrangements. The core AI inference path does not use a separate REDA-operated middleware database to store these records.
When an agent runs, selected request content travels to the configured AI provider and its response returns to Salesforce. Content may include instructions, record fields, conversation text, documents and tool results. It is not limited to technical tool descriptions.
A connected AI client, such as Claude through MCP, also receives information returned through that connection. Customer or partner portals, websites and messaging integrations have their own participating systems and identities. The customer must consider each route and the receiving account’s terms; an API arrangement does not automatically govern a separate connected-client account.
We access a customer organisation for support only when authorised. If you send REDA logs, attachments or other data directly, those disclosures are handled separately as support information. A statement about where Salesforce records reside is not a promise that REDA can never receive information you send us.
5. AI processing, training and retention
REDA does not operate or train an AI model and does not use Client Data to train one. AI-provider processing is distinct from REDA’s own activities. The selected processing tier, account terms and configuration determine which provider receives a request.
Anthropic. The primary provider’s Commercial Terms restrict model training on commercial customer content. Its Data Processing Addendum and retention information describe separate processing and retention conditions. A restriction on training does not mean zero storage. We do not represent that every account has a zero-retention agreement.
DeepSeek / Economy. This optional route has different provider terms and China-related processing considerations. It requires the applicable credential and administrator enablement steps described in MSA Section B3A. DeepSeek’s published terms permit specified improvement use of inputs and outputs and describe an opt-out. That wording does not establish that an opt-out is active for a particular API account. Under AI included, document and file processing uses the primary provider irrespective of the selected tier. Customer-account processing uses the configured customer connections and supported models.
With Bring your own AI, the customer connects supported Anthropic, OpenAI, Gemini or DeepSeek accounts and selects supported models. Credentials are stored in the customer’s Salesforce credential store; REDA does not hold those keys. Request content goes to the selected provider under the customer’s own agreement, training and retention settings. Review those arrangements separately before connecting an account. REDA’s managed-account terms apply to AI included, not to customer-contracted accounts. Contact legal@reda.one to review the processing arrangements relevant to your intended use.
6. Who receives information
Recipients depend on the activity and contractual arrangement. A service contracted directly by the customer is not automatically REDA’s subprocessor merely because it connects to REDA AI.
- Website delivery
- Netlify receives hosting requests. Fonts are served with the website. Google receives technical connection information when a form’s reCAPTCHA security check loads, and connection and playback information when you select a YouTube demo to play.
- REDA enquiries and support
- Salesforce hosts REDA’s enquiry records. Authorised REDA personnel and communication/support service providers handle information supplied for the business relationship.
- Customer Salesforce organisation
- Salesforce hosts the customer’s records under the customer’s own Salesforce agreement.
- AI inference
- Under AI included, Anthropic and DeepSeek where enabled receive the content required for requests. Under Bring your own AI, the selected supported provider receives that content under the customer’s direct account arrangements.
- Connected clients and channels
- The receiving AI client, website, portal or messaging service receives information through the integration the customer enables, under the relevant account arrangements.
We may disclose information where legally required, to professional advisers under appropriate confidentiality obligations, or as necessary to establish or defend legal rights. Contact us to identify the recipient and account arrangements relevant to your proposed use at legal@reda.one. Material subprocessor changes are handled under MSA Section H3.
7. International processing
Service providers and connected accounts may process information outside your country. Provider headquarters alone do not establish where every request is processed or retained. The Economy route has the China-related disclosures in MSA Section B3A. Other processing locations depend on the provider and account arrangements.
Where applicable law requires a transfer mechanism or safeguards, those requirements must be addressed under the applicable processing agreement, including Standard Contractual Clauses where appropriate. An administrator’s choice of provider is an instruction to use that route; it is not a substitute for a legally required transfer assessment or safeguard. Ask legal@reda.one for the terms and safeguards applicable to your proposed deployment.
8. How long information is kept
Customer Salesforce records: governed by the customer’s configuration, retention and backup policies. Customers must arrange exports and backups before termination and uninstall. No post-termination access or export period is included, and package records are not guaranteed to remain available after licence expiry or uninstall.
AI-provider and connected-client records: governed by the receiving service’s applicable terms, product and account settings. Provider retention and customer-controlled Salesforce retention are separate.
Information supplied to REDA for support: retained only as necessary to resolve the request and for up to 90 days afterwards, subject to retention required by law. Return or deletion obligations continue to apply to material REDA holds separately.
Enquiries and business records: retained for as long as needed to handle the enquiry or business relationship, meet legal obligations and establish or defend legal claims. Relevant factors include the purpose, whether the relationship remains active and applicable recordkeeping requirements.
Website delivery and security records: retention depends on the hosting or delivery service and its applicable configuration and terms. Contact us about records relating to your visit.
Removing direct identifiers does not necessarily make information anonymous. Information that remains identifiable remains subject to the relevant privacy obligations.
9. Your choices and rights
Depending on applicable law, you may have rights to access, correct, delete or obtain a portable copy of personal information; restrict or object to processing; withdraw consent; and complain to a supervisory authority. Withdrawing consent does not affect the lawfulness of earlier processing based on that consent.
You can object to direct marketing at any time. Contact legal@reda.one or use the unsubscribe route in a marketing message.
For information held by REDA about website visits, enquiries or support, contact legal@reda.one. We may need to verify identity or authority and will respond within the period required by applicable law. You may use an authorised representative where permitted and will not be penalised for exercising applicable rights.
For records held in a customer’s Salesforce organisation or its portal, contact that organisation. If you approach REDA directly, we will route the request appropriately and assist the customer as required. You may also complain to your relevant data-protection authority.
10. Security and incident reporting
We maintain commercially reasonable technical and organisational measures for the managed package, systems we operate or control, and credentials we issue. No system or transmission is risk-free, and REDA does not control the internal systems of Salesforce, AI providers or customer-selected services.
Under the MSA, we notify affected customers without undue delay, and in any event within 72 hours after becoming aware of a personal-data breach affecting Client Data within systems we operate or control. For relevant incidents at a third-party processor, we pass on information without undue delay after becoming aware of it, including after receiving its notification. These contractual provisions do not remove obligations imposed by applicable law.
Report suspected vulnerabilities or unauthorised access to security@reda.one. For an overview of access, processing and usage controls, read Governance & trust.
11. Data-protection arrangements and updates
The data-protection requirements for a deployment depend on the actual processing and the parties’ roles. Where applicable law requires written processing terms or transfer safeguards, those requirements must be addressed before the relevant processing begins. Contact legal@reda.one to discuss the arrangements for your intended use.
No blanket GDPR, HIPAA or other regulatory certification is implied. We update this policy when relevant practices change. The revision date appears above. Material changes affecting active subscribers are notified as required by the applicable agreement and law; publication of this notice does not silently replace an existing signed contract.
Legal contact
REDA One LLC
5 Independence Way, Suite 300
Princeton, NJ 08540, United States
Legal and privacy: legal@reda.one
Security: security@reda.one
Product IP owner
Vedi Technologies
#207 City Center, Amravati Enclave, Panchkula, Haryana, India 134107