Get the weekly research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean. No account.
The policy prohibits use of the service by children under 16 and states that Tabnine does not knowingly collect personal information from this age group, with an exception where parental consent is provided. No mechanism for obtaining or verifying parental consent is described.
This analysis describes what Tabnine's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision engages GDPR Article 8 requirements for children's consent to digital services (age threshold of 16 in the policy, consistent with GDPR's maximum threshold) and COPPA's restrictions on collecting personal information from children under 13 in the US context. The policy does not describe a parental consent verification mechanism, which creates an operational gap relative to regulatory requirements for the stated parental consent exception.
Interpretive note: The policy does not describe a parental consent verification mechanism, creating ambiguity about how the stated exception for under-16 users with parental consent operates in practice.
Under this clause, users under 16 are prohibited from using the service unless parental consent is provided. The policy does not describe the mechanism by which parental consent is obtained or verified, and states that Tabnine does not knowingly collect data from users in this age group.
Cross-platform context
See how other platforms handle Children Under 16 Exclusion and similar clauses.
Compare across platforms →Monitoring
Tabnine has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"The Services not intended for children under the age of 16. We do not, knowingly or intentionally, collect information about children who are under 16 years of age. IF YOU ARE UNDER THE AGE OF 16 YOU MAY NOT USE THE SERVICE, UNLESS PARENTAL CONSENT IS PROVIDED ACCORDINGLY.Excerpt from Tabnine's Privacy Policy
REGULATORY LANDSCAPE: This provision engages GDPR Article 8, which sets age of consent for data processing for information society services at 16 (member states may lower this to 13) and requires verifiable parental consent for users below that threshold. In the US, COPPA applies to online services directed to children under 13 and requires verifiable parental consent. The FTC enforces COPPA. The policy's age threshold of 16 is consistent with GDPR Article 8's default. GOVERNANCE EXPOSURE: Medium. The policy states parental consent may enable under-16 use but does not describe a consent verification mechanism, which is an operational gap relative to both GDPR Article 8 and COPPA requirements for verifiable parental consent. The absence of a described verification process may attract regulatory scrutiny if minors are found to have accessed the service. JURISDICTION FLAGS: EU member states that have lowered the GDPR consent age to 13, 14, or 15 should note that Tabnine's policy applies a uniform 16-year threshold. COPPA applies to US-based users under 13 regardless of the policy's 16-year threshold. UK GDPR and the Age Appropriate Design Code may impose additional obligations. CONTRACT AND VENDOR IMPLICATIONS: Enterprise customers deploying Tabnine in educational or youth-oriented contexts should assess whether the platform's age restriction and parental consent provisions are consistent with their own obligations under COPPA, FERPA, or applicable state student privacy laws. COMPLIANCE CONSIDERATIONS: Compliance teams should assess whether any technical or procedural age verification mechanisms are in place to support this policy commitment. The absence of a described parental consent mechanism is a review area for organizations operating in contexts where minor users are foreseeable.
This provision engages GDPR Article 8 requirements for children's consent to digital services (age threshold of 16 in the policy, consistent with GDPR's maximum threshold) and COPPA's restrictions on collecting personal information from children under 13 in the US context. The policy does not describe a parental consent verification mechanism, which creates an operational gap relative to regulatory requirements for …
Under this clause, users under 16 are prohibited from using the service unless parental consent is provided. The policy does not describe the mechanism by which parental consent is obtained or verified, and states that Tabnine does not knowingly collect data from users in this age group.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Tabnine.