Privacy Policy

Permissions

New Gmail connections request one gmail.modify scope covering reading, sending and organizing. New consent no longer requests gmail.send or gmail.readonly. Access to the mailbox through Aviloza remains limited until applicable Google verification and security assessment are complete; consequential actions always require explicit user approval. Calendar is connected separately:

• Sign-in: openid, email, and profile (https://www.googleapis.com/auth/userinfo.email and https://www.googleapis.com/auth/userinfo.profile, together with openid).
• https://www.googleapis.com/auth/gmail.modify — read, compose, send and organize Gmail (labels, read status, archive and Trash, but no permanent deletion). Inbox modifications currently require a separately approved action and an authorized test account.
• https://www.googleapis.com/auth/calendar.events — to create, edit or cancel events the user explicitly approved.
• https://www.googleapis.com/auth/calendar.readonly — user-requested calendar list and time zones.
• https://www.googleapis.com/auth/contacts.readonly — find the user's contacts and email addresses on request.
• https://www.googleapis.com/auth/drive.readonly — find user-requested Drive files and read selected text files.
• https://www.googleapis.com/auth/drive.file — read only the files the user picks in Google's file picker. Aviloza does not see the rest of the user's Drive and never changes or deletes files.

New Gmail consent requests gmail.modify only, which technically grants read, send and modify capabilities. Granting consent does not automatically trigger mailbox reads or changes. Public inbox operations remain subject to Google OAuth verification and applicable security assessment; Google may block new authorization before approval. Existing gmail.send and gmail.readonly grants remain recognized for legacy connections but are not newly requested. Data is not sold for advertising or used to train general-purpose AI models.

Google API Services User Data Policy and Limited Use

Aviloza's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Aviloza requests only the scopes needed for features the user turns on. A write scope is not requested merely because a read scope was connected. Where the product supports it, a later action that needs more access uses a separate incremental consent.

Aviloza uses Google user data only to provide or improve user-facing features that are visible in Aviloza and that the user asked for. Aviloza does not sell Google user data and does not use it for advertising, including retargeting, personalized advertising, or interest-based advertising.

Aviloza does not allow humans to read Google user data except when the user has given explicit consent for that case, when it is necessary for security (including investigating abuse), when it is necessary to comply with applicable law, or when it is necessary to fix a problem the user asked Aviloza to fix.

Aviloza does not transfer Google user data to others except as Limited Use allows: to operate the user-facing feature the user requested (including a minimum transfer to an infrastructure or AI provider for that feature), to comply with applicable law, or with the user's explicit consent for that transfer. Google user data is not transferred for advertising.

Aviloza does not use Google user data to develop, improve, or train generalized AI or machine-learning models that are not required for the user-facing feature the user requested.

Disconnect and deletion

When you disconnect a Google connection inside Aviloza, Aviloza tries to revoke that access at Google when it is your last live Google connection, deletes the encrypted credentials stored for the connection, and by default deletes the information imported through that connection and the derived information attributed to it. Disconnect stops future sync of that connection.

The disconnect button does not ask you to keep a synced copy, and it does not send a request to retain that copy. If deletion fails, the connection is still disconnected and Aviloza says that deletion did not finish. You can ask for help from the support page.

An older internal description said synced information was kept after disconnect. That description is out of date. Current product behavior is to delete that Google connection's imported and derived information by default.

Other information is kept while it is needed to provide the service, for security, for a record the product keeps, to comply with law, or until it is deleted through the product or as required by law. Deleting the account is a separate signed-in action. It starts by stopping actions and connections. Aviloza marks the account deleted only after the later deletion steps succeed. Security audit entries stay, with the account link removed, rather than being described here as fully erased. This policy does not set a retention period for operator backups.

To disconnect Google inside Aviloza, sign in and choose Disconnect next to the connection. Disconnect tries to revoke that access at Google, deletes the encrypted credentials stored for the connection, and by default deletes the information imported through that connection. You can also remove Aviloza's access from your Google Account at https://myaccount.google.com/permissions. Removing it there stops the grant at Google. To have Aviloza delete information it already stored, use Disconnect inside Aviloza or write to support.

Deleting the account is a separate signed-in action. A request to access, correct, or delete personal information goes to aviloza44@gmail.com from the account address. Do not send passwords or tokens.

Who is responsible for the information

The Aviloza operator is the controller of the service database and is responsible for processing information under this policy and under Israel's Protection of Privacy Law, 5741-1981.

1. What Aviloza processes

Aviloza may process account and sign-in details, content the user enters, outcomes and live cases, tasks, preferences, memories and context created to provide the service, usage and security data, and information from external services the user chooses to connect.

Aviloza requests identity scopes, gmail.modify for new Gmail connections and calendar.events for calendar actions. Although gmail.modify grants broad technical capability, public Gmail inbox reads and organization remain subject to verification, security assessment and explicit feature consent. A designated reviewer may use synthetic data to test the restricted workflows ahead of public approval.

Account details include email address, display name, preferred language, and a record of when these terms and this policy were accepted. A paid plan stores subscription and billing details (plan, amount, status and transaction identifiers), not the full card number (see section 14). For security and operations Aviloza also records technical data such as sign-in times, browser type and product-usage events.

There is no legal duty to give Aviloza information. Providing it and connecting services is voluntary. Without some information (for example an email address, or a connected source), the service or a particular feature cannot be provided.

3. Why the information is used

The information is used to provide the features the user asks for: building personal context, noticing items that need attention, managing open loops and live cases, preparing recommendations, carrying out authorized actions, verifying results, securing the service, preventing abuse and fixing problems.

4. Google API Services User Data Policy and Limited Use

The full Limited Use text is in the Permissions section and applies to every use of Google user data.

5. Connections, permissions and actions

A connection to an external service is not treated as active before the provider confirms it. Aviloza shows the permission to send email and the permission to create or edit an event, one at a time.

External actions that change or send information may require a preview and an explicit approval. Approval of one action does not automatically become a standing permission. Emergency Stop is there to block new actions that the product supports.

6. Storage and security

Sensitive OAuth credentials are stored encrypted and are limited to server-side access. Connected data is stored under the user's account, with access isolation, so the product can provide the features the user asked for, follow up, and verify.

Aviloza uses reasonable technical and organizational safeguards, including user separation, permissions, action logs and approval checks. No online system can promise absolute security. More detail is on the security page.

7. Disconnect and deletion of connection data

Disconnect and deletion instructions are in the Permissions section.

8. Rights and control

A user can disconnect sources inside Aviloza, delete the account when that control is available, and ask to access, correct or delete personal information, subject to applicable law and to security or records the product must keep.

Under the Protection of Privacy Law, a person may review information about them held in the database and, if it is not correct, complete, clear or up to date, ask for it to be corrected or deleted. A person may also ask to be removed from a marketing list. Such a request is handled within the time the law sets. A person who believes their rights were not respected may also contact the Privacy Protection Authority.

Privacy and Google-connection requests go to aviloza44@gmail.com.

9. Children, sensitive information and special uses

Aviloza is not currently intended for independent use by children, and it does not ask the user to enter sensitive information that a requested feature does not need. Users should not pass on sensitive information about other people without proper permission.

10. Changes to this policy

If the way information is used changes in a material way, Aviloza will update this policy and will show an appropriate notice before using information for a new purpose when the law or a provider's policy requires it.

11. Transfers outside Israel

To provide some features, Aviloza may use infrastructure and AI providers that operate outside Israel (for example in the United States). That transfer is limited to the information needed to run the feature the user asked for. Aviloza takes reasonable steps intended to meet the Protection of Privacy Law, 5741-1981, including Amendment 13 (in force from 14 August 2025), such as limiting what is transferred, encryption, and restricting server-side access.

12. Database registration, a privacy officer, and security incidents

Aviloza tracks the scale of its activity and the sensitivity of the information it processes against the duties in Amendment 13 of the Protection of Privacy Law (for example appointing a privacy protection officer or registering a database), and will follow any such duty if and when the conditions apply.

Aviloza aims to detect and handle security incidents that involve personal information without unreasonable delay, and to report a breach to the competent authority and to affected users when the law requires it, including within the times the law sets.

13. Cookies and analytics

Aviloza does not use third-party advertising, tracking or analytics cookies. The service uses only the cookies and local storage it needs to run:

• Sign-in cookies (Supabase Auth): keep the secure session. The product cannot sign you in without them.
• Language cookie (personal-ai-locale): remembers the interface language you chose.
• Browser local storage: accessibility preferences, navigation-menu state, and acknowledgement of the cookie notice. This stays on the device and is not sent to us.

Product-usage data (for example which screens and actions were used) is recorded on Aviloza's own servers to improve the service, without private content and without an external tracker. If non-essential cookies are added later, they will be used only after explicit consent.

14. Processors and payments

Aviloza does not sell personal information. Information is shared only with providers needed to run the service, and only to the extent a requested feature needs:

• Storage and infrastructure: Supabase (database and sign-in) and Vercel (hosting the site and servers).
• AI providers: OpenAI and Google (Gemini), to process requests, draft text and understand context.
• Payments: Tranzila. Card details are entered on the payment provider's page and are not stored on Aviloza's servers.
• Services the user connects: Google identity, Gmail via gmail.modify, and Calendar via calendar.events. Sending and changing messages requires approval. Public inbox reading and organization are held behind Google verification and security release checks; invited reviewers can test with synthetic data. Historic Gmail grants are recognized for compatibility only.

Information may also be disclosed when required by law or a court order, or to protect rights, security and to prevent fraud.