Privacy Policy

Effective Date: October 31, 2026

ProfoundSyntax respects the privacy and security of the people who use our developer community. This Privacy Policy explains what information we collect, why we collect it, how it is used, when it may be shared, how long it may be retained, and the choices and rights available to you.

This Privacy Policy applies to ProfoundSyntax, including profoundsyntax.com, member accounts, developer profiles, member-created Communities, public and private community features, Wiki tools, Feedback tools, connected integrations, account-security features, identity-verification features, notifications, moderation systems, and related services operated by ProfoundSyntax.

Information You Provide to ProfoundSyntax

Account Information

When you create or maintain an account, we may collect information such as your email address, username, public @handle, first name, last name, account preferences, profile settings, registration information, and records needed to operate and secure the account.

Your public @handle is managed separately from your underlying login identity. ProfoundSyntax may maintain limited handle history and reservation information to prevent impersonation, collisions, abuse, and immediate reuse of former handles.

Developer Profile Information

You may choose to provide a profile image, biography, website, GitHub profile, programming languages, technologies, development interests, and other profile information. Profile and activity visibility may depend on your account settings and ProfoundSyntax configuration.

Professional Profiles and Industry Credits

If you use Industry Credits, ProfoundSyntax may store the professional information you choose to submit, including game or product title, participation category, credited role, credited-as name or professional alias, studio or company, release year, platforms, contribution summary, external evidence URL, optional linked ProfoundSyntax Project, Featured status, cover source, and cover-rights declaration where applicable. You may also provide an external professional-profile URL, such as a MobyGames person profile, plus member-reported information about whether you control that external profile or added your ProfoundSyntax profile URL there.

Industry Credits are intended for public professional-profile use when your profile is visible. Public Industry surfaces can display submitted credit facts, evidence/source links, Featured status, source or administrator-review labels, linked Projects, and external professional-profile links. A saved external professional-profile URL may also be included as an identity reference in public structured data. Do not submit confidential employment records, private contracts, private contact information, credentials, or other information you are not authorized to make public.

ProfoundSyntax may store credit-review metadata such as review state, reviewer account identifier, review time, and a fingerprint of the reviewed credit facts so a material edit can invalidate an older review. An Administrator reviewed label means only that ProfoundSyntax staff reviewed the submitted credit against the available evidence; it does not mean the external provider, publisher, studio, employer, or platform verified or endorsed the member or the credit.

If the optional IGDB cover lookup is enabled and you deliberately use Find Cover, ProfoundSyntax sends the game title you entered to the IGDB API and may load the cover image you select from IGDB’s image service. IGDB/Twitch can receive the requested title and ordinary request or connection metadata under their own terms and privacy practices. ProfoundSyntax does not scrape MobyGames for this feature. Manually selected Media Library covers remain member-supplied content and can require a rights-basis and permission confirmation before a new or replacement cover is saved.

Industry Credit categories may also be compared locally with open Project collaboration-role categories to show advisory professional-fit context to the member or Project owner. This matching is informational only and does not automatically invite a member, grant Project access, award reputation, determine employment, or make an eligibility decision.

Community Content

We collect and store content you submit, including Questions, Discussions, Code posts, Tutorials, Projects or Showcases, Resource or News posts, replies, answers, code blocks, edits, reports, and other community contributions.

Community content may include edit-history information so authorized users or moderators can review changes when necessary for discussion integrity, moderation, abuse prevention, or dispute resolution.

Do not post passwords, private API keys, access tokens, financial credentials, private encryption keys, confidential client information, private personal information, or other secrets in public content.

Intimate-Image Removal Requests

ProfoundSyntax provides a public no-account process for an identifiable person shown in an intimate image or video, or an authorized representative, to request removal. A request may include the requester’s name, the identifiable person’s name, representative-authority information when applicable, contact email and optional phone, ProfoundSyntax content locations, a good-faith non-consent statement, an electronic signature, the request reference, status history, site-staff notes, and records of removal or exact-copy actions.

Sensitive request fields are stored in encrypted form where supported by the ProfoundSyntax legal-request workflow. The private status token is not stored in readable form after issuance. Access to the private request queue is limited to authorized site staff. ProfoundSyntax does not ask requesters to upload or resend the intimate image or video through the removal form.

ProfoundSyntax may retain limited request, contact, status, cryptographic exact-file hash, action, and audit records as reasonably necessary to process the request, document compliance, prevent re-upload of material that has been confirmed for removal, protect people, prevent abuse, or satisfy legal obligations. Exact-file hashes are used to identify byte-for-byte copies of ProfoundSyntax-hosted media and do not reconstruct the original image or video.

ProfoundSyntax Live

If you create or watch a ProfoundSyntax Live broadcast, ProfoundSyntax may process broadcast titles, descriptions, lifecycle state, audience settings, creator and Community relationships, broadcaster connection state, short-lived playback authorization, offline/channel branding images, social-preview images, and related operational or moderation records needed to operate and protect Live.

Your personal-data export can include Live broadcasts you authored without exposing broadcaster credentials. If account erasure applies to authored Live records, ProfoundSyntax disconnects any active publisher, makes those broadcasts non-publishable/Removed, clears creator-entered title/description and publisher credentials, and detaches your member identity. A minimal anonymous lifecycle or safety record may remain only until the configured Live retention purge where retention is needed for operational integrity, abuse prevention, or legal obligations.

