Legal

Privacy Policy

This Privacy Policy describes AURIX SHIELD's current privacy practices. Before public launch, the policy should be reviewed against the final production data flows and applicable legal requirements.

Effective Date: September 28, 2026

AURIX SHIELD is built to help developers and businesses understand and manage security issues across websites, software, and GitHub repositories.

Because the platform works with account information, security findings, repository information, scan results, and AI-assisted security context, privacy is an important part of how we build the product.

This Privacy Policy explains what information AURIX SHIELD may collect, how we use it, when it may be shared, how we protect it, and the choices available to you.

1. Who This Policy Applies To

This Privacy Policy applies to information collected through:

  • The AURIX SHIELD website
  • The AURIX SHIELD application
  • AURIX SHIELD accounts
  • Security scanning features
  • GitHub Security features
  • Monitoring features
  • Fix & Verify workflows
  • AURIX AI and Ask AURIX
  • Contact and support interactions
  • Other services that link to this Privacy Policy

AURIX SHIELD is a security product. Some information processed by the platform may relate to software, repositories, websites, security findings, source-code files, dependencies, or other technical security data.

2. Information We Collect

We collect information needed to operate AURIX SHIELD, provide security functionality, protect the platform, communicate with users, and improve the service.

The information we collect depends on how you use AURIX SHIELD.

2.1 Account Information

When you create or use an AURIX SHIELD account, we may collect information such as:

  • Email address
  • Account identifier
  • Authentication information
  • Account and profile information you provide
  • Subscription or plan information
  • Account settings
  • Security-related account state

Authentication information is used to securely identify your account and provide access to authorized parts of the platform.

3. Website Security Information

When you use AURIX SHIELD to scan an authorized website or target, the platform may process technical information required to perform the security analysis.

This may include:

  • Target URL
  • Host information
  • Discovered endpoints
  • HTTP response information
  • Security headers
  • Scan metadata
  • Scanner results
  • Security findings
  • Evidence associated with findings
  • Severity information
  • Scan status
  • Scan history
  • Finding comparison information

The exact information produced depends on the target and the security engines involved.

Website security scanning is intended for authorized security testing. Users must be authorized to verify and scan domains they submit.

3A. Domain Verification Information

When a user verifies a domain or website with AURIX SHIELD, the platform may process information necessary to establish that the user is authorized to verify and manage the target.

Depending on the verification method supported by the service, this may include:

  • Domain name
  • Website/target URL
  • Verification status
  • Verification method
  • Verification-related records or tokens
  • DNS or HTTP verification information used to establish control
  • Verification result
  • Verification timestamps
  • Related account/target identifiers
  • Technical information necessary to complete or troubleshoot verification

This information is used to:

  • establish or confirm control/authorization of the target
  • associate the verified domain with the user's AURIX SHIELD account
  • enable website security scanning and related security features
  • maintain verification state and history
  • prevent unauthorized use of another party's domain
  • troubleshoot verification failures
  • maintain security and reliability of the service

Domain verification does not itself grant ownership of a domain. AURIX SHIELD uses verification information to establish authorization for the requested service.

4. GitHub Security Information

When you connect or use GitHub Security functionality, AURIX SHIELD may process information associated with the repositories you authorize for security analysis.

This may include:

  • GitHub account information required for authorization
  • Repository owner and repository name
  • Repository metadata
  • Repository files needed for security analysis
  • Source-code information processed by security engines
  • Dependency information
  • Secret-detection results
  • Code analysis results
  • Security findings
  • File paths
  • Rule identifiers
  • Evidence
  • Finding fingerprints
  • Verification information
  • Scan results and history

AURIX SHIELD uses this information to perform the security analysis requested by the user and provide the resulting security findings.

5. Security Findings

AURIX SHIELD maintains security findings so that detected issues can be investigated, verified, and tracked over time.

A finding may contain information such as:

  • Finding identifier
  • Severity
  • Scanner engine
  • Detection rule
  • Target
  • Repository
  • File
  • Evidence
  • Finding fingerprint
  • Finding state
  • Verification state
  • Scan history
  • Timestamps

Persistent findings allow AURIX SHIELD to distinguish changes such as:

  • NEW
  • EXISTING
  • REAPPEARED
  • RESOLVED
  • CHANGED

This information is part of the security functionality of the platform.

6. Fix & Verify Information

When you use Fix & Verify, AURIX SHIELD may process information associated with the original finding and its verification workflow.

