Information Yara receives
- Google sign-in: your Google account identifier, email address, and display name, used to create and secure your Yara account. Yara does not request access to Gmail, Google Drive, or Google Contacts.
- Calendar, if connected: Yara checks availability and reads upcoming event titles and times to detect conflicts and prepare an optional daily summary. After you approve a meeting, it creates the calendar event and invitation; when you request cancellation, it removes that event. Yara stores the calendar connection credential in encrypted form.
- Meeting requests: the name, email address, meeting topic, requested time, duration, and time zone submitted through your personal request page. Yara stores these for your review and may send the approved details to Google Calendar and the requester as part of an invitation.
- Seedhape, if connected: the Yara-only access tokens you provide, delegated spending information, and any quote and purchase details you ask Yara to prepare. Yara encrypts stored Seedhape credentials and POST request bodies. Seedhape authorizes and executes payments under your existing mandate.
- Notifications: your email address for alerts and optional daily summaries. If you enable web push, Yara stores an encrypted push endpoint and subscription keys so it can send generic notifications to that device.
- Technical and preference data: your time zone, scheduling rules, notification settings, request history, and operational records needed to keep the service reliable. The public meeting form uses the visitor IP address to enforce a request limit; Yara stores a keyed hash rather than the raw address for that limit.
How Yara uses Google user data
Yara uses Google account data only to sign you in and to provide the calendar features you choose. Calendar information is used to check availability, find upcoming events for your optional daily summary, and carry out a calendar action only after your approval. If you enable a daily email summary, the summary may include upcoming event titles and times and is sent through Yara’s configured email provider.
Yara does not sell Google user data, use it for advertising, or use it to train generalized AI models. Yara’s use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements.
When information is shared
Yara shares information with the service needed to perform the feature you request: Google for sign-in and calendar operations; the email and web-push delivery providers configured for Yara; Seedhape when you connect it to retrieve spending information or approve a purchase; and the seller whose service you ask Yara to purchase. A meeting requester receives an invitation only after you approve the booking. Yara does not sell personal information or share Google data for advertising.
Storage, security, and retention
Yara stores account and activity data in its application database. Provider credentials, Seedhape tokens, and push subscription details are encrypted by Yara before storage. Yara uses a secure, HTTP-only session cookie in production. No online service can promise absolute security, so keep your account credentials private and disconnect integrations you no longer use.
Yara retains your account information and history while your account is active. You can disconnect Google Calendar or Seedhape from the dashboard. You can delete your Yara account from the dashboard; this removes Yara’s account data and attempts to revoke Google access. Calendar events already created in Google Calendar, messages already delivered, and Seedhape payment records remain with those providers and must be managed there.
Your choices and contact
You can choose whether to connect Calendar, Seedhape, email summaries, or push notifications. You can pause Yara, disconnect integrations, revoke individual push devices, or delete your account from the dashboard. For a privacy question or request, email jathinjagannath@gmail.com.
This policy describes the current Yara application. It must be updated if Yara’s data practices or service providers change.