While an authorized Live video is actually playing, ProfoundSyntax records a privacy-bounded first-party viewing heartbeat for that broadcast so authorized stream managers can review current viewers, peak viewers, unique viewers, minutes watched, and average watch duration. Aggregate Broadcast analytics are available only to the broadcaster, site administrators, and the owner of the attached Community. The Live viewing analytics record uses a per-broadcast pseudonymous viewer key and timing totals; it does not store the viewer’s IP address, user-agent string, or playback bearer token. For signed-in managers, ProfoundSyntax may also store whether the Broadcast analytics accordion is open or closed as a private interface preference. Signed-in account identifiers and that interface preference participate in personal-data export/erasure, and erasure detaches both the account identifier and stable viewer key while retaining anonymous aggregate totals.

Creators may upload default offline and social-preview images and may capture a current playing frame as a broadcast social preview. Eligible Pro creators may choose automatic recurring live-frame social snapshots for eligible Public broadcasts while their own Watch page remains open. Automatic live-frame snapshots are not used for protected audiences or Restricted/Private Community broadcasts. Saved Live images are handled as creator-controlled media and can be replaced or removed through the available controls.

When a broadcast is attached to a member-created Community, ProfoundSyntax also uses the Community’s current ownership, lifecycle, visibility, membership, ban, and moderation relationships to decide whether the broadcast may be started, published, surfaced on the Community page, or viewed. Private Community access remains stronger than a broadcast’s saved audience. A Community broadcast is not publicly surfaced to a viewer who is not authorized to know about it.

ProfoundSyntax Live Chat is a broadcast-scoped conversation associated with an authorized Live Watch page and is separate from Private Chat. Depending on the broadcast audience, authorized guests may read Live Chat while eligible signed-in Free and Pro members may send messages when Chat is open. ProfoundSyntax processes Live Chat message text, sender identity, timestamps, the creator’s Chat enabled/disabled setting, blocks, safety reports, broadcast-scoped timeouts or bans, and moderation actions needed to deliver and protect the conversation. A creator may turn Chat off or back on without deleting the retained broadcast-scoped Chat history.

Live Chat history remains tied to the broadcast so an Ended broadcast may retain its conversation. Permanently purging the broadcast also removes its Live Chat messages, sanctions, and reports. If an account is erased or deleted while the broadcast record remains, ProfoundSyntax detaches that member’s account identity from retained Live Chat rows where appropriate while preserving audience-scoped message text and limited moderation evidence needed for context, safety, or audit purposes.

Live Chat can also process broadcast-scoped reply relationships, Global or broadcaster emote references, GIF-provider media references, broadcaster Live Chat Rules, and viewer display preferences needed to provide the current Chat experience. Signed-in viewer preferences such as Chat Filters, Pause Chat mode, Screen Reader Auto Announce, GIF visibility, timestamps, reply display, font size, and readable-color preferences are stored privately with the member account; logged-out viewer preferences stay in that browser rather than creating a server-side guest profile. Viewer Chat Filters change only that viewer’s presentation and do not rewrite the canonical message or moderation record.

Broadcaster custom Live emotes are creator-controlled image assets and library metadata. If a broadcaster’s Pro entitlement ends, retained emotes may remain stored but unavailable for new use until eligibility returns. Personal-data erasure removes the broadcaster’s retained Live-emote assets/library metadata and broadcaster-specific Live Chat Rules; historical Chat messages fall back to readable emote aliases when the associated image is no longer available.

When an eligible viewer searches the GIF catalog, the browser may send the viewer’s search phrase and ordinary connection metadata directly to the administrator-configured GIF provider and load selected GIF media from that provider. ProfoundSyntax stores the selected provider/media reference and any typed Chat comment needed to deliver, moderate, export, or later display that Chat message; ProfoundSyntax does not copy the provider GIF file into the normal Live Chat media store solely because it was selected in Chat.

The Live Chat Community viewer panel uses current broadcast presence to show the broadcaster and eligible signed-in viewers/moderators while the panel is open. Anonymous viewers are represented only as a count. The panel does not expose viewer IP addresses, email addresses, private moderation notes, or the internal analytics viewer key. Hide Chat and Popout Chat are viewer-interface states and do not create a second copy of the conversation.

When a broadcaster enables Live captions, ProfoundSyntax may process short synchronized caption text, caption language, the authorized account that submitted a manual caption, and timing/sequence information needed to deliver captions to eligible viewers. Live caption cues are delivered through a first-party access-controlled channel separate from the video stream, are retained only for a short operational window, and are automatically purged. Privacy erasure detaches manual caption-author identity or removes broadcast-scoped caption data as appropriate.

If a broadcaster selects Automatic captions, the ProfoundSyntax Live server extracts the broadcast audio track and sends audio-only speech data to the active administrator-configured speech-recognition provider for real-time transcription. Administrators can configure a preferred provider and, when automatic provider failover is enabled, a compatible configured fallback may receive subsequent speech audio if the active provider has a quota, account, connection, or service failure. Only the active recognition provider is used for a caption session at a time; the automatic-caption feature does not send Live video frames, Live Chat messages, publisher credentials, or viewer authorization tokens to speech providers. Running transcript previews may be delivered briefly to authorized viewers to reduce caption delay; those previews are ephemeral and are replaced by finalized caption cues rather than added to the retained caption history. ProfoundSyntax stores finalized returned caption cues under the same short caption-retention rules and keeps bounded provider-usage, provider-health, failover, and worker-health metadata needed to operate the feature. Provider processing is also subject to the active provider’s service and privacy terms.

