Legal & trust centre
Clear boundaries. No hidden promises.
Konnextions is available worldwide. These launch drafts explain how the website and product are intended to work, but require qualified review for every country where the service is sold, deployed or used.
Privacy Notice
What data is where.
Public website data
Marketing Studios may receive Google-authenticated account identity, business contact details, demonstration requests, selected meeting times, support-ticket content and basic security/diagnostic logs when you use this website. This information is used to authenticate booking requests, prevent duplicate reservations, arrange sessions, answer enquiries, secure the service, administer subscriptions and meet legal obligations. Google passwords are never provided to Marketing Studios.
Customer-deployment data
Where a customer chooses the on-premises deployment, leads, call metadata, recordings and production-workspace content are stored in that customer-controlled environment. Marketing Studios does not receive that operational data merely because the software is installed.
Support boundary
Do not submit lead files, recordings, transcripts, credentials, provider secrets, database exports or unrelated personal information through the public support or booking forms. Ticket and booking data may be processed by Cloudflare, Supabase Auth and the configured website database provider.
Rights and contact
Subject to applicable law, individuals may request access, correction, deletion or restriction by contacting privacy@marketingstudios.in. Identity verification may be required.
User Agreement
Rules for using Konnextions.
Access is granted to the subscribing organisation and its authorised named users under the applicable order form. Accounts may not be shared. The organisation is responsible for lawful calling, consent, number ownership, user administration, endpoint security and use of connected providers.
Subscriptions and capacity
Capacity is purchased in the Agent packs stated in the signed order. Telephony, taxes, onboarding and optional services may be charged separately. Website illustrations do not replace the signed quote.
Availability and changes
Maintenance, security updates and support targets are governed by the applicable order and support schedule. Preview, mock and roadmap features are not production commitments.
Termination
Access may be suspended for security threats, unlawful use, material breach or non-payment, subject to the signed agreement and applicable law.
Acceptable Use Policy
Use calling tools responsibly.
Users must follow applicable telemarketing, consent, do-not-call, recording, privacy and consumer-protection laws in every destination and calling region.
Prohibited use
- Calling without a lawful basis or required consent.
- Ignoring suppression, opt-out or do-not-contact requests.
- Caller-ID spoofing, fraud, harassment or deceptive impersonation.
- Uploading stolen, unlawfully obtained or excessive personal data.
- Attempting to bypass roles, audit trails, rate limits or security controls.
- Using the service for emergency calling unless expressly supported and contracted.
Security overview
Control starts with separation.
- Named accounts and role-based access for Super Admin, Admin, Manager and Agent.
- HTTPS access and client-controlled certificate deployment for on-premises installations.
- Database and internal services not intended for direct Agent-network exposure.
- Audit evidence for administrative and operational changes.
- Encrypted backups with recovery material controlled separately.
- Provider credentials stored server-side, not in public website code.
Report a suspected security issue through the support form using the Security or privacy category. Do not include exploit details that expose active customer data; request a secure exchange channel.
Data Processing overview
Responsibility follows control.
The customer generally determines the purpose and lawful basis for contact-centre data and acts as controller/business where applicable. The contractual roles of Marketing Studios and any subprocessors depend on the selected hosting, support and integration services.
Worldwide launch work
Availability is not a claim that one agreement or calling configuration satisfies every jurisdiction. Before activation in any country, the parties must review applicable privacy, telemarketing, call-recording, consent, retention, data-transfer, number-ownership and telecom-provider rules. This includes national, state, provincial and sector-specific requirements where applicable.
A signed Data Processing Addendum, subprocessor list, retention schedule and any required cross-border mechanism must be finalised for each commercial offering and location.
Rhea assistant
Guidance first. AI later.
Rhea’s initial website version uses a fixed, browser-local knowledge map. It does not call an external language model, create support decisions or replace the Help Centre. Messages are not transmitted by the Rhea widget.
A future production assistant may use a customer-local model and approved local knowledge index. Any external processing option must be opt-in, separately disclosed and disabled by default for customer operational data.