aiwaCore Mobile Privacy Policy
Effective 16 November 2026 · Android package and Apple bundle com.aiwa.coreaiwaCore is an aiwa product for authorized staff to coordinate business support. People without a staff account can also voluntarily register interest in future founder access. This policy covers the aiwaCore Android, iPhone and iPad applications and their connected control-tower services. The app is operated by the aiwa team; product and privacy inquiries can be sent to cc@aiwacore.com.
Founder interest
If you choose Register your interest, we collect the name, email, mobile number, venture or company name, city and country you enter, your optional description of an idea or need, and your consent record and submission timestamps. We use these details to assess interest, review needs and contact you about aiwaCore founder access. The details are linked to the contact information you provide and can be reviewed by authorized aiwaCore staff. Submitting does not create an account, grant access or guarantee availability. Do not include passwords, customer records or sensitive personal information in the optional note.
The embedded interest form uses Cloudflare Turnstile to prevent automated abuse. Cloudflare processes network and browser/device signals for verification; our server checks the result and uses a keyed network-address value for short-term rate limits, without storing the raw address in the interest record. Google Firebase/Google Cloud hosts the form and stores accepted submissions. A submission reference supports duplicate protection and follow-up. Interest records are kept while needed to assess and respond to your request, unless you withdraw or request deletion, subject to applicable legal requirements. To withdraw consent, correct your details or request deletion, contact cc@aiwacore.com and include your submission reference or the email you used. See the account and data request page.
Staff accounts and access
Accounts are issued and managed by an aiwaCore administrator. We process staff names, work email addresses, account identifiers, roles and permissions to authenticate staff, manage sessions and control access. Passwords are handled by Firebase Authentication. The app stores session information securely on the device. Access to a channel or module depends on current server authorization.
Business conversations and files
Authorized staff can view assigned business WhatsApp channels and customer conversations. We process conversation identifiers, customer names and phone numbers when available, messages, quoted replies, reactions, delivery information and files or voice notes that staff choose to send. These records support customer service and synchronize with the aiwaCore web console. Where permitted, administrators can also manage staff or view business inquiries and workspace records.
Device permissions
Microphone access is used when you choose to record a voice reply. Camera access is used when you choose to take a photo. System pickers let you choose an attachment. The app does not require access to your address book, precise location or broad device storage. You may decline camera, microphone or notification permissions; the related optional feature will then be unavailable.
Notifications and technical records
If you enable WhatsApp alerts, we associate a device notification token and an installation identifier with your staff account. Android notifications can include a channel label, customer number and short message preview. iPhone and iPad notifications use generic text without customer numbers or message previews; conversation content is retrieved after authenticated access in aiwaCore. Google Firebase Cloud Messaging and Apple Push Notification service process the device identifiers and delivery metadata needed to route enabled alerts. Device notification settings govern visibility and sound. The Firebase messaging and installation SDKs also process installation and technical diagnostics, such as app/device configuration and messaging delivery information, to operate and assess service reliability. We also keep operational and security records, such as action timestamps, staff identifiers, request identifiers, read/delivery state and changes to conversations, to support authorization, troubleshooting, duplicate-send protection and auditing.
Service providers and sharing
We use Cloudflare Turnstile for bot verification on the founder-interest form, Google Firebase/Google Cloud for authentication, protected data storage, application services and push delivery, and Apple Push Notification service for enabled iPhone/iPad alerts. WhatsApp business messages and selected attachments are transmitted through Meta's WhatsApp services to the intended recipients. These providers process information needed to deliver those services. We do not sell app data or use it for advertising. The app contains no advertising SDK. If you explicitly export a document or copy text into another app, that destination receives the information you selected.
Protection and retention
Connections between the app and our services use encryption in transit. Server permissions restrict data by account, role and channel. Meta tokens and server credentials are not placed in the app. This is not a claim that business records are end-to-end encrypted against aiwaCore: authorized staff and server processes handle the content to provide support.
Business records are retained while needed for support, operational history, security and applicable legal obligations. Staff access can be suspended or removed. App-owned media and recording caches are cleared on sign-out, account changes and startup; a copy you deliberately exported to another application is outside that cleanup. Hiding a message for yourself does not delete the customer's or another authorized staff member's copy.
Your requests
To request correction, account closure or deletion of associated information, contact your aiwaCore administrator or cc@aiwacore.com. Include your work email address and the request, but never send your password or customer attachments. We verify identity and distinguish staff account information from business conversation records that may need to be retained. See account and data request instructions.
Review and demonstration accounts
Store review can use a separately provisioned account containing synthetic test information. That demo does not give access to real customer channels or transmit its demonstration messages through Meta. Files you choose to upload while testing are stored in the isolated reviewer workspace; use test files only. Review access and its synthetic records can be retired independently of staff/customer records. Reviewer credentials are supplied privately through the relevant store review system when provisioned.
Audience and changes
This is a workplace application intended for adults, not children. Changes to this policy will be published here with an updated effective date.
aiwaCore · aiwa
In-app account deletion
Updated mobile builds let you initiate permanent account and associated personal-data deletion from Settings → Delete account, with explicit consent and password confirmation. The aiwaCore owner processes requests manually within one calendar month and sends completion confirmation to your registered email. We store the request identifier, staff/account identifiers, registered email, consent version, timestamps and processing status to handle the request. Direct staff identifiers and email are removed from the request record on completion; a minimal consent/fulfillment receipt is retained only as needed for applicable compliance obligations. See account and data requests for scope and retention details.