Member-Created Communities and Wikis

When you create, own, moderate, join, or contribute to a Community, ProfoundSyntax may process Community identity, visibility, membership, ownership, moderation, rules, Wiki pages, revisions, publication-review status, scheduled content, archive status, and related audit information needed to operate that Community.

Public Community Wiki pages may be distributed through public feeds or connected services. Restricted or Private Community content remains subject to the applicable access controls and is not eligible for public external Wiki transfer unless ProfoundSyntax later provides a clearly disclosed feature that changes that rule.

Private Chat, Group Chat, and Mod Mail

One-to-one Private Chat, Group Chat, and Community Mod Mail are not public posts. ProfoundSyntax stores the messages, conversation participants, Group Chat names and participant roles, invitation/request/acceptance state, read state, blocks, reports, moderation context, and related delivery information needed to provide those features. Accepted Private Chats and Group Chats may also include eligible locally uploaded images, videos, and file attachments. Private Chat media is encrypted by ProfoundSyntax before it is written to private storage and is served through authenticated access checks rather than ordinary public media URLs. We may process the original file name, MIME type, file size, uploader, conversation/message relationship, and storage information needed to validate, deliver, remove, and moderate that media. Group Chat invitations are subject to the same account eligibility, profile/privacy, Chat preference, blocking, and safety controls used by Private Chat. Pending one-to-one Chat requests remain text-only until the recipient accepts the request. Authorized administrators may access reported private communications and their associated private media when reasonably necessary to investigate reports, enforce rules, protect users, comply with law, or maintain service security.

Members invited to a Group Chat receive access according to the invitation state and the Group Chat history cutoff applied when they are invited; prior group history is not automatically exposed to a later invitee. Archiving a Group Chat is a reversible personal organization action. Deleting an archived Group Chat removes that member’s retained local history through the deletion cutoff but does not leave the group, transfer ownership, or delete other members’ copies. Later legitimate group activity may return the Group Chat to that member’s Messages view without restoring history at or before the deletion cutoff. Leaving or removal is a separate membership action that ends that member’s access unless a valid later invitation is accepted.

When Private Chat message translation is enabled and a member has automatic eligible-content translation turned on, ProfoundSyntax may translate that member’s authorized Chat message display into the member’s selected language. Private Chat message bodies use the ProfoundSyntax-controlled local translation service only and are not sent to a configured cloud translation provider for this feature. The stored original message remains authoritative and unchanged. A translated display may be cached separately for the configured translation-cache period, and the member can switch between the translated display and the original message. Protected technical strings such as code-like text, URLs, handles, paths, commands, and similar technical content are preserved where the translation system can identify them.

Archiving a private conversation hides it from the ordinary conversation list but does not necessarily delete the underlying conversation. Where a permanent-delete or leave control is offered, it changes that member’s access/copy according to the feature’s current behavior while other participants may retain their own conversation history, subject to limited safety, audit, legal, or abuse-prevention records that may need to be retained.

Feedback, Diagnostics, and Private Screenshots

When you submit a bug report or feature suggestion, ProfoundSyntax may collect the information you enter plus privacy-limited technical context that helps reproduce the issue, such as the originating page, browser/device characteristics, selected language and appearance preferences, relevant Community relationship, and current ProfoundSyntax build information.

Bug reporters may choose whether to include recent sanitized same-site script errors. ProfoundSyntax is designed to remove or redact common credentials, authorization values, query parameters, and unrelated private form contents from this diagnostic context.

If you attach a Feedback screenshot, supported images are processed to remove embedded metadata where practical, encrypted for private storage, and made available only to you and authorized Feedback administrators through protected access. Feedback screenshots are not intended to become public media.

Business Inquiries and Optional CRM Follow-Up

ProfoundSyntax provides a separate private Business Inquiry workflow for consultation, project, partnership, and similar business contact. The inquiry type, subject, message, account relationship, workflow status, and related administrator notes are stored inside ProfoundSyntax and are separate from the Site Feedback bug/feature ledger.

If the site administrator enables HubSpot CRM follow-up, the Business Inquiry form may offer a separate optional consent checkbox. Only when you explicitly select that checkbox may ProfoundSyntax send your current account email, first name, and last name to the site-owned HubSpot CRM connection so the team can follow up. The Business Inquiry subject and message are not sent to HubSpot by this feature. HubSpot then processes the transferred contact fields under its own services and safeguards. If you do not select the CRM consent checkbox, the inquiry can still be submitted privately to ProfoundSyntax without the HubSpot contact handoff.

ProfoundSyntax may store follow-up messages exchanged between the member and authorized administrators as part of the private Business Inquiry history. Follow-up email notifications may be sent through the site’s configured mail-delivery service, but the authoritative follow-up history remains inside ProfoundSyntax. Business Inquiry follow-up messages are not mirrored to HubSpot by this feature.

