Privacy Policy
Application name: 0aueshka. Last updated: October 23, 2026.
This Privacy Policy is public. Reading it does not require an account or a login. It explains how the desktop application 0aueshka accesses, uses, stores, shares, retains, and deletes Google user data.
0aueshka is operated by the developer reachable at dekabrik0@gmail.com.
1. What 0aueshka does
0aueshka is a desktop application. Its purpose is to send an email message that the user writes, from a Gmail account that the user chooses to connect, using the Gmail API. The user provides the recipient addresses and the message. Sending happens only when the user starts it in the application.
0aueshka does not read the inbox, does not create images, and does not provide a website login.
2. Google user data 0aueshka accesses
0aueshka requests only these Google permissions:
openidandhttps://www.googleapis.com/auth/userinfo.email— the email address of the Google account the user selects.https://www.googleapis.com/auth/gmail.send— permission to send email from that account.
0aueshka does not request and does not read Gmail inbox contents, sent mail stored in Gmail, drafts stored in Gmail, contacts, Google Drive files, photos, calendar data, or any other Google account data.
3. How each type of data is used, stored, and shared
| Data | Why it is used | Where it is stored | Who it is shared with | How long it is kept |
|---|---|---|---|---|
| Gmail address of the connected account | To identify and display the account that will send mail. | A local file on the user’s computer, in the user’s home directory under .gmail-confirm. It is not uploaded to a server operated by the developer. |
Not sold. Not shared with the developer. Not shared with advertisers or other third parties. | Until the user removes that account in 0aueshka or deletes the local application files. |
| OAuth access token and refresh token | To call the Gmail API when the user starts sending a message, and to refresh that authorization. | The same local file on the user’s computer. Not uploaded to a developer server. | Not sold. Not shared with the developer or other third parties. The token is sent only to Google to authorize the API call the user started. | Until the user removes the account in 0aueshka, deletes the local files, or revokes access in their Google Account. |
| Recipient addresses, subject, and message text that the user enters | To send the email the user requested. This text is typed or loaded by the user. It is not read from the user’s Gmail mailbox. | Optional local files on the user’s computer if the user saved a draft or a recipient list in the application. | Transmitted to Google through the Gmail API so Google can deliver the message. Not transmitted to a server operated by the developer. Not sold. | Until the user deletes those local files. Google’s retention of delivered mail is governed by Google’s own policies. |
4. What 0aueshka does not do with Google user data
- It does not sell Google user data.
- It does not use Google user data for advertising, retargeting, or creditworthiness.
- It does not use Google user data to train machine-learning or artificial-intelligence models.
- It does not allow the developer to read the user’s mailbox or OAuth tokens. Those credentials stay on the user’s computer.
- It does not transfer Google user data to third parties except for the transfer to Google that is required to send the email the user started.
5. Limited Use
0aueshka’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Google user data is used only to provide the email-sending feature the user requested. It is not used for any unrelated purpose. Humans do not read this data, because the developer does not receive it. The only transfer is to Google, to deliver the message the user started.
6. Retention, revocation, and deletion
Local OAuth credentials and the connected Gmail address remain on the user’s computer until the user deletes them.
- In the application, the user can remove a connected account. That deletes the local credential file for that account.
- The user can also delete the
.gmail-confirmfolder in their home directory. - The user can revoke 0aueshka at any time at https://myaccount.google.com/permissions. After revocation, the saved token can no longer be used to send mail.
To ask a question about data stored by the application, email dekabrik0@gmail.com.
7. Security
OAuth credentials are stored locally so they are not collected on a developer-operated server. The user should protect the computer and the operating-system account, because the local files are on that computer. Transmission to Google uses HTTPS.
8. The public website
The website at https://0aueshka.my/ only publishes information about 0aueshka. It does not require an account or a login. It does not use cookies to identify visitors, and it does not contain a form that collects personal information.
9. AI-generated non-consensual intimate imagery
0aueshka does not use Google APIs, or any other service, to create, request, store, distribute, or facilitate intimate imagery, including AI-generated non-consensual intimate imagery. The application has no image-generation feature.
10. Children
0aueshka is not directed at children. It does not knowingly collect personal information from children.
11. Changes
If the application’s data practices change, this Privacy Policy will be updated, and the date at the top of this page will change.
12. Contact
Privacy questions about 0aueshka: dekabrik0@gmail.com