Privacy Policy
Last updated:
This policy describes how تیمد ("we", "our") handles data when organizations use our recruitment platform and optional Google Calendar integration. For recruiting records, the hiring organization determines its purposes and permitted users. Direct questions about an organization’s recruiting decisions to that organization.
1. Data used by the recruitment service
Depending on the features an organization uses, تیمد processes account and company details, candidates’ contact information and resumes, job criteria, evaluations, stage decisions, interview schedules, feedback and communication records. We also process session and security information needed to operate and protect the service. Organizations must have authority to provide this information.
2. Google account and calendar data
Only an authorized company HR manager initiates Google OAuth consent. تیمد receives the connected account’s verified email and Google account identifier, and stores an encrypted refresh token to keep the authorized connection working in the background. Short-lived access tokens are used to call Google APIs.
تیمد reads the account’s calendar list, including calendar identifiers, names and effective access roles, so a permitted user can choose a writable destination for each تیمد room/calendar. It reads its managed Google event details to reconcile updates and preserve attendee response information. It does not browse unrelated calendar events for recruitment analysis.
openidandemail: identify the account connected to the company.calendar.calendarlist.readonly: list available calendars and their access roles.calendar.events: create, read, update and cancel interview events in the chosen destinations, including existing shared calendars.
3. Purpose of use and storage
Google data is used to identify and maintain the authorized connection, display destination choices and synchronize interview bookings, time changes, participants and cancellations. We store the chosen calendar identifiers/names, event identifiers, interview event snapshots, synchronization state, retry information and relevant administrative audit records. Event snapshots may include the candidate’s name/email, job and stage title, start/end time, onsite location or online meeting link, and interviewer/guest names and emails.
4. Sharing and visibility
تیمد sends the interview details and selected attendees to Google to provide calendar synchronization and invitations. People with access to the destination calendar and invited recipients may see event details under that calendar’s permissions. Your organization controls the destination and invitees; choose them carefully.
Authorized users in the same company can access information within their تیمد permissions. Service providers may process information only as needed to operate, host, secure or deliver the requested features. Google’s own processing is governed by its Privacy Policy. Disclosure may also be required by applicable law or for security. We do not sell Google user data, provide it to data brokers, use it for advertising, or use it for lending or credit decisions.
5. Google data and AI / Limited Use
Google Calendar data obtained through this integration is not used to train or improve generalized AI/ML models and is not sent to resume-analysis or OCR services. Resume analysis is a separate feature using recruiting materials supplied or authorized by the organization, which may be processed by its configured AI/OCR services.
تیمد’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Human access to Google user data is limited to your affirmative permission to inspect specific data, necessary security investigations, applicable legal obligations, or aggregated internal operations allowed by that policy.
6. Retention, disconnecting and deletion
The encrypted refresh token is retained while the connection is enabled. Disconnecting in Settings → Service Connections removes the stored refresh-token credentials and stops further synchronization. You may also revoke access from your Google Account’s connections.
Disconnecting is not a request to delete all recruiting records. Connected-account metadata, chosen destinations, interview snapshots and synchronization/audit history remain with the organization’s records until removed through supported workflows or a verified deletion request, subject to necessary security and legal retention. Existing events in Google remain until separately removed by an authorized calendar user or a supported synchronization action. Copies retained in backups, where maintained, may persist until those backups expire.
For access, correction or deletion requests, contact your organization or info@teamed.ir. Identify the company and relevant account; do not send passwords, tokens or client secrets. We verify the requester’s authority and explain any data that must be retained.
7. Security and changes
We use authenticated sessions, role and company access controls, production HTTPS and authenticated encryption for stored Google refresh tokens. No system can guarantee absolute security. Essential session/security cookies support the application; these public information pages do not load advertising trackers or require a login.
We update this notice when our practices change and seek renewed consent before using Google data for a new purpose that requires it. Contact: info@teamed.ir.