Career Applications and Recruiting

When you apply for a ProfoundSyntax role, we may process the information you intentionally submit for recruiting purposes, including your name, email address, optional phone number, current location, portfolio or professional-profile URL, work-authorization and sponsorship responses, availability or notice period, cover-letter or application statement, the role you applied for, application status, and related recruiting history.

Résumés and optional cover-letter files submitted through the native Careers application workflow are not stored as ordinary public WordPress Media Library attachments. Supported documents are encrypted before ProfoundSyntax writes them to private application storage and are made available to authorized recruiting administrators only through protected download checks. ProfoundSyntax may retain document metadata such as the original filename, MIME type, file size, integrity hash, and upload time as needed to operate and secure the recruiting workflow.

Authorized recruiting administrators may assign an application for review, change recruiting status, add internal recruiting notes, and access the applicant’s submitted materials. ProfoundSyntax may also retain private recruiting-operation data such as interview stage, scheduled interview time and duration, interview format or meeting/location instructions, assigned interviewers, interview outcome and internal interview notes. Recruiter messages sent to an applicant through the native Career Applications workspace may be retained with delivery-result metadata so authorized administrators can understand the recruiting communication history. These actions may be recorded in restricted audit/history records.

Applicant information is used for recruiting and related administrative, security, legal, or compliance purposes and is not used by Session Activity diagnostics or Advertising targeting. ProfoundSyntax personal-data export and erasure tools include the native Career Applications workflow; when applicant data is erased, ProfoundSyntax removes private applicant identity, submitted documents, recruiting notes, interview-operation records and retained candidate-message content while a minimal non-identifying application/audit shell may remain where needed to preserve recruiting-process integrity or legal records.

Ask ProfoundSyntax Browser Extension Draft Handoffs

If you choose to connect the Ask ProfoundSyntax browser extension, ProfoundSyntax creates a revocable member-specific extension key. The full key is shown to you only when it is created or rotated. The persistent connection stores a one-way verification hash and limited key metadata; the one-time reveal is held only briefly in encrypted form so it can survive the account-page redirect, then is deleted when displayed or when it expires.

The draft-handoff endpoint accepts only information you explicitly choose to transfer, such as selected text, selected code, an optional question-title hint, an optional language or Topic hint, and an optional source page title or URL. ProfoundSyntax does not use this feature to fetch, scrape, or automatically upload the rest of the source page. Common tracking parameters are removed from source URLs, and credential-like URL parameters are removed when detected.

On the server, transferred material is stored as a short-lived, account-bound draft handoff so the normal ProfoundSyntax Question form can be prefilled for your review. The handoff does not publish anything. You must still open ProfoundSyntax, review the exact transferred material, complete the normal required posting fields, and submit through the ordinary posting flow. Draft handoffs expire automatically and are invalidated when the extension key is rotated or revoked. After the form opens, the site’s existing draft-protection feature may save your in-progress form locally in that browser under the same rules used for other ProfoundSyntax drafts.

ProfoundSyntax performs limited pattern checks for likely passwords, private keys, access tokens, and similar credentials before accepting a handoff. These checks can produce warnings and are not guaranteed to identify every secret. Do not transfer credentials or confidential information. Security and audit records for this feature are designed to record operational metadata such as transfer size, time, warning count, and whether a source URL was present without copying the transferred draft content into the audit log.

Votes, Reputation, Saves, Follows, and Activity

ProfoundSyntax may record upvotes, downvotes, vote changes, accepted answers, reputation activity, Topic-specific reputation, badges, saved content, followed Topics, followed discussions, mentions, reports, blocking relationships, and other community interactions.

Private Content Insights

ProfoundSyntax may collect privacy-limited performance counters for Discussions and replies so the author can privately understand how their own content is performing. These counters may include views or eligible feed impressions, shares initiated through ProfoundSyntax, vote and reply totals derived from existing Community records, Recognition totals, and first-24-hour view aggregates. When the hosting layer supplies a trusted country code, ProfoundSyntax may store only aggregate country-view counts for the content Insights display; the Insights feature does not store a raw network address as location analytics. Content Insights are visible only to the content author in the member-facing interface; administrator analytics remain separate.

Social Sign-In and Connected Providers

When enabled, ProfoundSyntax may allow you to sign in or create an account through supported third-party identity providers such as Google, GitHub, Discord, LinkedIn, or X.

We may receive a provider-specific identifier and limited profile information made available through permissions required for sign-in. Provider access tokens are used to resolve authentication and are not intended to be retained as permanent ProfoundSyntax profile data.

If a provider does not supply information required to safely create an account, ProfoundSyntax may require another registration or verification method instead of inventing missing information.

Connected Repositories and External Wiki Services

An eligible Community owner may choose to connect an external code repository or another supported service to a Public Community Wiki. When you authorize such a connection, ProfoundSyntax may process the external account/installation identifier, selected repository identifier and name, selected branch or folder, mapped Wiki file paths, synchronization status, revision identifiers, and related connection/audit information needed to provide the integration.

ProfoundSyntax uses the authorization granted for the selected connection to read or write the files you direct the service to synchronize. Temporary authorization material may be used during connection and repository selection; ProfoundSyntax is designed not to retain your general external-account user token as permanent Community profile data after repository selection.

