here.
Privacy policy
here. is operated by Konpat for personal use and specifically authorized collaborators. This policy describes its Google connection and personal note data handling.
Data and permissions
The Google file connection requests OpenID identity, email and the drive.file permission. It verifies your email address and stores authorization credentials so the server can continue the operations you authorized.
Access is limited to files created by or explicitly authorized for here., including its household expense Sheet and any subsequently enabled archive files. It does not give here. general access to all existing Drive files or Gmail. Google Calendar is a separate, optional connection with separate consent.
The private application also handles the notes, original recordings, photos, attachments, transcripts, AI answers, edit history and metadata you provide. Information relevant to a household expense can include dates, merchants, amounts, allocation decisions and source links.
Use and storage
Data is used to capture, retrieve and organize your notes; provide requested transcription and assistance; maintain your expense Sheet; and provide explicitly enabled storage and backup functions. New or edited expense information can update the linked Sheet in the background.
The application stores working data on your device and the private server. Google files remain in the connected account under the permissions you authorize. Credentials are stored privately on the server, not in public pages or note exports. Ordinary readable Drive files are not end-to-end encrypted by here.
Sharing and service providers
The expense Sheet is shared only with the specifically authorized household collaborator. Other sharing requires your instruction. Private source links still require access to here.
Google handles files and authorization on its services. The hosting infrastructure and Cloudflare handle application traffic. Audio and relevant note or attachment content may be sent to your configured OpenAI or Anthropic services for transcription, organization or requested assistance, subject to the configured provider's terms and settings. Google API data is transferred only where necessary for a specific, authorized, user-facing feature—not for unrelated analysis or model training.
here. does not sell Google user data, use it for advertising, or use it to train generalized AI or machine-learning models. Its use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Human access to Google API data is limited to your affirmative permission for specific content, necessary security or abuse investigation, or a legal obligation. These information pages provide no access to personal notes, attachments or account credentials, and have no sign-in form.
Your controls and retention
You can reconnect services from here.'s Connections menu, revoke the Google connection through your Google Account permissions, and manage file sharing in Drive. Revoking access stops future authorized Google operations; it does not delete files already stored on Google or copies retained on your device or server.
here. preserves original media and edit history for recovery and traceability. Archiving a note hides it rather than permanently erasing its originals or history. Data is retained until deliberately removed through an authorized removal process; retained cloud copies and backups may require separate removal. Contact the operator to request review, export or deletion.
Contact and changes
Contact the.akita.ta@gmail.com for access or privacy questions. Material changes to data use will be reflected in this policy and require new authorization where applicable.