PITMA

PITMA · PRIVACY

Privacy policy

TelegramOpen channel

About this policy

PITMA is a space for learning AI and ML, building projects and connecting with others. This policy explains what data hub.pitma.space processes and how the Google and GitHub integrations work.

For questions about personal data, correcting information or deleting your account, contact the PITMA / Intellectum team at support@intellectum.university. We may ask you to confirm ownership of your account before fulfilling a request.

Account and profile

To register you and operate the platform, we process your email, first and last name, date of birth, gender and selected interests, along with other details you add in settings: photo, username, phone number, country and GitHub links. Date of birth is used to calculate age automatically in administrative statistics.

Your public profile may include your name, username, photo, interests, GitHub links, published implementations and achievements. Public profiles and certificates shared by link can be viewed without signing in and may be indexed by search engines. Email, phone number, date of birth and gender are not displayed on your public profile.

When you sign in with Google or GitHub, we receive your account identifier, email and available basic profile details. The platform does not receive your Google or GitHub password.

Projects and community

We store code, project versions, Pull Requests, reviews, comments, posts, reactions and certificate data to provide these features. Members with access to a project or discussion can view the content published there.

Do not include passwords, access keys or other people's personal data in code, notebooks, execution results or discussions. Before publishing, check the content that will become available to others.

Google Colab and Google Drive

Connecting Colab is optional and requires separate Google authorization. PITMA requests openid, email and drive.file permissions. The drive.file permission is limited to files created by or explicitly shared with the application; the current integration works with notebooks PITMA creates for your projects and Pull Request checks. It does not browse your entire Google Drive or request access to Gmail or contacts.

PITMA creates an .ipynb file in your Google Drive with the project code. Code runs in Google Colab. When you import results, PITMA downloads the corresponding file, prepares the Python code and saves code and text cells, supported text outputs and PNG/JPEG images within technical limits. HTML, SVG, widgets and unnecessary metadata are not included in the version saved for review.

Submitting work to a Pull Request saves a separate notebook version: subsequent changes in Colab do not alter the review already submitted. A reviewer can create a copy of this version in their own Google Drive. Publishing to GitHub is a separate action and transfers Python code and a README, rather than the notebook file.

To communicate with Google, we store the Google account identifier, email, identifiers of created files and an encrypted refresh token. This lets the PITMA server work with these files without requiring sign-in for every action. Tokens are not shared with other platform members.

Google data is used for these user-facing features. We do not sell Google data or use Drive content for advertising targeting or training general-purpose AI models. The use and transfer of information received from Google APIs must comply with the Google API Services User Data Policy, including the Limited Use requirements.

Disconnecting Google

Disconnecting Colab in PITMA removes the integration credentials stored on the platform. It does not delete files in Google Drive or previously imported project and Pull Request versions. To fully revoke permission, remove PITMA's access in your Google account's connections settings. You can delete Drive files yourself.

Analytics and cookies

Essential cookies are used for sign-in and security. For statistics, the platform processes visits, approximate active time, referral sources and campaign parameters, along with approximate country, region and city based on hosting technical data. A random identifier may be used for visits; after sign-in, activity may be associated with your account.

Meta Pixel and Telegram Pixel may operate on sign-in and registration pages to measure referrals and completed registrations. These services may receive browser technical data, cookies, IP addresses and event information according to their own policies. PITMA code does not send them registration form fields or Google Drive content. PITMA's built-in trackers respect Do Not Track and Global Privacy Control signals.

You can manage cookies and tracking protection in your browser. Blocking essential cookies may prevent sign-in.

Services and data access

PITMA uses Vercel for hosting and Supabase for its database and file storage. Connected Google, GitHub and analytics services process the data shared with them under their own rules. Infrastructure providers may process data outside your country of residence.

Administrative features give the authorized team access to user data and statistics for support, security and platform management. Public content is available to the audience of the relevant feature. Data may also be disclosed when required by applicable law.

Retention and deletion

Account and work data is retained to operate the platform while the relevant account or content exists. Contact the team to access, correct or delete your data. Some technical logs, backups or records needed to meet legal obligations may have different retention periods.

Deleting a PITMA account does not delete Google Drive files, GitHub repositories, copies downloaded by others or search engine caches. These are governed by the controls and policies of the respective services.

Useful links

Manage Google connections

Google API Services User Data Policy

support@intellectum.university