Automatic synchronization is optional. When enabled, mapped public Wiki content may be transferred between ProfoundSyntax and the connected repository according to the selected sync mode and schedule. You are responsible for choosing a repository you are authorized to use and for understanding that public Wiki content synchronized to an external service is also subject to that service’s terms and privacy practices.

Translation and Assisted Processing

ProfoundSyntax may translate eligible interface or community text and may provide assisted content-quality features. Processing may occur on ProfoundSyntax-controlled systems or, when an administrator enables an external provider for a particular feature, through that provider. The feature interface and this Privacy Policy should be reviewed together when private or sensitive content is involved. Do not submit secrets merely because a feature offers translation or automated assistance.

Account Security Information

Depending on the features you enable, ProfoundSyntax may process information associated with authenticator-app multi-factor authentication, a ProfoundSyntax Security PIN, one-time recovery codes, verified-email recovery, trusted browsers, active sessions, linked social providers, sensitive-change verification, and security notifications.

Where supported, security secrets are encrypted or stored using one-way hashes rather than directly readable values. ProfoundSyntax does not attempt to read or reuse the PIN or password you use to unlock your computer, phone, or operating system.

Verified Email Recovery

If you enable verified-email recovery, ProfoundSyntax may send a short-lived one-time code to the email address associated with your account. Raw recovery codes are not intended to be stored after generation. Verification records may instead use one-way hashes, expiration information, challenge identifiers, attempt counters, and rate-limit data.

Real-Name Review and Identity Verification

ProfoundSyntax may use first-name and last-name information as part of participation, name review, or optional identity verification. Public display of a real name, @handle, or both may depend on site configuration.

Automated formatting or similarity checks may flag a submitted name for human review. These checks are intended to identify obvious placeholders, impersonation attempts, or suspicious formatting and do not by themselves prove or disprove identity.

Optional Identity Proof

If you voluntarily submit an approved identity document, such as government-issued photo identification, it is treated as highly sensitive information. Identity-proof files are designed to be stored outside normal publicly accessible media areas, protected from public access, encrypted at rest using authenticated encryption where secure key configuration is available, and made available only to specifically authorized reviewers.

The identity document itself is intended to be deleted after the verification decision. ProfoundSyntax may retain limited decision metadata such as verification status, submission date, review date, reviewer action, denial reason, revocation history, or related audit information.

A verified badge means only that the applicable identity-review process was completed. It does not represent endorsement, expertise, employment verification, or a guarantee that a member’s contributions are accurate.

Notifications and Email

ProfoundSyntax may provide on-site and, when enabled, email notifications for replies, nested replies, @mentions, accepted-answer changes, followed discussions, followed Topics, moderation actions, account-security activity, identity-review decisions, and other relevant events.

Members may control supported notification categories through account preferences. Certain important security, moderation, recovery, or administrative notices may be delivered regardless of ordinary community-notification preferences when necessary to protect the account or operate the service.

Moderation, Reports, Appeals, and Abuse Prevention

ProfoundSyntax may process information associated with reports, moderator notes, content removals, warnings, suspensions, bans, appeal submissions and outcomes, duplicate-content detection, excessive-link detection, rate limits, suspected coordinated voting, vote manipulation, ban evasion, and other abuse signals.

Moderation and security decisions may be recorded in audit logs so authorized staff can review disputes, prevent repeated abuse, and protect service integrity. Not every internal moderation or security record is made public or included in a member-facing data export.

A banned member may be given a restricted account area to submit appeals. ProfoundSyntax may configure a maximum number of denied appeals. When that limit is reached, the account may become Final Permanently Banned. A Final Permanent Ban cannot be reinstated or cleared through the normal moderation process; normal authentication is disabled and a timed account-purge process may begin.

To reduce straightforward ban evasion after a final-ban purge, ProfoundSyntax may retain limited keyed or cryptographic fingerprints derived from account identifiers such as the normalized email address, username, public handle, or connected sign-in-provider identifier. These retained enforcement values are used for account-protection and re-registration blocking rather than as ordinary public profile information.

Safety, Child-Protection, and Legal Requests

ProfoundSyntax may process reports and legal or safety requests involving suspected child sexual abuse material (CSAM), grooming, sextortion, child sex trafficking, non-consensual intimate imagery, sexual exploitation, threats, fraud, controlled-substance transactions, copyright complaints, or other potentially unlawful activity. Review may include the reported content, account and Community relationships, relevant messages or media, timestamps, network/security records, and other information reasonably necessary to investigate, preserve evidence, remove or restrict material, prevent re-upload, enforce the Rules, or satisfy a legal duty.

ProfoundSyntax uses the term child sexual abuse material (CSAM) for sexually exploitative images or videos involving minors, even though some U.S. statutes continue to use the term “child pornography.” Where U.S. law requires a qualifying provider to report apparent child sexual exploitation to the National Center for Missing & Exploited Children CyberTipline or another authority, ProfoundSyntax may preserve and disclose information reasonably necessary to make or support that report. Do not download, copy, redistribute, or forward suspected CSAM merely to report it.