This can include:

  • Finding identity
  • Scanner engine
  • Rule identifier
  • Repository
  • File
  • Verification target
  • Verification method
  • Verification result
  • Verification history

Verification information is used to determine whether the original security detection remains present under the applicable verification workflow.

7. Monitoring Information

When you enable monitoring, AURIX SHIELD may process information such as:

  • Monitored target
  • Monitoring state
  • Schedule frequency
  • Scheduled time
  • Timezone
  • Monitoring runs
  • Scan results
  • Finding changes
  • Monitoring history
  • Notification preferences

Monitoring information allows the platform to run and track scheduled security analysis.

8. AURIX AI and Ask AURIX

When you use AURIX AI or Ask AURIX, we may process:

  • Questions and prompts you submit
  • Relevant security findings
  • Scanner information
  • Severity
  • Repository information
  • File information
  • Detection rules
  • Security evidence
  • Verification information
  • Other security context necessary to answer your request

Ask AURIX is designed to use authorized security context to help users understand and investigate security findings.

AI-generated responses are not security verification results.

9. Information From Communications

If you contact AURIX SHIELD, we may receive information contained in your communication.

This may include:

  • Name, if provided
  • Email address
  • Subject
  • Message content
  • Attachments you voluntarily provide
  • Technical information relevant to your support request

Different contact addresses are used for different purposes, including:

Automated security notifications may be sent from:
alerts@aurixshield.com

10. Billing and Subscription Information

If you purchase a paid AURIX SHIELD plan, information necessary to manage the subscription and billing relationship may be processed.

This can include:

  • Plan
  • Subscription status
  • Billing status
  • Transaction-related information
  • Account identifiers
  • Information required to manage payment-related operations

Payment card details should be handled by the applicable payment provider where the payment infrastructure supports that arrangement.

AURIX SHIELD does not need to store complete payment-card credentials merely to provide account subscription functionality.

11. Technical and Usage Information

When you access AURIX SHIELD, technical information may be generated automatically.

This may include:

  • IP address
  • Browser information
  • Device information
  • Operating system
  • Request information
  • Authentication events
  • Security events
  • Error information
  • Performance information
  • Application logs
  • Timestamps

We use this information to operate, secure, troubleshoot, and improve the service.

12. Cookies and Similar Technologies

AURIX SHIELD may use cookies or similar technologies required for:

  • Authentication
  • Session management
  • Security
  • Preferences
  • Product functionality
  • Website analytics where enabled

Cookies that are necessary for the operation of the service may be used to provide requested functionality.

For additional information about cookies and similar technologies, see our Cookie Policy.

13. How We Use Information

We use information collected through AURIX SHIELD for purposes such as:

Providing the Service

To create accounts, authenticate users, operate the platform, and provide requested features.

Security Scanning

To perform website and GitHub security analysis.

Finding Management

To create, store, compare, investigate, and track security findings.

Verification

To perform applicable Fix & Verify workflows.

Monitoring

To operate scheduled security monitoring.

AURIX AI

To provide AI-assisted security investigation and explanations.

Support

To respond to questions and technical issues.

Security

To detect abuse, unauthorized access, attacks, fraud, and other threats against the service.

Reliability

To diagnose errors, monitor performance, and maintain the platform.

Product Improvement

To understand how the service is used and improve its functionality, security, reliability, and user experience.

Legal Compliance

To comply with applicable legal obligations and protect legal rights.

14. How We Do Not Use Security Data

AURIX SHIELD is a security product, so security information may contain sensitive technical information about software and infrastructure.

We do not use security findings simply as marketing content.

We do not intentionally expose one user's private security findings to another user.

Access to security information is subject to the application's authentication and authorization controls.

15. How We Share Information

We may share information with service providers and infrastructure providers that help us operate AURIX SHIELD.

Depending on the service being used, these providers may support areas such as:

  • Authentication
  • Database infrastructure
  • Cloud infrastructure
  • Security scanning
  • AI processing
  • Email delivery
  • Payment processing
  • Monitoring
  • Error reporting
  • Application operations

Service providers receive information only as needed for the services they provide and subject to applicable contractual and security requirements.

16. GitHub Information Sharing

GitHub repository information is used to provide the GitHub Security functionality requested by the user.

We do not treat authorization to scan a repository as permission to publicly disclose that repository's private security information.

Repository security information remains subject to the user's authorization and AURIX SHIELD's access controls.

17. AI Processing

When you use AURIX AI or Ask AURIX, relevant information may be processed by AI infrastructure necessary to generate the requested response.

The information supplied to an AI system may include security context needed to answer your question.

