Lawful and authorised
Use Rudrriv resources only for legitimate purposes, within approved access, agreed scope and applicable law.
Rudrriv Trust Center
Responsible use of Rudrriv services
Rudrriv services must be used lawfully, securely and only for authorised business purposes. These standards help prevent misuse while keeping legitimate work clear and practical.
- Authorised access only
- No harmful or deceptive activity
- Proportionate enforcement
- Clear reporting route
Responsible-use modelAuthorise · Protect · Respect · Report
Active standard
Authorised access
Protected data
Respectful use
Rapid reporting
Designed to reduce misuse and service risk
Core principles
A clear standard for responsible use
These principles apply across Rudrriv’s website, customer engagements, project tools, hosted environments, communications, integrations and deliverables.
Secure by default
Protect credentials, follow access controls and avoid conduct that could expose systems, data or other users to risk.
Respectful and fair
Do not use Rudrriv services to deceive, exploit, harass, discriminate against or unlawfully harm another person.
Transparent
Represent identity, authority, content, data sources and intended use honestly when working with Rudrriv.
Proportionate
Use technical resources, automation and data access in a reasonable way that does not disrupt service or bypass safeguards.
Accountable
Customers remain responsible for authorised users, instructions, content, permissions and legal approvals connected to their use.
Practical rules
What responsible use looks like—and what is not permitted
The examples below are designed to be direct. They are not exhaustive, and the full legal policy, contract and third-party platform rules may add requirements.
Accounts, identity and access
Use only approved accounts and permissions.
Expected use
- Access systems through assigned credentials and approved channels.
- Use permissions only for the authorised project, role and duration.
- Report suspected compromise, unauthorised access or mistaken permissions promptly.
Not permitted
- Credential sharing, impersonation, account takeover or access outside approved scope.
- Bypassing authentication, rate limits, security controls or technical restrictions.
- Testing, scanning or exploiting systems without written authorisation.
Security and system integrity
Do not introduce threats or disrupt operations.
Expected use
- Use supported integrations and documented technical methods.
- Follow secure configuration, patching and data-transfer instructions.
- Submit good-faith security reports without accessing unnecessary data.
Not permitted
- Malware, ransomware, destructive code, botnets, denial-of-service or cryptomining.
- Interference with availability, monitoring, backups, logs or another user’s service.
- Actions intended to conceal malicious activity or obstruct investigation.
Communications and marketing
Communicate with consent, accuracy and respect.
Expected use
- Send relevant communications to lawfully obtained contacts.
- Use accurate sender identity, claims, pricing and unsubscribe methods.
- Follow platform rules, campaign approvals and applicable marketing law.
Not permitted
- Spam, phishing, spoofing, deceptive promotions or fabricated endorsements.
- Purchased, harvested or unlawfully obtained contact lists.
- Circumvention of opt-outs, complaints, platform review or delivery controls.
Data, privacy and confidentiality
Use data only for approved and lawful purposes.
Expected use
- Share the minimum information required for the agreed service.
- Provide necessary notices, permissions and customer instructions.
- Use approved storage, transfer, retention and deletion methods.
Not permitted
- Unlawful surveillance, doxxing, stalking or collection of sensitive information.
- Uploading personal, confidential or regulated data without authority or safeguards.
- Re-identification, unauthorised profiling or use beyond the disclosed purpose.
Content and intellectual property
Use only content you are entitled to provide or publish.
Expected use
- Use original, licensed, public-domain or otherwise authorised materials.
- Maintain required credits, permissions and usage restrictions.
- Identify third-party assets and brand rules before production or publication.
Not permitted
- Copyright, trademark, design, trade-secret or publicity-right infringement.
- Counterfeit, plagiarised, deceptive or unlawfully copied content.
- Removal of rights notices, attribution, watermarking or access restrictions.
AI, automation and data extraction
Use automation with oversight, permission and appropriate limits.
Expected use
- Use approved automation for defined business tasks and reviewed outputs.
- Respect robots directives, API terms, licences and technical limits.
- Disclose material AI use where required by contract, law or customer policy.
Not permitted
- Automated abuse, mass account creation, scraping circumvention or resource exhaustion.
- Using AI to facilitate fraud, malware, impersonation or unlawful discrimination.
- Submitting restricted data to tools or models without permission and safeguards.
People, safety and protected groups
Do not use services to exploit, threaten or harm people.
Expected use
- Create lawful content and services designed with user safety in mind.
- Apply suitable moderation, age controls and escalation for higher-risk audiences.
- Report credible threats, exploitation or harmful material promptly.
Not permitted
- Threats, harassment, exploitation, trafficking or incitement of violence.
- Child sexual abuse or exploitation material, grooming or sexualisation of minors.
- Hateful abuse, non-consensual intimate content or instructions causing serious harm.
Regulated and high-risk activity
Disclose special requirements before work begins.
Expected use
- Discuss regulated requirements during scoping and contracting.
- Use qualified reviewers, approvals and controls where the engagement requires them.
- Maintain licences, notices, records and risk ownership required for the activity.
Not permitted
- Using Rudrriv to evade sanctions, export controls or legal restrictions.
- Unapproved activity involving weapons, illegal drugs, gambling, financial crime or dangerous goods.
- Presenting Rudrriv deliverables as licensed medical, legal, financial or regulatory advice when they are not.
Unsure whether a planned activity is allowed?
Request a use review
Ask before starting. Early review is especially important for security testing, high-volume automation, regulated data, sensitive audiences or unusual integrations.
Shared responsibility
Clear ownership reduces uncertainty
Responsible use depends on both Rudrriv and its customers. Contracts and service scopes may allocate additional responsibilities for specific systems, data or deliverables.
Customer responsibilities
- Provide accurate instructions, authority and lawful source materials.
- Control authorised users and remove access when no longer required.
- Obtain licences, notices, consents and approvals relevant to the intended use.
- Review deliverables before publication, deployment or business reliance.
- Inform Rudrriv about regulated data, high-risk audiences or unusual technical activity.
- Cooperate with incident, abuse and policy investigations.
Rudrriv responsibilities
- Communicate applicable restrictions and material service conditions.
- Use proportionate safeguards, access controls and escalation paths.
- Assess credible abuse or security reports in good faith.
- Apply restrictions based on risk, evidence, contract and applicable law.
- Protect confidential information during review and investigation.
- Provide a reasonable route to ask questions or request review.
Review and enforcement
Reports are assessed by risk, evidence and impact
Rudrriv may take urgent protective action where delay could create material security, legal, service or user-safety risk. Final action is intended to be proportionate to the verified circumstances.
Receive and triage
Rudrriv reviews the reported conduct, affected service, urgency, available evidence and potential impact.
Assess and contain
Where appropriate, access may be limited, harmful material isolated or additional information requested while facts are verified.
Decide proportionately
The response may range from guidance or correction to removal, suspension, termination or referral, depending on severity and risk.
Close and improve
Material cases may result in corrective actions, control changes, retained evidence, customer communication or lessons learned.
Policy relationship
This page explains the standard. The legal policy provides the detailed terms.
The Trust Center overview is designed for fast customer understanding. The complete Acceptable Use Policy covers scope, prohibited activities, investigation, enforcement, reporting, review, responsibility and governing terms in greater detail.
- The signed customer agreement takes priority where it contains specific service terms.
- Applicable law and third-party platform rules continue to apply.
- Written approval may add safeguards but cannot authorise unlawful activity.
- Last reviewed: July 2026.
Recognised references
Grounded in widely used security and accountability principles
Rudrriv’s acceptable-use approach is informed by recognised security guidance, customer obligations, service-provider rules and applicable law.
ISO/IEC 27001:2022
Supports risk-based access, asset protection, incident handling and accountability principles.
NIST Cybersecurity Framework 2.0
Provides recognised outcomes for governance, protection, detection, response and recovery.
OWASP security guidance
Informs expectations concerning authorised testing, secure development and common application risks.
Applicable laws and provider rules
Use must also comply with relevant laws, contracts, platform terms and third-party acceptable-use requirements.
References describe alignment principles only. They do not represent certification, independent attestation or regulatory approval unless Rudrriv separately publishes current evidence.
Who must follow Rudrriv’s acceptable-use requirements?
The requirements apply to visitors, customers, authorised users, contractors, partners and any person using Rudrriv websites, accounts, communications, systems, project environments, deliverables or professional services. Customers are responsible for people they authorise to use Rudrriv resources.
Is this Trust Center page the complete legal policy?
No. This page is a practical overview intended to make Rudrriv’s expectations easy to understand. The full Acceptable Use Policy, applicable contract, service terms and third-party platform rules govern where more detailed or binding terms are required.
Can Rudrriv approve an activity that would otherwise be restricted?
Some activities may be considered when they are lawful, clearly scoped, technically safe and approved in writing. Approval may require additional controls, specialist review, contractual terms, evidence of authority or limits on data and system access. Rudrriv cannot approve unlawful conduct or override a third party’s rules.
Can I conduct a security test against a Rudrriv system?
Only with prior written authorisation that defines the systems, methods, dates, contacts and safety limits. Unauthorised scanning, exploitation, social engineering, service disruption or access to unnecessary data is prohibited, even when described as research.
How should a suspected violation be reported?
Email support@rudrriv.com with the affected URL, account or service, a factual description, relevant dates, supporting evidence and the potential impact. Do not include unnecessary personal data, malicious files or confidential information unless Rudrriv provides a suitable channel.
What action can Rudrriv take after a violation?
Depending on urgency and severity, Rudrriv may provide guidance, request correction, remove or restrict content, limit functionality, suspend access, terminate an engagement, preserve evidence, notify affected providers or cooperate with lawful requests from competent authorities.
Will every report result in suspension?
No. Rudrriv aims to act proportionately based on verified facts, legal duties, contractual rights, technical risk, user safety, recurrence and the customer’s cooperation. Urgent restrictions may be applied before a full review when delay could create material harm.
How does this page apply to customer content?
Customers remain responsible for the legality, accuracy, rights, permissions and intended use of content and data they provide. Rudrriv may decline, pause or remove work that creates material legal, safety, security or platform risk.
Does this page mean Rudrriv is certified against the listed frameworks?
No. The frameworks are recognised references that inform the principles described here. They do not represent certification, regulatory approval or independent assurance unless Rudrriv separately publishes current evidence.
Where can I ask whether a planned use is permitted?
Contact support@rudrriv.com before beginning the activity. Include the service involved, intended users, data categories, integrations, automation level, jurisdictions and any regulated or higher-risk characteristics so the request can be assessed accurately.
Raise a concern or review a planned use before it creates risk.
Contact Rudrriv with a factual description of the service, activity, data, audience and potential impact. Avoid sending passwords, live malicious files or unnecessary personal information by email.