Legal · Governance
Acceptable Use Policy
Enterprise Innovation & Assurance Ecosystem
Effective Date: 24 September 2026 | Last Updated: 24 September 2026
This Acceptable Use Policy governs permitted and prohibited use of PIEDAP, Pion Global's Enterprise Innovation & Assurance Ecosystem, including GRCNest, NexGenQE, DPConsent, PIEStrat, EvalTiq and Talenaise, together with covered applications, APIs, developer interfaces, integrations, AI features, sandboxes, documentation and related services.
Policy at a Glance
| Area | Summary |
|---|---|
| Operator | Pion Global Private Limited. |
| Ecosystem | PIEDAP, including GRCNest, NexGenQE, DPConsent, PIEStrat, EvalTiq and Talenaise. |
| Who Must Comply | Customers, authorized users, administrators, employees, contractors, developers, API users, partners, trial users and any person or system accessing the Services through an authorized account or credential. |
| Core Rule | Use PIEDAP only for lawful, authorized business purposes and within the rights, roles, subscription limits and permissions granted to you. |
| AI and Automation | AI, agents, APIs, bots and automation must be used responsibly, with appropriate human oversight and without bypassing controls, creating harmful content, making prohibited high-impact decisions or abusing shared resources. |
| Security Testing | Do not scan, probe, exploit or conduct penetration testing against PIEDAP without prior written authorization. Good-faith vulnerability reports should follow the Responsible Vulnerability Disclosure process. |
| Customer Data | Use only data you are authorized to process. Do not access, scrape, export or expose another customer's data or confidential information. |
| Enforcement | Pion Global may investigate, restrict, suspend or terminate access where reasonably necessary to protect PIEDAP, customers, users, third parties or legal and contractual obligations. |
| Precedence | Signed customer agreements and applicable platform-specific terms may impose stricter requirements and prevail for their subject matter. |
1.Purpose and Scope
This Acceptable Use Policy ("AUP") defines the rules for safe, lawful and responsible use of PIEDAP and its connected services. It is intended to protect the security, availability, integrity and trustworthiness of the ecosystem while enabling customers, users, developers and partners to use PIEDAP for legitimate enterprise purposes.
This AUP applies to the PIEDAP website, platform applications, customer environments, APIs, webhooks, connectors, developer and partner interfaces, sandboxes, trial and proof-of-concept environments, AI-assisted capabilities, documentation and other services where this AUP is referenced or incorporated into an agreement.
1.1 PIEDAP Ecosystem Coverage
| Platform | Authorized Purpose | Additional Acceptable-Use Focus |
|---|---|---|
| GRCNest | Governance, risk, compliance, controls, audits, evidence and assurance. | Do not use compliance outputs to misrepresent certification, regulatory approval or audit conclusions, and do not upload evidence you are not authorized to disclose. |
| NexGenQE | Quality engineering, testing, automation, release assurance and engineering intelligence. | Do not test third-party systems without authorization, create malicious test payloads, or use automation in a way that disrupts systems or violates third-party rights. |
| DPConsent | Consent, preferences and privacy operations. | Do not fabricate consent, alter consent evidence improperly, impersonate Data Principals, or use the platform to circumvent privacy or consent obligations. |
| PIEStrat | Project, portfolio, program and delivery management. | Do not manipulate project, risk, resource or governance data to mislead stakeholders, hide material issues or bypass organizational controls. |
| EvalTiq | Audit, discovery, gap, maturity and survey assessments. | Do not falsify evidence, ratings or responses, misrepresent assessment results, or use assessments as an unauthorized substitute for independent certification or audit. |
| Talenaise | 360-degree competency, skills, leadership and performance evaluation. | Do not use the platform for unlawful discrimination, covert monitoring or prohibited solely automated employment decisions. Use appropriate notice, confidentiality and human review. |
1.2 Relationship to Other Terms
This AUP forms part of the PIEDAP contractual framework and should be read with the PIEDAP Terms of Use, Privacy Policy, Responsible Vulnerability Disclosure Policy, Data Processing Agreement where applicable, and any signed customer, subscription, order, security, developer, partner or platform-specific agreement. If another applicable written agreement imposes stricter acceptable-use requirements, the stricter requirement applies for that subject matter.
2.Permitted Use
You may use PIEDAP only for lawful and authorized enterprise purposes within the scope of your account, role, subscription, license, trial, partner authorization or written agreement.
- Use only accounts, environments, APIs, modules, features and data sets that you are authorized to access.
- Follow documented security, authentication, rate-limit, integration and technical requirements.
- Use Customer Data, personal data and confidential information only where you have a lawful basis, authority and appropriate organizational approval.
- Maintain appropriate human review for AI-assisted recommendations, assessments, risk outputs, compliance conclusions, talent insights and other material decisions.
- Comply with applicable laws, regulations, contracts, professional obligations and your organization's internal policies.
- Cooperate with reasonable security, abuse-prevention, incident-response and compliance measures.
3.General Prohibited Conduct
You must not use PIEDAP, directly or indirectly, for conduct that is unlawful, harmful, fraudulent, abusive, deceptive, disruptive or inconsistent with the intended enterprise use of the Services.
- Violate applicable law, regulation, court order, contractual restriction or third-party right.
- Facilitate fraud, theft, deception, harassment, extortion, abuse, unlawful surveillance or other harmful conduct.
- Circumvent regulatory, audit, security, privacy, governance or organizational controls.
- Knowingly submit materially false, fabricated or misleading information where accuracy is important to an assessment, audit, consent record, risk decision, project report or talent evaluation.
- Use PIEDAP to facilitate activities that Pion Global reasonably determines present a material threat to the security, integrity, availability or lawful operation of the Services.
4.Security and System Abuse
You must not interfere with, compromise, bypass or attempt to defeat PIEDAP security or the security of any customer, user, partner, integration or connected system.
- Attempt unauthorized access to accounts, tenants, data, APIs, infrastructure, secrets, keys, tokens, administrative functions or connected systems.
- Bypass authentication, authorization, tenant isolation, role-based access, license controls, rate limits, security controls or usage restrictions.
- Introduce malware, ransomware, spyware, destructive code, credential-stealing content or other harmful components.
- Conduct denial-of-service activity, traffic flooding, resource exhaustion, credential stuffing or other disruptive activity.
- Probe, scan, exploit or perform vulnerability assessment, penetration testing, red-team activity or security research without prior written authorization.
- Attempt to obtain source code, secrets, model configuration, system prompts, security rules or internal architecture through exploitation, prompt injection, jailbreak techniques or other unauthorized methods.
- Interfere with logs, audit trails, security alerts, evidence records or monitoring intended to protect the Services or customers.
5.Data, Privacy and Confidentiality
You are responsible for ensuring that data submitted to PIEDAP is lawfully obtained, appropriately classified and authorized for the intended processing.
- Do not upload or process personal, confidential, regulated, proprietary or sensitive information unless you are authorized to do so and appropriate contractual and security controls are in place.
- Do not access, export, disclose, scrape, infer, re-identify or attempt to obtain data belonging to another customer, user or organization.
- Do not use PIEDAP to violate privacy rights, confidentiality duties, data localization requirements, consent requirements or data-subject rights.
- Do not submit passwords, private keys, authentication secrets or unnecessary highly sensitive data into free-text, prompt or AI fields unless the feature and agreement explicitly support that use.
- Do not use anonymization, aggregation or de-identification features to intentionally re-identify individuals or circumvent privacy protections.
- Do not retain, download or redistribute data beyond the permissions, retention period or business need authorized by your organization and applicable agreement.
6.AI, Agentic Automation and Automated Decision-Making
PIEDAP may provide AI-assisted features, agents, copilots, recommendations, summaries, classifications, predictions and generated content. These capabilities are intended to support, not replace, accountable enterprise judgment.
- Do not use AI features to create malware, phishing, social-engineering content, credential theft, unlawful surveillance, deception or other harmful activity.
- Do not intentionally manipulate prompts, context, documents, connectors or agent workflows to bypass policy, access controls or safety restrictions.
- Do not represent AI-generated content, recommendations or predictions as independently verified facts where verification is reasonably required.
- Do not use PIEDAP AI as the sole basis for a legally prohibited or otherwise inappropriate high-impact decision, including employment, disciplinary, eligibility, financial, regulatory or similar decisions, without required human review and safeguards.
- Do not use AI functionality to discriminate unlawfully or to infer sensitive characteristics in a manner prohibited by law or contract.
- Do not use customer data, platform outputs or AI features to train or improve an external model where doing so would violate confidentiality, intellectual property, privacy or contractual obligations.
- You remain responsible for reviewing outputs, validating material conclusions and ensuring that downstream actions are appropriate for the relevant context.
7.APIs, Developer Portal, Bots and Automated Access
Automated access is permitted only through approved interfaces and within documented or contractually authorized limits.
- Use only issued API keys, OAuth credentials, service accounts and tokens, and protect them against unauthorized disclosure.
- Do not exceed documented or contracted rate limits, concurrency limits, quotas, storage limits or other technical controls.
- Do not scrape webpages or user interfaces, automate browser interactions or harvest information where an authorized API or export mechanism is required or where such activity is prohibited.
- Do not attempt to discover undocumented endpoints, hidden parameters, internal APIs or privileged functions for unauthorized purposes.
- Do not use APIs to create competing data sets, replicate substantial platform functionality, or systematically extract platform content except where expressly permitted.
- Validate webhook origins, secure integration secrets and follow published integration-security requirements.
- Bots, agents and integrations must identify and operate under an authorized customer or service account and remain attributable to the responsible organization.
8.Excessive Use and Shared-Service Protection
PIEDAP may apply technical safeguards to protect service quality and fair access across shared infrastructure. You must not intentionally consume resources in a way that materially degrades the Services or other customers' use.
- Do not generate excessive requests, workloads, data transfers, background jobs or automation that unreasonably burden shared systems.
- Do not circumvent storage, user, transaction, API, AI-token, compute, environment or other subscription limits.
- Do not run stress tests, load tests or high-volume synthetic workloads against production systems without prior written authorization.
- Do not create multiple accounts, tenants or credentials to evade limits, restrictions, suspension or billing controls.
- Pion Global may throttle, queue, restrict or temporarily disable abusive workloads where reasonably necessary to protect service stability.
9.Intellectual Property, Reverse Engineering and Competitive Misuse
- Do not reverse engineer, decompile, disassemble or attempt to derive non-public source code, models, algorithms, prompts, schemas or proprietary design except where applicable law expressly prohibits such restriction.
- Do not copy, modify, distribute, sublicense, sell or create unauthorized derivative works of PIEDAP software, documentation, templates, assessment content or proprietary materials.
- Do not remove, obscure or alter copyright, trademark, confidentiality or other proprietary notices.
- Do not use PIEDAP content, documentation, outputs or interfaces to benchmark, train or build a competing service where prohibited by contract or applicable law.
- Respect third-party intellectual property rights when uploading code, documents, assessments, evidence, media or other content.
10.Communications, Content and Collaboration Misuse
Where PIEDAP enables notifications, surveys, messages, collaboration, invitations, comments or external communications, you must use those functions responsibly.
- Do not send spam, phishing, deceptive invitations, unsolicited bulk communications or communications that violate applicable marketing or privacy laws.
- Do not upload or distribute unlawful, malicious, defamatory, infringing, threatening or abusive content.
- Do not impersonate another individual, organization, regulator, auditor, customer, partner or Pion Global representative.
- Do not falsify authorship, timestamps, evidence provenance, approvals, acknowledgements, consent records or audit history.
- Do not use collaboration or survey functionality to harass, retaliate against or improperly pressure employees, respondents, Data Principals or other individuals.
11.Platform-Specific Responsible Use
11.1 GRCNest
- Use compliance mappings, control recommendations and AI-assisted insights as decision support and validate them against applicable laws, standards, contractual obligations and professional judgment.
- Do not claim that use of GRCNest itself constitutes certification, regulatory approval, legal compliance or an independent audit opinion.
- Do not alter or fabricate evidence, control testing results, approvals, audit history or risk information to create a misleading compliance posture.
11.2 NexGenQE
- Conduct testing, automation and security-related validation only against systems you own or are authorized to test.
- Do not use test-generation or automation features to create harmful exploits, destructive payloads or unauthorized attacks.
- Respect source-code, test-data, production-data and third-party intellectual property restrictions.
11.3 DPConsent
- Do not fabricate, backdate, suppress, alter or misrepresent consent, withdrawal, preference or notice records.
- Do not impersonate a Data Principal or submit rights/consent actions without appropriate authorization.
- Do not configure consent interfaces or workflows to intentionally mislead individuals or make withdrawal materially harder than the corresponding consent action where prohibited by law.
11.4 PIEStrat
- Do not falsify project status, risk, resource, dependency, milestone or KPI data to conceal material delivery issues or mislead stakeholders.
- AI estimates, risk signals and change-impact outputs must be reviewed before being used for material commitments or decisions.
- Use integrations with project, engineering and enterprise systems only within authorized scopes.
11.5 EvalTiq
- Do not manipulate assessment criteria, evidence, scoring, respondent data or results to create predetermined or misleading outcomes.
- Respect respondent confidentiality and any anonymity commitments communicated for surveys or assessments.
- Do not present EvalTiq assessment results as independent certification, accreditation or assurance unless a qualified independent process actually supports that conclusion.
11.6 Talenaise
- Provide appropriate notice and maintain confidentiality for 360-degree feedback, competency and performance evaluation data.
- Do not use Talenaise for unlawful discrimination, retaliation, covert surveillance or prohibited profiling.
- Do not rely solely on automated or AI-generated outputs for high-impact employment decisions where human review, explanation or additional safeguards are required.
12.External Integrations and Third-Party Services
PIEDAP may connect with customer systems and third-party services. You are responsible for having authority to connect those services and for configuring scopes, credentials, data flows and permissions appropriately.
- Do not connect a third-party account, repository, cloud environment, CRM, HR system, ITSM tool or other service without authorization.
- Do not use integrations to copy or move data in violation of third-party terms, data-protection obligations, confidentiality requirements or licensing restrictions.
- You are responsible for external-service credentials, permission scopes and configuration under your control.
- Third-party services remain subject to their own terms, availability, security and privacy practices.
13.Partner, Marketplace and Ecosystem Conduct
Partners, integrators, resellers, solution providers and developers participating in the PIEDAP ecosystem must comply with this AUP and any applicable partner or developer terms.
- Do not claim partnership status, certification, authorization, endorsement or technical compatibility beyond what Pion Global has expressly approved.
- Do not misuse PIEDAP names, trademarks, logos, documentation or customer references.
- Do not use partner access to obtain customer data, platform information or competitive intelligence beyond the authorized engagement.
- Maintain appropriate confidentiality, security and data-protection controls for customers and Pion Global information.
- Do not introduce integrations, extensions or services that materially compromise platform security, availability, integrity or customer trust.
14.Security Research and Vulnerability Reporting
PIEDAP welcomes responsible reporting of suspected security vulnerabilities. However, this AUP does not grant permission to conduct security testing. Security research, scanning, exploitation, penetration testing or similar activity requires prior written authorization unless expressly permitted under Pion Global's published Responsible Vulnerability Disclosure Policy.
- If you discover a suspected vulnerability, stop any activity that could access, alter, destroy or expose data beyond what is reasonably necessary to confirm the issue.
- Do not exfiltrate data, pivot to other systems, establish persistence, conduct denial-of-service testing or publicly disclose an unresolved vulnerability without coordination.
- Report vulnerabilities through the published vulnerability-reporting channel or to [email protected] until a dedicated security mailbox is published.
- A vulnerability report does not create an entitlement to payment or a bug bounty unless Pion Global has separately announced a reward program.
15.Customer and Administrator Responsibilities
Customers and account administrators are responsible for reasonable governance of their users, integrations, credentials and data within their control.
- Provision access according to least privilege and remove or update access promptly when roles change.
- Configure authentication, SSO, MFA, API credentials, integration scopes and security settings appropriately for the customer environment.
- Educate authorized users regarding this AUP and applicable customer policies.
- Investigate suspected misuse by users under the customer account and cooperate with reasonable Pion Global security inquiries.
- Maintain appropriate backup, retention, classification and export practices for Customer Data where those controls are the customer's responsibility.
- Ensure contractors, partners and service accounts using customer credentials comply with this AUP.
16.Monitoring, Detection and Investigation
Pion Global may use service telemetry, security logs, authentication information, API and usage metadata, abuse-detection mechanisms and other proportionate controls to operate, secure and protect PIEDAP and to investigate suspected violations. Monitoring will be conducted in accordance with applicable law, the PIEDAP Privacy Policy and contractual obligations.
Pion Global does not rely on this AUP as a general right to inspect Customer Content without limit. Where review of specific content is reasonably necessary to investigate security, abuse, legal or contractual issues, Pion Global will seek to limit access to what is reasonably necessary and will apply applicable confidentiality and privacy obligations.
17.Enforcement and Consequences
Pion Global may take proportionate action where it reasonably believes a violation has occurred or an immediate risk exists. Depending on severity, urgency, recurrence and contractual terms, actions may include:
- Warning the customer, administrator or user and requesting corrective action.
- Throttling or restricting a workload, integration, API key, feature, account or environment.
- Removing or isolating malicious or prohibited content where reasonably necessary.
- Temporarily suspending access while a security, abuse or legal issue is investigated.
- Terminating access or Services for material or repeated violations, subject to applicable contract terms.
- Preserving relevant records, notifying affected customers or third parties, or reporting matters to authorities where required or permitted by law.
- Seeking legal or equitable remedies where necessary to protect Pion Global, customers or third parties.
18.Reporting Suspected Misuse
If you become aware of suspected misuse, unauthorized access, data exposure, abusive automation or another violation of this AUP, please report it promptly. Include sufficient information to identify the affected account, environment, activity and timing without sending unnecessary sensitive data.
| Issue | Reporting Route |
|---|---|
| General AUP or abuse report | [email protected] |
| Security vulnerability | Use the published Responsible Vulnerability Disclosure channel; until a dedicated security mailbox is published, contact [email protected] and identify the message as a security report. |
| Customer account issue | Contact your organization administrator and the applicable PIEDAP support channel. |
| Privacy concern | Use the PIEDAP Privacy Request / grievance channel or the contact method stated in the PIEDAP Privacy Policy. |
19.Exceptions and Written Authorization
An activity otherwise restricted by this AUP is permitted only if Pion Global has provided specific prior written authorization or the activity is expressly allowed by an applicable signed agreement, documented feature or published policy. Authorization may be subject to scope, timing, environment, testing, rate, confidentiality, security and reporting conditions.
20.Changes to this AUP
Pion Global may update this AUP to reflect changes in the PIEDAP ecosystem, law, security practices, platform functionality, APIs, AI capabilities or abuse patterns. The updated version will be published with a revised "Last Updated" date. Where required by an applicable agreement or law, Pion Global will provide additional notice of material changes.
21.Contact
Questions about this Acceptable Use Policy may be directed to:
| Contact | Details |
|---|---|
| Organization | Pion Global Private Limited |
| PIEDAP | www.pionglobal.com |
| [email protected] | |
| Telephone | +91 80 2679 0999 |
| Business Address | 48, 4th B Main, Classic Paradise Layout, Begur Road, Bengaluru, Karnataka, India |