Last updated: May 20, 2026

Privacy Policy

This Privacy Policy explains how Ark.in handles information for Krisply, an Android writing assistant. Krisply is built with a privacy-first posture: collect only what is needed, avoid storing voice content from normal processing, keep diagnostics content-free by default, and give users a way to delete account data.

Our privacy principles

We do not sell personal data.
Voice input is used to generate your requested output, not to build an advertising profile.
Krisply's backend does not intentionally store audio or transcripts from normal speech processing.
Public diagnostics are intended to measure reliability, latency, routing, failures, and app/build health without sending your spoken content.
Feedback logs that may include transcripts or generated output are sent only when you choose to send them from the app. Audio is not included automatically. The backend stores selected structured report files and upload metadata for support, rather than keeping the raw zip by default.

Data we handle

The table below describes the main categories of data Krisply may access, collect, use, or transmit.

Account data: Google Sign-In data such as email address, email verification status, Google account identifier, and authentication token information. We use this to create or verify your Krisply account, protect trial eligibility, and connect subscription status to your account.
Installation identifiers: Krisply-generated installation IDs and access/refresh tokens. We use these for service access, rate limiting, abuse prevention, entitlement checks, and basic account continuity.
Voice/audio input: Audio you choose to record is sent for speech-to-text and writing output generation. In normal processing, Krisply handles the audio in memory or temporary app cache and clears/deletes it after processing. Krisply does not intentionally keep a backend copy of your audio.
Transcript and generated output: Transcripts and generated output are used to create the response you asked for. Krisply's backend does not intentionally store transcripts or generated output from normal processing. The app may keep local run logs on your device for troubleshooting, and those logs may include transcript/output text.
Writing settings: Mode, output language/script, requested polish level, and related context needed to produce the requested writing result.
Subscription data: Google Play product ID, base plan ID, purchase token, order/subscription state, expiry time, and entitlement status. We use this to verify Krisply Pro access. We do not receive your full card number or full payment credentials.
Diagnostics metadata: App version, build number, Android version, device model, locale, entitlement tier, delivery outcome, failure stage, error code, recording duration, audio size, latency, and timestamps. This helps us find crashes, slow processing, failed insertion paths, and reliability issues.
Feedback logs: If you manually choose to send feedback logs, the zip may include transcript text, generated output, diagnostics, usage snapshots, and issue tags. The app warns you before upload. Audio is not included automatically. The backend stores selected structured report files extracted from the bundle, such as export manifest, diagnostics, usage snapshot, forensic events, and eval-log records, along with upload metadata such as filename, size, consent note, issue tag, installation/account context, and timestamps.

Diagnostics and product improvement

Krisply may send public diagnostics by default in backend builds so we can keep the service reliable. These diagnostics are designed to be content-free: they focus on operational signals such as model latency, speech-to-text latency, cleanup latency, total processing time, failure stage, delivery path, entitlement tier, app version, Android version, device model, locale, recording duration, and audio payload size.

Diagnostics are used for debugging, reliability monitoring, fair-use guardrails, performance tuning, and deciding where the product is failing users. They are not intended to include your audio, transcript, generated text, clipboard contents, or screen contents. You can turn public diagnostics off from inside the app where the diagnostics control is available.

Krisply may transmit data to service providers only as needed to provide app functionality, secure the service, process subscriptions, and diagnose reliability issues. This may include cloud hosting, database/infrastructure providers, Google Sign-In, Google Play Billing, speech-to-text providers, and language-processing providers.

Voice input, transcripts, and generated text may be processed by speech-to-text or language-processing providers to deliver the requested output. We do not sell this data, and we do not share it for advertising purposes.

Security

Krisply uses HTTPS and authenticated backend requests for network communication. Account and installation tokens are used to protect backend access. Production account, installation, and subscription records are stored in durable backend storage. Access to production systems is intended to be limited to operational needs.

Retention

Audio: Krisply does not intentionally retain audio from normal processing. Temporary local audio files and backend audio buffers are cleared/deleted after processing.
Transcripts and generated output: Krisply's backend does not intentionally store these from normal processing. Local troubleshooting logs on your device may include them. If you choose to send feedback logs, transcript/output text may be present inside the bundle you send and inside selected extracted support records stored by the backend.
Diagnostics: Content-free diagnostics may be retained for reliability analysis, abuse prevention, and service improvement.
Account and subscription records: These are retained while your account or subscription relationship exists and as needed for billing, fraud prevention, legal compliance, security, and dispute resolution.
Feedback logs: Selected extracted support records and feedback upload metadata may be retained as long as needed to investigate issues and improve reliability, unless legal, security, or abuse-prevention needs require longer retention. Krisply does not need to keep the raw uploaded zip by default to support this workflow.

Your choices and controls

You can stop or cancel a recording from the Krisply overlay.
You can revoke microphone, overlay, notification, or accessibility permissions from Android settings.
You can turn public diagnostics off from inside the app where that control is available.
You can choose not to send feedback logs.
You can manage or cancel Krisply Pro through Google Play subscriptions.
You can request account and data deletion from the data deletion page.

Children

Krisply is not directed to children. If you believe a child has provided personal information, contact us and we will take appropriate action.

Changes to this policy

We may update this Privacy Policy as Krisply changes. If we make material changes, we will update this page and the date above. The privacy policy URL should remain stable even if the website design changes.

Contact

For privacy questions, support, or deletion requests, contact us at [email protected].