Removal requests involving non-consensual intimate images, including eligible digitally created or altered depictions, may require ProfoundSyntax to process requester identity/contact information, the location of the material, a signature or electronic signature, a good-faith non-consent statement, and status/history needed to process the request and document the response. Where a legally valid request is subject to a statutory deadline, ProfoundSyntax may retain limited request and action records needed to demonstrate compliance, prevent reappearance, resolve disputes, or cooperate with lawful authorities.

User Blocking

Members may be able to block other members. Blocking is designed to reduce ordinary discovery and direct interaction while preserving discussion structure and necessary moderation or security functions.

Technical, Device, Cookie, and Session Information

Our systems and service providers may process IP address, browser type, device information, request timestamps, referring pages, error information, session data, security-event data, and information necessary to detect abuse or maintain the service.

For administrator-only account review, ProfoundSyntax may retain the server-seen IP address and broad browser/operating-system family associated with a new self-service registration and the most recent successful login, together with the corresponding login timestamp. Registration network details are collected prospectively, so older accounts may not have a historical signup IP on record. These account-context fields participate in ProfoundSyntax personal-data export and erasure.

We may use cookies, browser storage, session identifiers, or similar technologies to keep you signed in, remember interface preferences, maintain security state, remember trusted-browser status, and support other site functionality.

Hosted Projects using an eligible persistent-browser Runtime profile may save Project-specific data in browser storage controlled by the isolated ProfoundSyntax Runtime shell. This saved data stays in the current browser/device and is not synchronized to the ProfoundSyntax application server through the storage bridge. It is scoped to the applicable Project and can be cleared from the hosted Project viewer or through browser site-data controls. Clearing browser data, private-browsing behavior, browser storage eviction, or changing devices can remove it. Because this data is browser-local, deleting a Project or account on ProfoundSyntax cannot reliably erase copies already stored in a visitor’s browser; visitors can clear those local copies through the available browser/runtime controls.

Privacy-Safe Session Activity and UX Diagnostics

ProfoundSyntax may use a first-party Session Activity diagnostic system to understand navigation flow, clicks, scrolling, viewport/layout behavior, route changes, and structural JavaScript errors so authorized administrators can diagnose usability and technical problems. The replay is reconstructed from bounded interaction metadata and text-free layout geometry; it is not a literal screen or video recording.

Session Activity is designed to apply privacy exclusions before storage. Raw keyboard input, ordinary form-field values, page text, cookies, authorization credentials, authentication/session tokens, request or response bodies, and raw IP addresses collected solely for replay are not stored in the replay dataset. Password/MFA/recovery flows, checkout/payment and saved-payment areas, identity/KYC material, private Chat or Mod Mail content, secrets/API or webhook credentials, file-upload contents, protected downloads, and equivalent sensitive surfaces are blocked or represented only as opaque geometry where needed to preserve layout context.

Replay records may include a short-lived first-party session identifier stored server-side as an opaque hash, coarse browser/device classification, route paths without query strings, timestamps, scroll positions, click target geometry, safe structural layout roles, error markers without sensitive error text, capture/drop status, and the applicable consent or capture-scope state. Replay access is limited to true site administrators and replay views/configuration changes may be audited.

Session Activity retention is intentionally short. The current system defaults to 30 days and administrator configuration is bounded to 7–90 days unless a separate legal or security obligation expressly requires a different retention rule. Session Activity is not used for Advertising targeting, member reputation, employment or eligibility decisions, or unrelated profiling.

ProfoundSyntax stages Session Activity collection behind consent and notice controls. Administrator QA capture is separately identified. For broader sampled visitor/member capture, ProfoundSyntax presents an explicit Session Activity diagnostics choice before capture begins. Choosing Allow diagnostics permits privacy-safe sampled capture subject to the protected-surface rules above; choosing No thanks prevents Session Activity replay capture for that browser choice. Declining or lacking replay consent does not prevent ordinary use of the service.

CAPTCHA and Automated Abuse Protection

ProfoundSyntax may use CAPTCHA, honeypots, rate limits, automated heuristics, and similar controls to distinguish legitimate activity from automated or abusive activity. Third-party CAPTCHA providers may process information under their own privacy terms.

How We Use Information

• Create, authenticate, secure, and recover accounts.
• Operate developer profiles and public handles.
• Publish and organize community discussions.
• Operate member-created Communities, Wikis, private Chat, Mod Mail, Feedback, and connected integrations.
• Process replies, votes, reputation, badges, saves, follows, and accepted answers.
• Deliver notifications and account communications.
• Provide search, feeds, Topics, discovery, and related discussions.
• Conduct identity review or optional identity verification.
• Prevent impersonation, spam, fraud, abuse, and security threats.
• Investigate reports and enforce ProfoundSyntax Rules.
• Maintain, troubleshoot, measure, and improve the service.
• Comply with legal obligations and protect the rights and safety of ProfoundSyntax, its users, and others.

When Information May Be Shared

We may share or disclose information only as reasonably necessary to operate ProfoundSyntax, provide a feature you request, protect the service, comply with law, or work with service providers performing functions on our behalf. These recipients may include hosting or infrastructure providers, email-delivery providers, social sign-in providers, CAPTCHA or anti-abuse providers, security vendors, professional advisers, and authorities where disclosure is legally required.

Developer Projects and Portfolio Data

