takebay privacy policy
Scope and provider
This policy applies to takebay, the Android recording and transcription app provided by fullrange. It also explains how fullrange handles website visits and support inquiries related to takebay.
Device storage and protection
The app uses the microphone to record audio and saves it on your device. Recording, importing or editing does not by itself send content to an AI provider.
- Audio, text and history
- The app stores recorded and imported audio, transcripts, AI summaries, titles, projects, dates, participants, tags, notes, previous content, processing settings and history for playback, viewing, editing and resuming tasks. Imported source files are not changed.
- API keys
- Registered API keys are encrypted on the device and used to authenticate with the corresponding external service.
- Google connection details
- The app keeps the selected Google account's email address and account type, the destination ID, name and displayed path, save history and information needed to resume saving. Account identifiers and resumable connection details are stored encrypted.
- Trial history
- The ID and trial start date of each recording first registered for AI processing are kept locally to count trial usage and allow retries and regeneration for that recording. Failure, cancellation or deletion of the recording does not remove that history or return the trial slot. It remains across app updates and device restarts.
- Purchase information
- Signed purchase information from Google Play and its verification status are stored to check and restore purchase entitlement. This includes the product, purchase status and purchase token. It is encrypted on the device using Android Keystore. The app does not directly collect card numbers or similar payment details.
Audio and text are kept in app-specific storage. The app does not provide its own encryption for audio files or the recording database. Protection provided by your device depends on Android and your device settings. API keys and the credentials described above use Android Keystore for encryption. External service connections use HTTPS. App data is excluded from Android's standard backup.
There is no separate fullrange account, advertising or analytics system in the app. The Google Play billing SDK may automatically send diagnostic information to Google. Google services, Android and AI providers handle information under their own policies.
Backup and restore
You can save a backup file to a location chosen in the system file picker and select that file to restore recordings on another device. Backups include saved recordings and original audio; titles, recording dates and other recording details; transcripts and AI summaries; notes, tags and projects; current and previous versions; and edit and processing history.
Backup files are not encrypted and may contain sensitive information. Keep them in a secure location and manage access to them yourself. If you select a cloud storage provider in the system file picker, the backup is transferred to that provider. This is separate from the built-in Google Drive integration, which saves Markdown only.
Backups exclude API keys, sign-in and OAuth credentials, purchase information, trial usage, app settings and saved-file status. Configure the destination device's accounts and save destinations separately. Restoration does not overwrite its purchase or trial state.
Restoring keeps past processing history but does not automatically restart transcription, summaries or uploads. It does not delete existing recordings. Deleting a recording, clearing app data or uninstalling takebay does not remove backup files or other exported copies; delete those separately where they are stored.
Data sent to other services
When you start AI processing or save to Google Drive, the app sends the relevant data directly from your device to the selected service. These transfers do not pass through a fullrange server.
- OpenAI transcription
- When you select OpenAI, the app sends the audio, processing settings such as the model and language, and an ID used to match the processing request.
- AssemblyAI transcription
- When you select AssemblyAI, the app uploads the audio and submits its URL, processing settings such as the model and language, and a request-matching ID to request transcription.
- OpenAI summaries
- The app sends the selected transcript, app-provided generation instructions, processing settings such as the model, and a request-matching ID. If you select edited text, that text is sent. This task does not include audio.
- Google Drive Markdown saving
- The app sends Markdown to the chosen folder in your selected Google account. It can include the transcript, AI summary, title, project, participants, tags, notes, recording and generation dates, duration, language, service and model. The filename and information needed to reconcile the save result are also sent. This integration does not send audio.
- Google Play purchase and restoration
- Google Play handles purchases and payment. The app exchanges product information and purchase tokens with Google Play to check and restore purchase status and acknowledge completed purchases. Purchase information is not sent to a fullrange server. Audio, transcripts, AI summaries and API keys are not sent for purchase verification.
- Google Play SDK diagnostics
Connecting to Google Play and checking purchase status may send processing results, errors, app and SDK versions, device, operating system and network information, and random session identifiers used to relate SDK activity to Google. Google uses these logs to improve billing SDK performance and investigate errors.
Purchase status is also checked when opening or returning to the app, so this can happen without making a purchase. The app has no setting to disable only this diagnostic transmission.
Transcription uses the service you select. The app does not automatically switch to another provider and send your content there. AI features use your own API keys, and provider charges are separate during the trial and after purchase.
Exporting to a chosen destination
You can export audio and Markdown to a destination selected through the system file picker. Selecting a cloud destination transfers that data to the provider. Exported files and their backups are managed under the destination's settings.
Sharing and copying
Sharing a transcript, AI summary or saved Markdown passes the content to the app you select. Copying text places it on the device clipboard. Handling by the receiving app or clipboard follows the relevant provider's policies and device settings.
Google Drive integration
The app uses Google's account and folder selection screens and requests the file-level drive.file permission. This covers files created by the app and files or folders you select and authorize. It does not grant access to your whole Drive or every existing file in the destination folder.
To confirm the account and destination, save Markdown, display save status and retry saves, the app obtains:
- Connected account
- Email address and account type.
- Files and destinations
- Names, IDs, types, sizes and viewing links of authorized files or folders, and their locations, including parent folders and shared drives.
- Save status
- Information needed to check whether saving is allowed, whether a file is in the trash, and whether file content and save results match.
The app does not obtain your Google profile name or photo, contacts or Gmail.
Information obtained through this Drive integration is not used for advertising, sale or AI training. Use and transfer to other apps of information received from Google APIs comply with the Google API Services User Data Policy, including the Limited Use requirements.
Provider retention and training
Retention periods, processing locations and use for model training at the receiving service depend on its terms and privacy policy and your contract and settings. Data may be processed or stored outside your country, including outside Japan.
- OpenAI
- Data sent to the API is not used for model training unless you explicitly opt into data sharing. The app generates summaries with API response storage disabled, but that setting does not disable every form of retention, including abuse monitoring. Retention depends on the API's terms and your account settings.
- AssemblyAI
- Submitted data may be used for model training depending on your agreement and settings. Check the provider's guidance for conditions to stop training use and the separate retention periods for audio and transcripts.
- Google Drive and other storage destinations
- Saved files are managed under your account and the destination's settings and terms.
- Google services and SDKs
- Use, retention and deletion of purchase, authentication and SDK diagnostic information follow the policies of the relevant Google service.
Deletion and cancellation
Saved recordings and text remain in the app until you remove them or the app's data is cleared. You can delete recordings and text in the app. Imported source files and exported files are managed separately at their respective locations.
- Delete audio only
- Deletes the selected audio. Transcripts and AI summaries remain.
- Delete a recording completely
- Deletes that recording and its related app data. Its trial-counting ID and trial start date, app-wide purchase information, API keys and settings remain. Imported source files, files exported to other folders and Markdown saved to Drive also remain.
- Delete an API key
- Removes its local registration. It does not revoke the key at the provider. Use the provider's controls to revoke it.
- Cancel an AI task
- Stops processing for that recording in the app, without automatic restart. Results already received may be saved. You review and start any resumption. Resending may incur additional charges.
Clearing app data or uninstalling the app removes local trial history and purchase information. It does not remove Google Play's purchase or payment records.
Deleting recordings or disconnecting Drive does not request deletion of SDK diagnostics already sent to Google. Text and Markdown shared to another app and clipboard copies are also outside recording deletion; manage them using the receiving app or device controls.
Deleting data or cancelling a task in the app does not delete data already sent to AI providers, cancel their processing or reverse charges. Data held by external services follows their deletion procedures and retention terms.
Disconnecting Drive
Disconnecting in the app stops Drive saving and revokes Google's access permission. If revocation does not complete, saving still stops and the app offers a retry. Recordings, transcripts, AI summaries and files already saved to Drive remain.
The option to delete connection information on the device, for example after a connection error, removes local account details and destination settings only. It does not revoke permission at Google. You can check that permission in your Google account connections.
Website and support information
When you visit this website, Cloudflare processes connection information such as your IP address to deliver the site and prevent unauthorized access.
If you contact fullrange, we use your name, affiliation, email address or other contact details, message and attachments to respond, clarify your request and communicate about estimates or agreements where relevant. For product support, we use contact details, your inquiry and the environment or fault information you provide to explain operations, investigate causes and fix issues.
We limit collection to what is needed for these purposes. Except where the law permits, we do not use information beyond those purposes without your consent.
Protection and retention
Access to personal information is limited to what is needed for the work. We take measures such as protecting devices and accounts to prevent loss or disclosure. If an incident occurs, we investigate and limit the harm, and report or notify as required by law.
We retain support and inquiry information for as long as needed to respond, perform agreements, meet legal retention duties or handle disputes. When it is no longer needed, we delete or dispose of it.
Service providers and transfers
We do not provide personal data to third parties without your consent, except where permitted by law. We may engage providers for email or data storage as needed for these purposes. We review their safeguards and contract terms and provide necessary oversight.
Where information is provided to an overseas provider or handled abroad, we review the relevant legal system and recipient safeguards and follow legally required disclosure, consent and other procedures.
Privacy requests and contact
For questions about app data or operations, contact support@fullrange.jp.
For privacy questions, complaints or requests concerning personal data held by fullrange, contact contact@fullrange.jp. We also answer inquiries about the proprietor's identity and management of personal information.
You can request information about purposes of use, access to your personal data or records of third-party disclosure, correction, deletion, restriction of use or cessation of third-party provision. We verify your identity or your representative's authority as necessary and respond under applicable law. If we cannot fulfill part of a request, we explain why.
If this policy changes, we will publish the changes and their effective date on this site. We provide notice or obtain consent where required by law.