01 / SECTION
PSC-owned materials
Except where otherwise stated, PSC reserves its rights in original material that it owns.
Depending on the product or page, PSC-owned material may include:
- original software source code
- application architecture
- original user-interface designs
- original visual systems and graphics
- product workflows
- original documentation
- technical diagrams
- training materials
- written website content
- original product specifications
- test infrastructure
- original prompts and structured AI workflows
- original product names, logos, and brand materials where applicable
The presence of material on the public website does not place that material in the public domain.
02 / SECTION
Public website content
Public access to the PSC website is intended to support legitimate informational, evaluation, and business-review purposes.
You may:
- browse public pages
- link to public pages
- share public URLs
- quote reasonable portions for legitimate commentary, evaluation, or discussion
- make reasonable internal copies needed to evaluate a potential product, service, license, or transaction
These permissions do not grant ownership of PSC materials.
Unless applicable law or a separate license provides otherwise, public access does not authorize:
- wholesale republication of proprietary PSC content
- resale of PSC materials
- removal of ownership or attribution notices
- representation of PSC material as your own
- unauthorized commercialization of PSC-created materials
- copying of nonpublic software source
- redistribution of controlled-review materials
Nothing in this notice is intended to restrict fair use or other rights provided by applicable law.
03 / SECTION
Portfolio software
Products displayed in the PSC portfolio may contain multiple categories of rights.
A particular application may include:
- software created by PSC
- original PSC product and workflow design
- PSC documentation and tests
- open-source software
- third-party packages
- external APIs
- cloud services
- AI model providers
- publicly available information
- government or court materials
- external datasets
- third-party publications
- third-party trademarks or product references
For that reason, the appearance of a product in the PSC portfolio should not be interpreted as a claim that PSC owns every component, technology, dataset, document, or mark associated with that product.
PSC claims ownership only over material it owns and claims transferable rights only where those rights have been verified for the relevant transaction.
04 / SECTION
Open-source software
PSC software may incorporate open-source libraries, frameworks, packages, or other components.
Those components remain subject to their respective licenses.
Nothing in this notice changes, overrides, or restricts rights granted under an applicable open-source license.
Where an open-source license provides rights that differ from PSC's general website or software restrictions, the open-source license controls the covered component.
Product-specific dependency and license information may be reviewed when relevant to a technical, licensing, or acquisition evaluation.
05 / SECTION
Third-party software and services
PSC products may depend on or interact with third-party technologies such as:
- cloud infrastructure
- model providers
- communications services
- APIs
- databases
- payment or carrier services
- development libraries
- hosted platforms
- external data sources
Those services and technologies remain subject to their providers' own terms, licenses, privacy policies, technical requirements, and availability.
Use of a third-party technology within a PSC product does not mean PSC owns that technology or can transfer the provider relationship.
Provider accounts, subscriptions, API access, credentials, contracts, or other third-party rights are included in a software transaction only where the applicable provider permits transfer and the definitive agreement expressly includes them.
06 / SECTION
Third-party content and data
Some products may display, organize, transform, link to, or otherwise use information originating outside PSC.
Examples may include:
- government information
- court forms
- statutes or regulations
- public records
- publications
- educational resources
- reference materials
- public datasets
- information obtained through external APIs
Ownership and use rights for that material remain subject to the rights and restrictions applicable to the original source.
PSC's software implementation, organization, transformation, or presentation of third-party information does not convert the underlying third-party material into PSC-owned content.
07 / SECTION
Trademarks and brand names
Prosocial Coding names, logos, product names, visual identities, and other brand identifiers may function as trademarks, service marks, trade names, or other source identifiers.
Unless PSC expressly states otherwise, this website does not represent that a particular PSC mark is federally registered.
Third-party trademarks, logos, company names, product names, and service names remain the property of their respective owners.
References to third parties are made for identification, interoperability, explanation, compatibility, attribution, or other legitimate informational purposes.
Such references do not by themselves imply:
- sponsorship
- endorsement
- partnership
- certification
- ownership
- affiliation
08 / SECTION
Software acquisition and ownership transfer
Some PSC software assets may be available for acquisition.
An acquisition discussion may contemplate transfer of agreed seller-owned assets such as:
- PSC-created source code
- application architecture
- original workflows
- interface systems
- tests
- documentation
- configuration materials
- maintainership information
- transition materials
- other seller-created intellectual property identified during review
The exact package differs by product.
No website description should be interpreted as a warranty that every component associated with a product is owned by PSC or transferable.
09 / SECTION
Transfer boundary
A software transaction may include both a transferable PSC-created foundation and components that require separate treatment.
Items requiring separate rights review can include:
- open-source software
- vendor libraries
- external APIs
- third-party datasets
- publications
- trademarks
- domain names
- hosted services
- cloud accounts
- AI-provider agreements
- telecommunications services
- payment accounts
- external model access
- credentials and secrets
Credentials, private keys, access tokens, passwords, and similar security secrets are not intellectual-property assets and should not be transferred as part of a source-code package.
A receiving organization should establish its own authorized accounts and credentials where appropriate.
10 / SECTION
Acquisition does not automatically transfer third-party rights
A transfer of PSC-owned software does not automatically transfer rights PSC does not own.
Where a product depends on third-party rights, a buyer or licensee may need to:
- accept an open-source license
- obtain its own commercial license
- create its own provider account
- obtain API access
- enter into its own provider agreement
- obtain permission to use external data
- replace a nontransferable service
- conduct additional rights review
These matters should be identified during product-specific diligence.
11 / SECTION
Licensing
Where PSC offers a software license rather than an ownership transfer, the rights granted are defined by the applicable written license agreement.
A public product page does not itself create a software license.
Licensing terms may address matters such as:
- permitted users
- permitted organizations
- permitted use cases
- modification rights
- deployment rights
- sublicensing
- redistribution
- support
- updates
- confidentiality
- duration
- termination
Only the applicable written agreement establishes those rights.
12 / SECTION
Controlled-review materials
PSC may provide additional nonpublic materials during a qualified technical, acquisition, licensing, or commercial review.
Controlled materials may include:
- source code
- internal technical documentation
- security information
- architecture details
- dependency records
- intellectual-property records
- product limitations
- transition documentation
- private diligence materials
Providing access to those materials does not transfer ownership.
Controlled materials may be subject to separate confidentiality, evaluation, licensing, or transaction terms.
Unless authorized by an applicable agreement, controlled materials may not be:
- publicly distributed
- republished
- disclosed outside the approved review group
- used to create unauthorized commercial derivatives
- used for purposes unrelated to the approved review
- represented as public PSC documentation
13 / SECTION
No rights created by review
No ownership, license, exclusivity, option, reservation, or other intellectual-property right is created merely because a person or organization:
- visits the PSC website
- views a product
- submits a Contact inquiry
- receives a response
- attends a demonstration
- participates in a technical discussion
- receives controlled-review access
- evaluates source code
- receives transaction materials
Rights arise only through applicable law or an appropriate written agreement.
14 / SECTION
Product-specific ownership verification
Software products can accumulate different rights and dependencies over time.
Accordingly, intellectual-property review should be product-specific.
Where relevant to a transaction, review may address:
- source-code authorship
- dependency licenses
- external services
- datasets
- publications
- trademarks
- domains
- contractor or contributor rights
- third-party agreements
- documentation
- transfer restrictions
Public portfolio information is not intended to substitute for that review.
15 / SECTION
No blanket clean-title representation
This public notice is not a legal opinion regarding title to a particular software asset.
PSC does not use this website to make a blanket representation that:
- every component of every product is solely owned by PSC
- every dependency can be transferred
- every third-party service can be assigned
- every trademark is registered
- every dataset is owned by PSC
- every external license permits unrestricted commercial transfer
- a product is free from every potential third-party claim
Where a transaction requires ownership, provenance, licensing, or transfer representations, those representations should be established through product-specific diligence and the definitive written agreement.
16 / SECTION
Definitive agreements control
Acquisition, licensing, services, confidentiality, and other commercial relationships may be governed by separate written agreements.
Those agreements may define:
- intellectual-property ownership
- transferred assets
- excluded assets
- license rights
- third-party dependencies
- representations and warranties
- transition obligations
- confidentiality
- support
- indemnification
- post-transfer responsibilities
Where a signed agreement conflicts with this general notice on a matter covered by that agreement, the signed agreement controls that matter.
17 / SECTION
Feedback and submissions
Providing nonconfidential feedback about PSC software does not transfer ownership of unrelated materials you own.
As described in the Terms of Use, PSC may consider and use voluntarily submitted nonconfidential product feedback without creating an obligation to compensate the sender, unless a separate written agreement provides otherwise.
Do not submit:
- trade secrets
- confidential product concepts
- proprietary third-party materials
- confidential source code
- protected client information
through the public Contact form.
18 / SECTION
Copyright and rights concerns
If you believe material on the PSC website infringes a copyright, trademark, or other intellectual-property right that you own or are authorized to represent, contact PSC with enough information to evaluate the concern.
Please include:
- your name and contact information
- identification of the work or right involved
- identification of the PSC material at issue
- the relevant URL, if available
- a description of the concern
- information supporting your authority to make the request
PSC may request additional information before acting.
This contact process is not represented as a formal DMCA designated-agent procedure unless PSC separately establishes and publishes one.
19 / SECTION
Changes to this notice
PSC may update this notice as:
- portfolio products change
- external dependencies change
- transaction practices change
- new licensing models are introduced
- new third-party services are used
- relevant legal or operational requirements change
The revision date at the top of the page identifies the current version.
Changes to this public notice do not retroactively modify rights established in a signed agreement.
20 / SECTION
Contact
Questions about intellectual property, third-party rights, or this notice may be sent to:
Prosocial Coding LLC Austin, Texas, United States hello@prosocialcoding.com
Do not send passwords, API keys, confidential source code, survivor information, client records, protected health information, or other sensitive material through an initial inquiry.
© 2026 Prosocial Coding LLC. Rights in third-party and open-source materials remain with their respective owners and licensors.
