Privacy

Privacy Policy

This Privacy Policy explains how Askly handles account, guest, and messaging identifiers, Balance and payment records, prompts, uploads, analytics, support, and mobile app data.

Last updated Jul 18, 2026

Responsible party, scope, and privacy contact

Tradegrow Pty Ltd, registration number 2024/207287/07, trading as AI Airtime, operates Askly and is the developer and responsible party for the Android app, iOS app, PWA, checkout pages, support pages, and related backend services. Our physical address is 44 Schumann street, SW5, Vanderbijlpark, 1911, South Africa. The designated Information Officer is Jarrod Dawson. POPIA, privacy, account deletion, and access-to-information requests can be sent to legal@ai-airtime.co.za. Support requests can be sent to support@ai-airtime.co.za.

Information we collect

For registered accounts we process identifiers and account details such as email address, phone number, display name, tenant, market, authentication session, language preference, legal-consent timestamps, Balance and immutable ledger records, top-ups, vouchers, payment references, and support activity. When you use an approved messaging channel, we may also process the channel and provider identifier, a provider-issued pseudonymous contact or conversation identifier, language and market routing, commands and responses, delivery and retry status, opt-in or opt-out state, account-link and consent timestamps, and short-lived handoff-session records. One-time handoff codes and checkout sessions are limited to the action and expiry shown. For guests we create pseudonymous local session and device identifiers and may process a limited device-environment fingerprint to enforce the two-free-question allowance and prevent abuse. This can include browser, operating system, language, screen, timezone, and device-capability signals. When you use AI, we process prompts, responses, selected answer mode and provider, conversation history, metering and monetary charge records, and any text, document, image, or other file you choose to upload.

How we use information

We use information to create and protect accounts, provide guest and approved messaging access, route commands to the correct tenant, market, and region, enforce abuse and rate limits, record consent and account-link choices, deliver and retry messages, process Balance top-ups and vouchers, maintain Balance and ledger integrity, provide AI services, show charges after completed requests, retain conversation history, support customers, investigate failures, and produce tenant-level operational and financial reporting. We also process diagnostics, IP address, browser or app version, crash and error logs, referral and campaign identifiers, ad click identifiers, checkout events, and resettable analytics identifiers where those tools are enabled.

Prompts, uploads, AI providers, and cross-border processing

Prompts, selected uploads, and AI interaction data may be routed to specialist AI and infrastructure providers in jurisdictions including the United States, the European Union, and other territories. We use contractual and technical safeguards appropriate to the service and applicable data-protection law, including POPIA Section 72 where relevant. Only attach content you are permitted to share. Askly does not require background location, precise location, contacts, SMS, call logs, health data, microphone recordings, or unrestricted access to your photo library for the core service.

Model training

Askly does not use customer prompts, uploaded documents, or private conversation histories to train foundational AI models. We configure and contract with service providers to restrict model-training use where their services support those controls.

Payments, Balance, vouchers, and service records

Configured payment providers handle card, wallet, QR, or hosted-checkout details. On iPhone and iPad, Apple processes in-app purchases and supplies a signed transaction record for server verification. Askly stores payment status, gross amount, wallet value, separately disclosed payment-fee or customer-price-adjustment records, transaction references, idempotency keys, provider names, top-up and voucher records, completed AI-service charges, reversals, refunds, and ledger balances. Askly does not receive or store the payment credentials used for an App Store purchase, and the PWA does not need to store full card numbers. Balance values are recorded in the configured local currency. New Balance funds and voucher values do not expire. Historical ledger entries may retain legacy descriptions where required for accounting and dispute records.

Analytics and advertising measurement

When enabled, analytics and advertising measurement tools may process app opens, sign-ups, top-up and voucher funnels, completed purchases, feature use, diagnostics, campaign identifiers, and aggregate product performance. We use this information to operate and improve the service and to understand which campaigns led to registrations or purchases. Google Play Data safety and Apple App Privacy disclosures must remain consistent with this policy and the app's actual handling of account identifiers, contact information, user content, purchases, product interaction, diagnostics, and analytics identifiers.

We share data only as needed with tenant administrators, approved business-messaging providers, payment providers, AI providers, infrastructure and analytics providers, fraud-prevention services, support operators, professional advisers, app-store reviewers where necessary, and public authorities where lawfully required. A messaging provider may receive the destination identifier, message content required for delivery, delivery status, and a secure PWA link; it does not receive your Askly password or full card details. Providers must process data for disclosed purposes and protect it appropriately. We do not sell prompts, uploaded content, Balance history, messaging contact identifiers, or account details.

Security

Askly uses encrypted transport, backend-controlled authentication, tenant-scoped authorization, restricted administrative access, server-side monetary and usage checks, immutable financial ledger records, idempotency controls, operational logs, and hosted checkout where configured. No system can be guaranteed perfectly secure, but public app screens do not expose passwords, full card numbers, raw access tokens, backend secrets, or internal provider credentials.

Retention, deletion, rights, and complaints

Request account deletion or exercise applicable access, correction, export, objection, consent-withdrawal, or deletion rights by contacting legal@ai-airtime.co.za or support@ai-airtime.co.za. Include the account identifier, market, and the nature of the request. You may also use the supported STOP or opt-out command to stop non-essential messaging where that channel offers it. We delete or de-identify account, guest, messaging-session, and delivery data where law and platform-integrity requirements allow. One-time handoff codes and sessions expire and are not retained as reusable credentials. Limited security, fraud, messaging-consent, delivery, tax, accounting, immutable ledger, dispute, legal-compliance, and proof-of-request records may be retained for the required period. Account closure does not remove statutory refund, reversal, complaint, or other remedies that apply to remaining Balance or disputed transactions. You may contact South Africa's Information Regulator at POPIAComplaints@inforegulator.org.za if you believe your POPIA rights have not been respected.

Questions? Contact support@airtime.local.