Scope
This Data & Retention page describes API-originated data handling for Reply In My Voice, operated by TimeAwake Ltd at replyinmyvoice.com.
Effective 6 June 2026
Data & Retention
API data handling notes for Reply In My Voice request and result content on replyinmyvoice.com.
What is stored
For API rewrite jobs, Reply In My Voice stores request metadata plus the input and output on RewriteAttempt so async polling, idempotency, account history, support, and quota reconciliation can work.
Retention window
API-originated request and result content has a bounded 30-day retention window. After that window, stored input and output content is purged while operational records needed for account, billing, security, and abuse review may be retained.
Deletion
You can request deletion of API-originated content by contacting TimeAwake Ltd at info@timeawake.co.nz. Deletion is available for retained request and result content, subject to account, security, billing, and legal obligations.
Processors
API content is processed by the rewrite and naturalness providers needed to provide the service. Hosting, database, authentication, billing, and operational providers may also process the minimum data needed for their role.
API keys and account records
The service stores API key metadata, masked key previews, revocation status, usage counts, rate-limit data, and account identifiers needed to authenticate requests and operate paid quota.
Sensitive content
Do not submit passwords, payment card details, government identifiers, or highly sensitive personal information unless your own workflow has a clear need and permission to do so.
Contact
Questions about this data page can be sent to TimeAwake Ltd at info@timeawake.co.nz.