AURIX SHIELD is designed to provide the AI with relevant security context rather than unrelated account information.

Users should avoid intentionally submitting passwords, private keys, API keys, or other secrets into conversational prompts unless the feature specifically requires and securely supports that information.

18. Security

Security is fundamental to AURIX SHIELD because the platform itself processes security-related information.

We use technical and organizational measures designed to protect information against unauthorized access, loss, misuse, alteration, or disclosure.

These measures may include:

  • Authentication
  • Authorization controls
  • Access restrictions
  • Secure communications
  • Security monitoring
  • Logging
  • Infrastructure security controls
  • Data-access controls
  • Secure development practices

No internet service can guarantee absolute security.

If you believe you have discovered a security issue involving AURIX SHIELD, contact:
security@aurixshield.com

19. Data Retention

We retain information for as long as reasonably necessary to:

  • Provide the requested service
  • Maintain security findings and history
  • Provide monitoring functionality
  • Maintain account functionality
  • Meet contractual obligations
  • Comply with legal requirements
  • Resolve disputes
  • Enforce agreements
  • Protect the service

Retention periods may differ depending on the type of information and the purpose for which it is processed.

We will not state fixed retention periods until the production retention configuration has been formally finalized.

20. Account Deletion

If you want to request deletion of your AURIX SHIELD account or associated personal information, contact:
privacy@aurixshield.com

Some information may need to be retained where required for legal, security, fraud-prevention, dispute-resolution, or other legitimate purposes.

Deleting an account does not necessarily require immediate deletion of every record where retention is legally or operationally necessary.

21. Your Privacy Rights

Depending on where you live and which privacy laws apply to you, you may have rights concerning your personal information.

These may include rights to:

  • Access personal information
  • Request correction of inaccurate information
  • Request deletion
  • Request information about processing
  • Object to certain processing
  • Restrict certain processing
  • Withdraw consent where processing is based on consent
  • Request portability where applicable
  • Opt out of certain forms of sale or sharing where applicable
  • Lodge a complaint with a relevant privacy authority

The exact rights available to you depend on applicable law.

For example, California privacy law provides qualifying consumers with rights including access, deletion, correction, and certain opt-out rights. (California DOJ)

India's Digital Personal Data Protection Act establishes requirements concerning notice, consent, processing, and data-principal rights, subject to the Act's applicability and commencement framework. (MeitY)

22. How to Exercise Privacy Rights

For privacy-related requests, contact:
privacy@aurixshield.com

Please describe:

  • The request you are making
  • The email address associated with your account, if applicable
  • Enough information for us to understand and verify the request

We may need to verify your identity before completing certain requests to protect account security and prevent unauthorized disclosure.

23. Children's Privacy

AURIX SHIELD is designed as a professional security platform and is not directed toward children.

We do not knowingly design the service to collect personal information from children for purposes unrelated to providing the service.

If you believe a child has provided personal information to AURIX SHIELD in circumstances where it should not have been collected, contact:
privacy@aurixshield.com

24. International Data Processing

AURIX SHIELD may use service providers or infrastructure located in countries different from your country of residence.

As a result, information may be processed internationally.

Where applicable law requires safeguards for international transfers, we intend to use appropriate mechanisms and contractual protections.

25. Third-Party Services

AURIX SHIELD may rely on third-party infrastructure and service providers to operate parts of the platform.

Examples can include services supporting:

  • Authentication
  • Database operations
  • Cloud infrastructure
  • AI processing
  • Email delivery
  • Payment processing
  • Security analysis

Third-party services may have their own privacy policies and terms.

Where appropriate, users should review the privacy practices of relevant third-party services.

26. Security Scanning and User Responsibility

AURIX SHIELD processes technical information because security analysis requires it.

Users are responsible for ensuring that they are authorized to scan websites, repositories, systems, and other targets submitted to AURIX SHIELD.

Do not submit information to AURIX SHIELD that you do not have permission to process.

27. Changes to This Privacy Policy

We may update this Privacy Policy when our services, data practices, legal obligations, or privacy controls change.

When we make material changes, we may provide additional notice where required.

The updated version will be published on this page with a revised effective date.

28. Contact Us About Privacy

For privacy questions, requests, or concerns:
privacy@aurixshield.com

For general questions:
contact@aurixshield.com

For product support:
support@aurixshield.com

For security concerns:
security@aurixshield.com


AURIX SHIELD

Security for the software AI makes easier to build.

Detect → Explain → Fix → Verify → Monitor