ProfoundSyntax Projects may contain a title, summary, description, development status, visibility setting, technologies, demo/documentation/package links, repository links, owner-controlled Project cover/hero artwork, Project gallery images, related ProfoundSyntax Communities/Discussions/Wiki/Blog references, collaborator invitation state, accepted collaborator attribution, and optional cached metadata copied from public GitHub repositories that the Project owner explicitly authorizes through Apps & Integrations.

Project visibility can be Public, Members only, Private, or Draft. Public Project information may be visible to anyone. Members-only Projects are limited to signed-in eligible members. Private and Draft Projects are limited to the owner, accepted collaborators who need access to work on that Project, and authorized site/community management. Project collaborator invitations are private until accepted. Accepted collaborators are publicly credited on Project/portfolio surfaces and may receive bounded Project edit access. ProfoundSyntax does not implicitly publish private GitHub repository metadata through Projects; Project GitHub synchronization accepts only authorized public GitHub repositories selected by the Project owner.

When Hosted Demo is used, ProfoundSyntax can temporarily quarantine an uploaded ZIP, validate its static files, store accepted source in private Project storage, and create immutable Draft, Active, or retained build records. Project runtime URLs do not expose the private storage path. Quarantined packages remain private and can be reviewed or deleted only by authorized site administrators; administrators can also configure automatic quarantine retention cleanup. Hosted source and build records may include opaque source/build identifiers, runtime-profile identifiers/versions, entry-file names, file counts, byte totals, validation timestamps, build state, and the membership tier recorded when a build was created.

Personal-data export can include Project runtime/build metadata and opaque source references without exposing private server filesystem paths. A personal-data erasure request removes owned Project quarantined ZIPs, validated hosted source, build history, runtime pointers, and viewer source-sharing settings. The public or member-visible Project page may remain as a community contribution under the account’s anonymized public identity, consistent with the treatment of other retained public contributions. Permanently deleting a Project also purges its private validated-source and quarantine directories. Limited de-identified audit or moderation records may remain where reasonably necessary for security, abuse prevention, legal compliance, or service integrity.

Package Ecosystem Metadata

If a Project includes a recognized public package URL for npm, PyPI, Packagist, or NuGet, ProfoundSyntax may request and cache public registry metadata such as the package name, current version, description, license, author information when supplied, platform/runtime requirement information, public download counts when supplied, verification status when supplied, repository/homepage links, and a version-specific installation command.

Package ecosystem lookups do not require a member registry account, access token, API key, password, or publishing permission. ProfoundSyntax constructs requests only to supported public registry API endpoints and uses the cached data to enrich the Project for viewers who are already permitted to see that Project. The registry remains the authoritative source and its own terms, availability, and metadata accuracy apply.

Connected GitHub Member Integration

If you connect GitHub through Account → Apps & Integrations, ProfoundSyntax may store the encrypted authorization credential required for the connection, the connected GitHub account identifier, GitHub App installation identifiers, cached metadata for repositories the installation authorizes, and your selected public profile-repository choices. Repository authorization by itself does not publish a repository on ProfoundSyntax.

When GitHub lifecycle Bell notifications are available, ProfoundSyntax may process signed GitHub event data indicating that an Issue closed, a Pull Request merged, or a Release was published. ProfoundSyntax creates these routine Bells only for a repository already used by your ProfoundSyntax profile showcase or one of your Projects, stores the applicable notification record and safe GitHub destination link, and does not require GitHub write access for these notifications. Your per-GitHub routine Bell preference can suppress these routine lifecycle notifications. Disconnecting or erasing the integration removes locally stored connection credentials and integration selections according to the current privacy workflow; ordinary notification retention follows the ProfoundSyntax notification controls and retention rules.

Public GitHub Smart Cards

When a signed-in user deliberately chooses the GitHub Smart Card tool for a supported public github.com Repository, Issue, Pull Request, or Release URL, ProfoundSyntax may request and cache public metadata from GitHub such as the resource title, short description, public state, author handle, labels, counts, language, release tag, and the public GitHub URL. The preview is shown before the Smart Card is inserted. The same public-card adapter can be used by authorized Blog editorial staff from the Blog post editor.

Public GitHub Smart Cards do not require a GitHub account connection and do not use a member’s stored GitHub OAuth token. ProfoundSyntax constructs requests only for the supported public GitHub resource deliberately identified through a Smart Card control, does not automatically convert ordinary GitHub links into Smart Cards, and does not intentionally fetch or publish private GitHub resources through this feature. GitHub remains the authoritative source and its own terms, availability, rate limits, and privacy practices apply.

Stack Exchange Integration

If you connect Stack Exchange through Account → Apps & Integrations, ProfoundSyntax stores the encrypted OAuth access token needed for the connection plus cached public metadata for associated Stack Exchange network site identities. Cached identity metadata can include the site name and URL, network/site user identifiers, reputation, question and answer counts, badge totals, and the public profile link. You choose which associated site identities, if any, are displayed publicly on your ProfoundSyntax profile.

For site identities you have already selected for public display, you may also ask ProfoundSyntax to refresh recent public question and answer metadata and explicitly choose a limited set of those contributions for your public profile. Cached Q&A metadata can include the external post type, title, public URL, Stack Exchange site, public post identifiers, score, tags, creation/activity dates, answer-count or answered state for questions, and accepted-answer state for answers. ProfoundSyntax does not copy the full external question or answer body, comments, inbox content, or private Stack Exchange data for this showcase.

