Your data. A clear explanation.

1. Who this policy covers

Raunix Rise is provided by Raunix Tech Services Pvt Ltd. This notice describes information handled through the Rise website, hosted workspaces, support and app-delivery service.

A client’s own website or app needs its own privacy notice. The client decides why it collects its customers’ information; Rise processes workspace or delivery-project information to provide the agreed service. A source-code licence does not transfer ownership of customer data.

2. Information used in Rise

The information involved depends on what you enter, upload and connect.

• Account and business details, workspace membership, permissions and support requests.
• Contacts, conversation content and attachments, consent records, tags, campaign drafts, automation rules and activity records supplied to the workspace.
• Business details and public website/profile information selected during discovery, including the source of a finding and any corrections you make.
• Brand assets, app requirements, project/source references, approvals, quotes and payment reference records used for delivery work.
• Connection credentials, technical errors, security/audit records and browser storage needed for sign-in, preferences and supported notifications.
• When you connect a Google account, Rise may access the Google account identifier, email address, profile information and the specific Google service data you authorize, such as Business Profile, YouTube, Google Ads or other explicitly requested scopes shown on the Google consent screen.

3. Why information is processed

Information is used to operate accounts, route conversations, prepare content, perform enabled workflows, connect chosen services, maintain security, assist with support and keep commercial/approval records.

Imported contact details, historical messages or public discovery results do not by themselves establish permission to market to a person. The workspace business must supply the appropriate permissions and respect requests to stop.

4. Connected services, Google data and AI

A connection or requested action can send relevant information to the provider you use—for example Google, Meta/WhatsApp, a connected store or payment provider, a configured AI content service, or Runway when video rendering is enabled. Hosting, storage and communication services also process the information needed to operate Rise.

Google user data is used only to provide the Google-connected features you choose, such as connecting an account, listing available Google assets, preparing or managing authorized workflows, showing activity in your workspace, troubleshooting errors and maintaining security/audit records.

Rise does not sell Google user data. Rise does not share, transfer or disclose Google user data to advertising networks, data brokers or unrelated third parties. Google user data may be shared only with: Google services to complete the action you authorize; your authorized workspace members according to their permissions; contracted service providers that host, secure, process or support Rise under confidentiality and data-processing obligations; professional advisers or authorities when required by law; and another provider only when you explicitly configure a workflow that sends selected information there.

AI preparation can include business context, selected source information and draft content in a provider request. Google user data is not sent to an AI provider unless you deliberately include that information in a prompt, workflow or content draft that uses the configured AI service. Review the selected provider and its data-handling settings before sending confidential or personal information. A template or starter draft is not an AI-generated result, and approving a draft alone is not publication.

Provider accounts may have their own retention, geographic processing and privacy terms. Contact support for the processing arrangements applicable to your deployment before you upload data requiring a particular location or contractual restriction.

5. Access, storage and security

Workspace permissions determine which team members can work with its information. Authorized service operators may access information when needed for support, security or agreed delivery work. Keep accounts and provider credentials secure, and remove access when a team member leaves.

Browser storage supports sign-in and preferences. Sound and browser notifications depend on your choices and browser permissions. Disconnecting a provider stops that connection’s future authorized use; it does not erase records already held by Rise or that provider.

6. Retention and deletion

Workspace and project records are retained to provide the active service and its history. Applicable billing, support, security, dispute and legal requirements can require some records to remain after a project or account closes. Retention therefore depends on the record’s purpose and the agreed service, rather than a single fixed period for every type of data.

Ask support to review access, correction, export or deletion requests. We may need to verify your identity and authority over the workspace. Deletion from a workspace does not necessarily remove separate provider records, and backup or legally required records may follow a different retention process. Confirm any required retention schedule with us before placing data in the service.

7. Your choices and questions

You can correct business information, review enabled connections, manage team permissions and stop supported automation from your workspace. If your information was collected by a business using Rise, contact that business first about its customer records; we can help route a request if you cannot identify the responsible workspace.

For privacy requests or a suspected information exposure, email support@raunix.com with the relevant workspace or project reference. Do not include passwords, private keys or complete payment-card information. Your rights under applicable law are not limited by this notice.

8. Changes to this notice

The date and version on this page identify this notice. Material changes should be reviewed alongside your service agreement and the providers you enable. Contact support if you need the version associated with an existing project.