Kyndrava Privacy Policy
Kyndrava is developed with security as its core purpose; daily social-media and game settings are additional features. A patent application is pending in Japan. This policy applies across operating systems to apps and services offered as Kyndrava, including editions for Apple environments (iOS, iPadOS and macOS), Android, Microsoft Windows and other environments where offered. Actual platform availability, features and data handling depend on the product and edition.
The following describes free editions that process app data on the device. It is not limited to one operating system or build number. Differences by feature or plan are identified by scope; enterprise and contract services are described separately below.
Security-record integrity checks
At startup, the apps check the on-device security ledger and verify existing records using timestamps, local references, the preceding record’s hash and authentication information. Authentication keys and verification anchors are kept in protected OS storage. Records that cannot be verified are marked unverified and are not sent to AURA for verification. These checks concern Kyndrava’s own on-device records.
On-device information and purposes
The apps store the display language, a randomly generated local reference, daily social-media and game settings, selections, save times, and local integrity records on the device to save, reload, and verify settings. The random reference is not a hardware identifier. Details such as selected targets and enforcement status depend on the operating system and available features.
Developer collection and sharing
These on-device apps do not send this app data to AURA servers. AURA does not collect, sell, or disclose it to third parties. These releases have no account registration, sign-in, advertising, behavioral analytics, tracking, billing, subscriptions, Family Cloud, or cross-device synchronization. They do not provide secret monitoring of other people.
Apple devices
The iOS/iPadOS app uses Apple Screen Time features with the user's permission. Opaque tokens representing selected apps, categories and websites, selection counts, limits and enforcement status are handled on the device. The app does not obtain message contents, photos, contacts, location, passwords or browser history. Apple's policies may apply to processing performed by its operating system. Permission can be revoked in OS settings.
Android devices
An additional feature of Android Play Safe stores daily usage goals on the device. It saves social-media and game goals and a planning preference to avoid websites. It does not read actual usage, block apps through the OS, filter websites or monitor others. Android backup is disabled. This Android release is intended for users aged 18 or older.
Web pages and support
The privacy policy can be viewed in the app or on the website. Terms and other web links may open in an external browser. The app does not add local references or settings to URLs or receive browser input, cookies or browsing content. The website processes access logs needed to deliver and secure its pages. If you contact us by email, we process your email address, message and optional attachments to respond, maintain security and meet legal duties, and retain them only as long as needed.
Retention, deletion and security
On-device information is retained while needed to provide the features. You can delete it by uninstalling the app or using the OS's app-data deletion options. Apple device restrictions can be stopped using the app's removal function or by revoking authorization in OS settings. Storage and deletion in protected OS storage follow OS behavior. Contact us below to request access to or deletion of support information. Information no longer needed is deleted, except where retention is legally required. Device security also depends on screen locks and OS updates; absolute security is not guaranteed.
Policy changes
Before enabling features that expand data collection, transmission, sharing or purposes, we will update this policy, the relevant store privacy disclosures, and any required in-app information and consent.
AURA policy on avoiding customer-data accumulation and temporary correspondence
AURA does not base its business on collecting and accumulating information about individual or corporate customers. Our policy is not to create customer-identifying lists, company-specific customer profiles or sales ledgers. When proposal-related contact details and messages are processed temporarily, their use is limited to consideration and necessary replies; they are not repurposed into permanent customer profiles.
Once the purpose has ended, our policy is to delete the information appropriately, including storage locations and copies under our control. We will explain verified retention periods, deletion procedures and external-service retention or recovery periods for inboxes, sent mail, forwarding destinations, device copies and backups. This is not a claim that immediate, complete erasure across every location has been implemented and verified. We cannot guarantee deletion of copies held by correspondents.
Records subject to legal retention are distinguished from ordinary inquiry information and handled within the necessary scope and period. The product and contract-service descriptions below, including technical state, transaction references and operational logs, are distinguished from creating customer lists or sales profiles. This policy does not relabel all such information as anonymous; the existing explanations about information that can be linked or recombined continue to apply.
Information processed for website delivery and security, payments, external video services or advertising is explained separately from AURA's policy of not building customer databases. The policy does not mean that third parties never process cookies, IP addresses or other information.
Existing policy for enterprise and contract services
The following information concerns services with contract, issuance and management features. It does not mean that the on-device apps above collect these contract details or administrative logs.
1. Basic Policy
Our basic policy is data minimisation and privacy by design / by default.
In the standard workflow, we do not collect unnecessary information that identifies a natural person.
2. Standard Product Dataset
The information we ordinarily retain mainly includes serial ID, serial hex, issued market code, issued country, billing market, tenant ID, contract term, device identifier, contract records, and administrator action logs.
As long as the information can be recombined behind the scenes, we treat it as pseudonymized information rather than anonymous information.
3. Information Not Collected on Standard Pages
- Name on the standard purchase page
- Date of birth on the standard purchase page
- Address on the standard purchase page
- Telephone number on the standard purchase page
- Personal email address on the standard purchase page
4. Separation of Payments, Billing, and Legal Compliance
- Information required for payment may generally be collected and processed by a collection agency or payment service provider through a separate workflow.
- We receive only the minimum payment result, transaction reference information, and issuance information needed to perform the contract.
- If additional information is required for billing, taxation, or legal obligations, it is managed separately from the standard product dataset.
5. Special Provisions for B2B
- Corporate data itself is generally not data about a natural person.
- However, data concerning a one-person company or a company email address containing an individual's name may constitute personal data.
- We therefore recommend using a role-based address as the standard contract address.
6. Logs and Regional Information
- Observed country or region codes are retained, but raw IP addresses are kept only in short-term logs and precise latitude and longitude are not retained long term.
- Logs are used only to the extent necessary for contract performance, security measures, fraud prevention, audits, and administrator privilege management.
Customer-Managed Operations
Kyndrava is based on a Customer-Managed model in which the customer administrator manages users, devices, invitations, QR codes, and backups. As a rule, we do not obtain the customer organization's end-user roster, device list, individual usage logs, personal data, or backup data.
Customer-Managed Policy Operations Checklist Invitation Template
Operator and contact
AURA Intellectual Property Management LLCAURA知的財産管理合同会社
30-6-403 Kamiyamatecho, Suita, Osaka 565-0841, Japan
representative@aura-ip-jp.com