Privacy policy

Who we are

git.team is operated by FRONTAL, a TALOS company (“we”, “us” or “our”). FRONTAL is responsible for the handling of personal information described in this notice. Our privacy contact is thetalosteam@gmail.com.

This notice applies to git.team, including its developer news, public portfolios, project pages and Application Studio. It does not cover other FRONTAL or TALOS group websites, or third-party sites you visit through links. Group affiliation does not change which information you publish on git.team.

Information we handle

• Account information: when you sign in through Google or GitHub, we receive the account identifiers, name, email address and profile information made available through that sign-in. Supabase manages authentication and session credentials. We do not receive your Google or GitHub password.
• Profile and project content: the name, biography, work history, education, skills, contact links, projects, case studies, media references and appearance settings you provide.
• Application information: job descriptions, profile facts, CVs, cover letters, application status and other draft content you enter or explicitly save in Application Studio.
• Preferences: your theme, selected news topics, bookmarks and locally saved drafts.
• News metadata: publicly available publisher headlines, links, dates and topic labels, which can mention people. Our news index links to the original publication rather than storing its full article body.
• Technical information: hosting and analytics services may process your IP address, browser and device information, requested pages and URLs, referring pages, timestamps, usage events, errors and performance information.
• Communications: information you include when you contact us, including correspondence needed to handle support or privacy requests. Email sent to our Gmail contact address is also processed by Google’s email service.

Creating a profile and providing its content are voluntary. Sign-in information is needed for account features; without it, we cannot provide account access or cloud saving. You can read the news without creating an account. Please do not include sensitive information about yourself or someone else unless it is necessary and you are entitled to provide it.

Why we use it

We use information to authenticate users, operate and display portfolios, save requested content, organize relevant news, remember preferences, provide support, understand service usage, detect abuse, maintain reliability and meet applicable legal obligations.

Where data-protection law requires a legal basis, the relevant bases are providing the service you request, our legitimate interests in security, reliability and support, compliance with legal obligations, and consent for optional tracking or advertising where required. Where processing relies on consent, you may withdraw it without affecting processing already lawfully carried out.

Application Studio currently builds documents using browser-based templates and matching against the facts you supply. It does not send your document text to a generative-AI provider or submit applications to employers. You decide what to edit, export, save or send. It does not make hiring decisions about you.

Public profiles and projects

New profiles are public by default. Public profile and project pages, including any contact details or media you put on them, can be viewed by other people, shared and indexed by search engines. An unfamiliar or unlisted URL is not a privacy control. Do not publish confidential client work, private contact details or material you do not have permission to share.

Cloud application drafts are not public portfolio content. They are associated with your account and protected by account-access controls. Authorized operational access may still be needed to support, secure or maintain the service.

You can edit available profile and project fields while signed in. To request unpublishing, account deletion or help with information you cannot change through the interface, contact us. Removal from git.team does not instantly remove search-engine caches, copies other people made or material hosted elsewhere.

Cookies and browser storage

Authentication uses session cookies and related credentials to keep you signed in and protect account functions. Browser storage also remembers your theme, news topics and bookmarks.

Guest Studio drafts saved in the browser use session storage, normally for the current tab session; browser session restoration can preserve them. Signed-in browser drafts use local storage scoped to the account. Browser storage is not the same as cloud saving and is not synchronized automatically between devices. Avoid saving private drafts on a shared device.

We use Google Analytics on the service to understand visits and usage. It can use cookies and process technical information about your device, pages and interactions. This privacy page does not load our Google Analytics tag. See how Google uses information from sites that use its services and the Google Analytics opt-out browser add-on.

You can remove saved drafts and bookmarks using the available controls, and clear or restrict cookies and site storage through your browser. Clearing authentication storage can sign you out; clearing local storage can permanently remove browser-only drafts. Browser controls and extensions differ and may not stop every type of technical processing.

Advertising

Advertising status: AdSense ownership verification is in place, but ad serving is not currently enabled.

When advertising is enabled, our AdSense integration is limited to News pages, not profiles, project case studies, Application Studio or account pages. Third-party vendors, including Google, may use cookies and similar technologies to serve ads based on previous visits to git.team or other websites. Google’s advertising cookies allow Google and its partners to personalize ads based on those visits.

