Privacy Policy

1. Who is responsible for Agiles

Agiles is technically operated by an individual self-employed professional. No company or Brazilian corporate registration number (CNPJ) is claimed in this policy. Where this individual determines the purposes and means of processing, they may act as a data controller under applicable law.

Organizations using Agiles may decide what information to add to projects and for which purposes. Legal responsibilities depend on what each participant actually does.

Agiles has four access roles: Collaborator, Analyst, Manager and Principal Manager. These roles determine permissions within the platform; they are not, by themselves, the legal categories of controller and processor under Brazil’s General Data Protection Law (LGPD).

2. What information we process

Depending on the features used and information entered, Agiles may process:

• Identity and contact details: name, email address, telephone number and profile picture.
• Account and access data: account identifier, organization memberships, role, permissions, account status and authentication information.
• Project data: names, descriptions, assignments and records entered by authorized users.
• Technical and security data: sessions, access records and information needed to protect the service.
• Meeting data: event identifiers, Google Meet links, associated projects and organizations, and the creation or ending of meeting associations.

Users and organizations should avoid adding sensitive or unnecessary personal data to projects and communications.

3. Why we use personal data

• Create and administer accounts, authenticate users and manage permissions.
• Organize projects and enable collaboration within each organization.
• Show contact details of authorized participants to facilitate communication.
• Create and share project-linked meeting URLs when requested.
• Protect the service, prevent unauthorized access and provide technical support.
• Comply with legal duties and respond to legitimate data subject requests where applicable.

Legal grounds depend on the particular activity and may include performance of a contract, compliance with legal obligations, legitimate interests within the law, and consent when required. Not all processing is based on consent.

4. Google Calendar and Google Meet integration

Agiles uses the technical Google account agiles.social@gmail.com to provide meeting links for projects. SaaS users do not have to connect their personal Google accounts to use those links.

Data accessed and permissions

OAuth authorization of the central account may involve basic account identification and the calendar.events.owned permission, used to read, create, change and delete events in calendars owned by the authorized account.

How the integration works

• When a meeting is requested, Agiles sends Google Calendar event details, including the project identifier and name, meeting title and description, and the necessary times.
• Google returns the event identifier and Google Meet URL. Agiles stores them in association with the project and organization so authorized users can retrieve the link.
• Authorization of the central account is maintained on the server with an encrypted refresh token; OAuth secrets are not published on the website.
• Creating and displaying meeting links does not require Agiles to access the audio or video content of calls.

Data received through Google APIs is used to provide the meeting features described here, in accordance with the Google API Services User Data Policy, including its Limited Use requirements. This meeting feature does not use such data for targeted advertising.

You can also read the Google Privacy Policy.

5. Sharing information

Where needed for a feature, information may be shared with:

• Authorized users within an organization or project, according to their access rights.
• Google, to create calendar events and make video conferences available.
• External messaging services such as WhatsApp and Telegram when users choose to open those links.
• Infrastructure and support providers actually used to operate and protect the platform.
• Competent authorities when required by law or a valid order.

Using Agiles does not automatically grant members of one organization access to another organization’s data.

6. Access within organizations and projects

Agiles uses organization memberships, project assignments and four access roles — Collaborator, Analyst, Manager and Principal Manager — to determine available actions. Rights differ according to each user’s role and active associations.

The person responsible for an organization may also be best placed to explain why particular personal information was included in its projects. A functional role in Agiles does not, on its own, determine whether someone is a controller or processor under the LGPD.

7. Cookies, sessions and technical logs

Agiles uses sessions to recognize signed-in users and apply security controls. Technical logs may include dates, times, IP addresses, session identifiers and browser information, depending on the deployment configuration.

Third-party services opened from Agiles, including Google Meet, WhatsApp and Telegram, may use their own cookies and technologies under their respective policies.

8. Data retention and deletion

Information may be retained as needed to operate accounts, organizations, projects and services, or to meet legal obligations and exercise rights. Actual periods depend on the category of information and the retention and deletion processes implemented.

Ended meeting associations may remain in Agiles history. Events created in the central Google account may remain in Google Calendar until separately deleted; ending an association in Agiles does not remove those events automatically.

Deletion requests will be evaluated in light of legal requirements and the responsibilities of the organizations involved.

9. Information security

The platform uses authentication and access controls based on users, organizations and projects. The Google integration runs on the server, and the refresh token is stored in encrypted form.

No technology eliminates every risk. Suspected unauthorized access or misuse of information may be reported to the support channel below.

10. External services and international transfers

Global services, including Google Calendar and Google Meet, may process or store information outside Brazil according to their providers’ infrastructure and policies. Applicable international transfers must comply with the LGPD.

11. Your personal data rights

Subject to the LGPD and applicable conditions, data subjects may request confirmation of processing, access, correction, information on sharing, anonymization, blocking or deletion of unlawfully processed data, portability where applicable, information about consent and its withdrawal when consent is the legal basis.

To submit a request, contact support and explain the right you wish to exercise and your relationship with Agiles. Do not send passwords or unnecessary documents. Proportionate information may be requested to verify your identity.

If information was added by an organization using Agiles, that organization may need to participate in handling the request.

12. Contact and updates

This policy may be updated as the platform, its integrations or legal requirements change. Material changes will appear on this page with an updated revision date.