Introduction
Pyas is a calendar integrations API service that allows developers to read, create and manage events on Google Calendar and Microsoft Outlook (Microsoft 365 and Outlook.com) calendars, and on Pyas calendars, which are virtual calendars Pyas hosts itself. Pyas also allows developers to add Google Meet, Microsoft Teams and Zoom meetings to events. The www.pyas.io website (the "Site"), including all subdomains such as app.pyas.io, is comprised of various web pages owned and operated by BrutForce Technologies, LLC ("BrutForce"). Pyas and BrutForce Technologies, LLC may be collectively referred to as "the Company" in this document.
Protecting your private information is our priority. This Statement of Privacy applies to www.pyas.io, app.pyas.io, all other Pyas subdomains and governs data collection and usage. The Pyas website is a commercial site. By using the website, you consent to the data practices described in this statement.
End User Privacy Policy
This End User Privacy Policy is meant to help you (the "end user") understand how Pyas collects, uses, and/or shares your data when you use applications ("apps") that are powered by Pyas. You should read this Policy carefully, as it is important.
Data Collection
When you use Pyas, like when you connect your Google, Microsoft, or Zoom account(s) to a developer's app through Pyas, we may collect the following data from you:
- Name
- Email address
- Security Tokens
- The permissions (scopes) you granted
Google User Data
Pyas's use and transfer of information received from Google APIs to any other app will adhere to Google API Services User Data Policy, including the Limited Use requirements.
Pyas collects and stores the following Google user data:
- OAuth Tokens: We store encrypted oauth/security tokens in order to authenticate each API request to your (the "user's") Google Calendar.
- Email: We store your (the "user's") email in order to access your Google Calendar.
- Name: We store your (the "user's") name in order to properly associate your Google account with Pyas.
When you connect your Google account to Pyas, Pyas will have the ability to do the following:
- List calendars - We will be able to see a list of your calendars
- List calendar events - We will be able to see/access all of your calendar events
- Create calendar events - We will be able to create and add new events to your calendars
- Update/edit calendar events - We will be able to update/edit your calendar events
- Delete calendar events - We will be able to delete events from your calendars
- See your free/busy information - We will be able to see when you are busy, without seeing event details
- Read your calendar settings - We will be able to read settings such as your time zone
Pyas does not keep copies of your calendar events. To tell the developer's app when an event changes, Pyas stores each event's identifiers, its start time and a fingerprint (a one-way hash of the event), never its title, description, location or attendees. To answer repeated requests quickly, Pyas may hold an event's details in a temporary cache for no more than 20 minutes.
When you connect your Google account to a developer's app through Pyas, we may share your calendar events data with that developer. We are not responsible for the developer's privacy practices, but we have put forth some rules and guidelines in our Developer Policy below regarding how developers who use Pyas should protect any data shared with them. You should review the developer's privacy policy before connecting your Google account.
You (the "end user"), reserve the right to revoke access to your account. In the event that you revoke Pyas's access to your Google account, Pyas will no longer be able to access your Google Calendar.
Microsoft User Data
Pyas collects and stores the following Microsoft user data:
- OAuth Tokens: We store encrypted oauth/security tokens in order to authenticate each API request to your (the "user's") Microsoft Outlook account.
- Email: We store your (the "user's") email in order to access your Microsoft Outlook Calendar.
- Name: We store your (the "user's") name in order to properly associate your Microsoft account with Pyas.
When you connect your Microsoft account to Pyas, Pyas will have the ability to do the following:
- List calendars - We will be able to see a list of your calendars
- List calendar events - We will be able to see/access all of your calendar events
- Create calendar events - We will be able to create and add new events to your calendars
- Update/edit calendar events - We will be able to update/edit your calendar events
- Delete calendar events - We will be able to delete events from your calendars
- See your free/busy information - We will be able to see when you are busy, without seeing event details
- Read your mailbox settings - We will be able to read settings such as your time zone and working hours
- Create Microsoft Teams meetings - We will be able to create and update Teams meetings for your events
Pyas does not keep copies of your calendar events. To tell the developer's app when an event changes, Pyas stores each event's identifiers, its start time and a fingerprint (a one-way hash of the event), never its title, description, location or attendees. To answer repeated requests quickly, Pyas may hold an event's details in a temporary cache for no more than 20 minutes.
When you connect your Microsoft account to a developer's app through Pyas, we may share your calendar events data with that developer. We are not responsible for the developer's privacy practices, but we have put forth some rules and guidelines in our Developer Policy below regarding how developers who use Pyas should protect any data shared with them. You should review the developer's privacy policy before connecting your Microsoft account.
You (the "end user"), reserve the right to revoke access to your account. In the event that you revoke Pyas's access to your Microsoft account, Pyas will no longer be able to access your Outlook Calendar.
Zoom User Data
Pyas collects and stores the following Zoom user data:
- OAuth Tokens: We store encrypted oauth/security tokens in order to authenticate each API request to your (the "user's") Zoom account.
- Email: We store your (the "user's") email in order to access your Zoom account.
- Name: We store your (the "user's") name in order to properly associate your Zoom account with Pyas.
When you connect your Zoom account to Pyas, Pyas will have the ability to do the following:
- List meetings - We will be able to view/list meetings and meeting information
- Create meetings - We will be able to create new meetings on your behalf.
- Update/edit meetings - We will be able to update/edit Zoom meetings.
- Delete meetings - We will be able to delete meetings on your behalf.
Pyas does not keep copies of your Zoom meetings. Notifications that Pyas sends to the developer's app about your meetings are kept for 30 days so the developer can resend them.
When you connect your Zoom account to a developer's app through Pyas, we may share your meetings data with that developer. We are not responsible for the developer's privacy practices, but we have put forth some rules and guidelines in our Developer Policy below regarding how developers who use Pyas should protect any data shared with them. You should review the developer's privacy policy before connecting your Zoom account.
You (the "end user"), reserve the right to revoke access to your account. In the event that you revoke Pyas's access to your Zoom account, Pyas will no longer be able to access your Zoom meetings.
Pyas Calendars
Pyas calendars are virtual calendars that exist only in Pyas, not in Google Calendar or Outlook. When a developer's app keeps your calendar as a Pyas calendar, Pyas is your calendar provider and stores that calendar's events, including their titles, times and attendees, until the developer deletes them. Deleted events are kept for 30 days so connected apps can sync the deletion.
How Long Pyas Keeps Your Data
- Your connected account (name, email address, the permissions you granted and encrypted security tokens): until the developer's app deletes it. If you revoke Pyas's access, Pyas can no longer reach your account.
- Notifications sent to the developer's app about your account or calendars: 30 days.
- Records of requests made to Pyas, which hold identifiers but not the contents of your calendar: 7 to 30 days, depending on the developer's plan.
- Information the developer attaches to your events or calendars through Pyas: until the developer deletes it or your account, then removed within 30 days.
- Operational logs, which record which requests were made but not what they contained: 30 days.
- A change an AI tool asks to make on a real calendar, while it waits for someone to confirm it: up to 30 minutes.
Who Decides How Your Data Is Used
The developer whose app you connected decides why your calendar data is used and how. Pyas handles that data for the developer, following its instructions. In data protection terms, the developer is the controller and Pyas is its processor.
To use your rights over that data, such as seeing or deleting it, contact the developer first. If you contact Pyas instead, we will help you reach them. To stop Pyas reaching your account at any time, revoke its access in your Google, Microsoft or Zoom account settings.
For the details in a developer's own Pyas account, Pyas is the controller.
Developer Policy
This Developer Policy provides rules and guidelines that govern access to or use by developers ("you", "your") of the Pyas API, websites, dashboards, tools, and any other service(s) provided by Pyas.
By accessing and using our services, you agree to comply with all the terms of this Policy. This Policy will apply each time you access or use our services. If you are agreeing to the terms of this Policy on behalf of an organization or entity, you represent and warrant that you are so authorized to agree on behalf of that organization or entity. This Policy is important; please read it carefully.
Registration
To sign up for Pyas, you must create an account ("Account") by registering on our website (www.pyas.io) and providing true, accurate, and complete information about yourself and your use of our services. You agree not to misrepresent your identity or any information that you provide for your Account, and to keep your Account information up to date at all times. It is your responsibility to maintain access to your Account; you may never share your Account information, including your Pyas account password, as well as your API authentication credentials, including app Client ID and Secrets, with a third party or allow any other application or service to act as you.
Compliance with Applicable Law
When using Pyas, you agree to abide by all applicable local, state, national, and international laws. You also confirm that you, your business, your employees, your service providers, and any others acting on your behalf adhere to all applicable laws, especially those pertaining to user/consumer data, data protection, privacy and data security.
Security
You are responsible for securely maintaining your Pyas Account username and password, as well as your API authentication credentials, including all Client ID and secrets. You agree to notify us promptly at support@pyas.io in the event of any breach of security or unauthorized use of your Account or any End User Data. You must never publish, distribute, or share your API keys, Client ID or secret, and must encrypt this information in storage and during transit.
Your systems and application(s) must handle End User Data securely. With respect to End User Data, you should follow industry best practices but, at a minimum, must perform the following:
- Use modern and industry standard cryptography when storing or transmitting any sensitive End User Data.
- Maintain reasonable access controls to ensure that only authorized individuals that have a business need have access to any End User Data.
- Monitor your systems for any unauthorized access.
- Patch vulnerabilities in a timely fashion.
- Log and review any events suggesting unauthorized access.
- Plan for and respond to security incidents.
- Maintain administrative, technical, and physical safeguards that are designed to ensure the security, privacy, and confidentiality of End User Data.
Data Storage and Usage
Any End User Data in your possession must be stored securely and in accordance with applicable laws. To the extent applicable, if you use End User Data in an anonymized form then your use of such anonymized data must be clearly and conspicuously disclosed to the End User including a description of how you use such anonymized End User Data.
Prohibited Conduct
You agree not to, and agree not to assist or otherwise enable any third party to:
- sell or rent End User Data to marketers or any other third party;
- access or use Pyas or End User Data for any unlawful, infringing, threatening, abusive, obscene, harassing, defamatory, deceptive, or fraudulent purpose;
- access or use Pyas to access, transmit, process, or store End User Data in violation of any applicable privacy laws or in any manner that would be a breach of contract or agreement with the applicable end user;
- access or use Pyas to infringe any patent, trademark, trade secret, copyright, right of publicity, or other right of any person or entity;
- scan or test (manually or in an automated fashion) the vulnerability of any Pyas infrastructure without express prior written permission from Pyas.
- breach, disable, interfere with, or otherwise circumvent any security or authentication measures or any other aspect of Pyas.
- overload, flood, or spam any part of Pyas.
- create developer accounts for Pyas by any means other than our publicly-supported interfaces (e.g., creating developer accounts in an automated fashion or otherwise in bulk);
- transfer, syndicate, or otherwise distribute any Pyas or End User Data
- decipher, decompile, disassemble, copy, reverse engineer, or attempt to derive any source code or underlying ideas or algorithms of any part of Pyas, except as permitted by applicable law;
- access or use Pyas or End User Data in a manner that violates any agreement between you or the end user and Pyas
- access or use Pyas or End User Data in a manner that violates any applicable law, statute, ordinance, or regulation.
Termination
We reserve the right to withhold, refuse, or terminate access to Pyas and/or End User Data in whole or in part where we believe Pyas is being accessed or used in violation of this Policy or any other Pyas agreement.
Collection of your Personal Information
In order to better provide you with products and services offered, Pyas may collect personally identifiable information, such as your:
- Name
- Email address
- Contact information
- Company/Organization Name
- Payment information
- The name of each AI tool or CLI sign-in you connect to Pyas, and when it was last used
Note: Pyas does not store your credit card information. Pyas uses Stripe to securely handle all payment information.
Use of your Personal Information
Pyas collects and uses your personal information to operate and deliver the services you have requested.
Pyas may also use your personally identifiable information to inform you of other products or services available from Pyas and its affiliates or to:
- Comply with applicable laws and regulations
- Protect Pyas's rights and property
- Respond to user requests
Sharing Information with Third Parties
Pyas does not sell, rent or lease its customer lists to third parties.
Pyas may, from time to time, share data with trusted partners to help perform statistical analysis, send you email, or provide customer support. All such third parties are prohibited from using your personal information except to provide these services to Pyas, and they are required to maintain the confidentiality of your information.
Data Collection
Data collection is limited to the following:
- Visiting our website: We employ Google Analytics tools.
- Account creation: It is necessary to provide personal information in order to create an account. We do associate the email address with your account (for password recovery, or notifications).
- IP Logging: By default, we do not keep permanent IP logs in relation with your use of the Services. However, IP logs may be kept temporarily to combat abuse and fraud, and your IP address may be retained permanently if you are engaged in activities that breach our terms and conditions (spamming, DDoS attacks against our infrastructure, brute force attacks, etc). The legal basis of this processing is our legitimate interest to protect our Services against nefarious activities.
- Payment Information: We rely on Stripe to process payments. We redirect you to their platform, and you provide your payment information to them. Therefore, we do NOT store your payment information. However, we do store payment confirmations. The legal basis of this is the necessity to the execution of the contract between you and us.
- Communicating with Pyas: Your communications with us, such as support requests, bug reports, or feature requests may be saved by our staff. The legal basis for processing is our legitimate interest to troubleshoot more efficiently and improve the quality of the Pyas service.
- Account activity: We store records of requests from your website or app to Pyas: the endpoint, status, identifiers and any error, not the contents of the request. They are kept for 7 to 30 days depending on your plan.
Service Providers
We use service providers for hosting, database storage, caching, file storage, email, error monitoring, payments, bot protection and measuring website visits. Each may only use your data to provide its service to us. Our hosting, database, caching, file storage and error monitoring providers each hold a SOC 2 Type II report from an independent auditor.
Google, Microsoft and Zoom aren't service providers of ours: you connect those accounts yourself, and they act under their own terms.
Where Data Is Processed
Pyas stores and processes data in the United States. Data protection law in the United States can differ from the law where you live.
Cookies
Cookies are small files that a site or its service provider transfers to your computers hard drive through your Web browser (if you allow) that enables the sites or service providers systems to recognize your browser and capture and remember certain information.
We use cookies to compile aggregate data about site traffic and site interaction so that we can offer better site experiences and tools in the future. We may contract with third-party service providers to assist us in better understanding our site visitors. These service providers are not permitted to use the information collected on our behalf except to help us conduct and improve our business.
Cookies are used by us to authorize and authenticate Users. These cookies are necessary for the Pyas dashboard.
Data Security
Pyas takes steps to protect personal information from unauthorized access, use, disclosure, alteration, or destruction. These steps include:
- Using industry-standard security measures
- Requiring third-party service providers to comply with Pyas's security standards
- Monitoring Pyas's systems for security vulnerabilities
User Rights
Users have the right to access, correct, delete, or restrict the use of their personal information. Users may also have the right to object to the processing of their personal information. To exercise these rights, users may contact Pyas at: support@pyas.io
Links
This website contains links to other sites. Please be aware that we are not responsible for the content or privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of any other site that collects personally identifiable information.
Changes to This Privacy Policy
Pyas may change this privacy policy from time to time. When Pyas makes changes to this privacy policy, Pyas will post the changes on Pyas's website. Users are responsible for reviewing Pyas's website for updates to this privacy policy.
Contact Us
Pyas welcomes your questions or comments regarding this Privacy Policy:
Email Address:
support@pyas.io