Stack Exchange remains the authoritative source of all displayed external identity and Q&A metadata. External links open the applicable Stack Exchange network site. Removing a saved public site identity also removes locally cached Q&A selections tied to that identity, and disconnecting or erasing the integration removes the local connection credentials, cached Stack Exchange metadata, and public selections according to the current privacy workflow.

External Runnable Code Sandboxes

Supported code blocks may offer an Open In action for administrator-approved external sandboxes such as CodePen, JSFiddle, or StackBlitz. ProfoundSyntax does not automatically send code to these providers and does not execute the code on ProfoundSyntax servers. A viewer may transfer one supported code block, or may deliberately choose an available combined example that groups an unambiguous set of compatible HTML, CSS, and script blocks from the same content item. The selected code is transferred directly to the provider only after the viewer explicitly chooses that provider. The selected third party then processes the transferred code under its own privacy policy, terms, account settings, and technical controls.

Public Information

Information you intentionally publish may become publicly accessible. Public information may include your public handle or permitted display name, profile image, biography, public profile fields, Threads, replies, code examples, reputation indicators, badges, contribution history, and other public activity.

Public information may be indexed, cached, quoted, linked to, archived, or copied by search engines, other users, or third parties outside ProfoundSyntax’s control.

Data Retention

We retain information for as long as reasonably necessary to provide the service, maintain account and discussion integrity, comply with law, resolve disputes, prevent abuse, protect security, and enforce our agreements. Temporary verification codes may expire quickly, identity-proof files are intended to be deleted after a verification decision, while moderation, security, copyright/DMCA, or other legal records may need to be retained longer.

Public Threads and replies may be retained after account deletion or privacy erasure where automatically deleting them would damage discussion structure, accepted-answer history, or other members’ contributions. In those cases, ProfoundSyntax may anonymize or neutralize the associated public identity instead.

For Final Permanently Banned accounts, ProfoundSyntax may schedule deletion of the account and eligible private or account-linked data after an administrator-configured delay. This includes profile data, private or non-discussion media, drafts, settings, relationships, notifications, identity-verification proof, Community membership and sanction state, and other live account relationships. Public Community Threads, replies, and media attached to those discussions are retained to preserve discussion integrity, detached from the deleted account, and may continue to display the member’s previously public-facing name or handle with a “No Longer with us” status. If the deleted account owned a Community, that Community may be suspended until an administrator assigns an eligible replacement owner. An administrator may temporarily place a purge hold when reasonably necessary for security, abuse investigation, legal obligations, or dispute handling. After purge, ProfoundSyntax may retain limited keyed identity fingerprints and de-identified enforcement or audit evidence reasonably necessary to document the final action and prevent straightforward re-registration.

Personal-Data Export and Erasure

ProfoundSyntax supports personal-data export and erasure processes for applicable member data. An export may include profile information, preferences, Community Threads, replies, handle history, votes, reputation records, saves, follows, notifications, identity-review status, reports submitted by you, and other applicable account data.

Highly sensitive authentication secrets are not included in personal-data exports. An erasure request may remove or anonymize applicable profile information, private saves and follows, votes, reputation records, notification history, recovery-email state, handle history, and other ProfoundSyntax-owned personal data.

Public discussion content may remain in anonymized or neutralized form where retention is necessary to preserve discussion integrity. Moderation, abuse-prevention, legal, and security records may also be retained where reasonably necessary.

Your Privacy Choices and Rights

Depending on where you live, you may have rights to request access, obtain a copy, correct inaccurate information, request deletion, object to certain processing, restrict certain processing, or exercise other privacy rights available under applicable law. We may need to verify your identity before completing a privacy request.

Security

ProfoundSyntax uses administrative, technical, and organizational safeguards intended to protect account and community information. No online service can guarantee absolute security. You are responsible for protecting your credentials, recovery information, devices, and any credentials or secrets you choose to publish.

International Use

ProfoundSyntax is operated with a United States compliance baseline but may be accessed globally. Information may be processed in jurisdictions where ProfoundSyntax or its service providers operate, subject to applicable safeguards and legal requirements. Site-wide safety rules apply regardless of where a member is located. Users are responsible for complying with laws that apply to their own conduct and jurisdiction, and ProfoundSyntax may remove, restrict, preserve, or report conduct anywhere when reasonably necessary to enforce the Rules, protect people, or comply with a lawful obligation. Nothing in this Policy is intended to state that mandatory non-U.S. law can never apply.

Children

ProfoundSyntax is not intended for children under 13 years of age, or a higher minimum age where required by applicable law. If you believe a child has provided personal information in violation of applicable law, contact ProfoundSyntax so the matter can be reviewed.

Changes to This Privacy Policy

We may update this Privacy Policy as ProfoundSyntax evolves, legal requirements change, or new features are introduced. When changes are material, we may provide notice through the website, account interface, notification system, email, or another appropriate method.

Contact and Privacy Requests

If you have questions about this Privacy Policy or want to submit a privacy-related request, use the official ProfoundSyntax Help or contact channel. For account-specific requests, we may require you to verify ownership of the affected account.