Advertising vendors may also use web beacons, IP addresses and device information to deliver and measure ads, limit repetition and prevent fraud. Non-personalized ads may still involve storage and technical processing; turning off personalization does not necessarily remove ads.

You can manage Google ad personalization through Google’s ad settings. Other participating vendors offer choices through industry advertising opt-out controls. See Google’s advertising information and Google’s privacy policy for more detail.

Where a consent message is presented, use its choices to accept, reject or manage the purposes and vendors it lists, and its available privacy controls to revisit those choices. We are completing the consent setup before enabling advertising. An advertising message is not automatically a control for all analytics or external-media processing. Reading this policy or continuing to browse is not, by itself, consent to optional tracking.

Service providers and external media

We use providers to deliver the service: Cloudflare for hosting, delivery and security; Supabase for account authentication and database storage; and Google for the analytics, email and conditional advertising described above. Google or GitHub also processes your sign-in under its own terms when you choose that provider.

Project covers and linked media are external URLs, not media files hosted by git.team. Images and covers may load when the page displays them. Gallery players and supported interactive embeds load when you choose their Load control. Their hosts can receive your IP address, browser information and other request information, and may use their own cookies or storage. Examples include YouTube, Vimeo, Loom, Google Drive and CodePen; the actual provider depends on the content linked by the profile owner.

Where the optional avatar or experience-image upload feature is used, the selected image passes through our upload endpoint to ImgBB. The resulting image link may be publicly accessible. Deleting a profile or link on git.team does not automatically delete a file from ImgBB or another external host. Contact the host, or ask us for assistance, if you need an externally hosted file removed.

We may disclose information when reasonably necessary to comply with law, respond to a valid legal process, protect people or the service, or handle a business transfer with appropriate protection for the information. This notice does not authorize unrelated group marketing. News publisher links and other external sites have their own privacy practices.

Retention and deletion

• Account and portfolio records: kept while needed to provide your account and published work, subject to deletion requests and any necessary legal or security retention.
• Cloud Studio drafts: kept until you delete them, request their removal or the account data is removed, subject to applicable retention obligations.
• Browser-only drafts and preferences: remain according to the storage behavior described above, until you remove them or the browser clears them.
• Support, security and technical records: kept for as long as needed to resolve requests, investigate issues, protect the service and satisfy applicable obligations. Provider retention settings and the purpose of each record affect these periods.

Deletion from active systems may not immediately remove backups, logs or cached copies; those can remain until their applicable retention or replacement cycle ends. We do not promise an instantaneous purge of every provider’s systems. Ask us about a particular record or request, and we will explain the applicable handling.

International processing

Our primary application database is hosted through Supabase in Tokyo, Japan. Cloudflare operates a global network, and our other providers may process information in other countries, including the United States. Your information may therefore be processed outside your country, where data-protection laws can differ.

Applicable transfer requirements depend on the data, the countries involved and the provider arrangements. You can contact us for information about the location and safeguards relevant to your information. This notice is not a claim that data stays exclusively in Israel or in your home country.

Your choices and rights

Depending on the law that applies and the circumstances, you may have rights to access information about you, correct inaccurate information, request deletion, restrict or object to processing, receive portable data, and withdraw consent. Some rights have legal exceptions. You may also complain to the relevant data-protection authority, including Israel’s Privacy Protection Authority or the authority in your country where applicable.

Send requests to thetalosteam@gmail.com, identifying the relevant account or page and what you would like us to do. Do not send passwords, session tokens or unnecessary identity documents. We may ask for proportionate information to verify your identity before disclosing or changing account data. We will respond within the time required by applicable law; where GDPR applies, that is generally one month, with any permitted extension explained.

Security and younger users

We use access controls and transport encryption to help protect information. No online service or storage system is completely secure. Keep your sign-in provider account secure and tell us promptly if you suspect misuse.

git.team is intended for a general developer audience, not specifically for children. If you are below the age at which you can consent to the relevant processing under local law, involve a parent or guardian. If you believe a child’s information has been provided without the required authorization, contact us so we can review and address it.

Changes and contact

We may update this notice as the service or its data practices change. The date at the top identifies the latest version. Where required, we will provide additional notice or seek consent before introducing a materially different use.

For privacy questions, requests, or information about the responsible operator, email thetalosteam@gmail.com.