Privacy Policy

This policy applies to the Prosocial Coding website and other PSC-controlled public pages that link to it.

It does not automatically apply to:

• separately deployed portfolio applications
• customer or partner systems
• third-party websites or services
• software transferred, licensed, or operated by another organization
• controlled technical-review environments governed by separate terms

Individual portfolio applications may have different data practices. When an application has its own privacy notice, that notice governs that application.

The PSC website is intentionally designed to collect limited information.

Information you provide through Contact

If you submit a Contact inquiry, we may receive:

• your name
• your email address
• your organization, if provided
• the type of inquiry
• the application or service you are interested in, if selected
• the message you provide

The Contact form requires you to confirm that your inquiry does not contain sensitive or confidential personal information.

Request and security information

When you use the website, standard website infrastructure may process technical request information needed to deliver and protect the service.

This may include information such as:

• IP address
• request date and time
• requested page or resource
• browser or device information
• HTTP request information
• security and delivery diagnostics

PSC also uses request information to limit abusive or excessive Contact submissions.

Theme preference

If you select Light or Dark mode, the PSC website stores that preference in your browser's local storage under a PSC-specific theme setting.

That preference is used only to remember how you want the website displayed.

The current PSC website does not provide user accounts, subscription billing, customer dashboards, payment processing, public file uploads, or application-level analytics.

PSC website application code also does not currently use behavioral advertising or marketing tracking technologies.

Portfolio applications described on the site may have their own technical architecture and data practices. Those should not be inferred from the PSC website's practices.

We use information submitted or processed through the PSC website for limited business and operational purposes.

These purposes include:

Responding to inquiries

We use Contact information to understand your request, respond to questions, and communicate about software, services, training, licensing, acquisition, or other requested topics.

Routing requests

We may use the inquiry type and selected product or service to route a message appropriately and determine the relevant next step.

Evaluating potential work or transactions

If you contact us about a product, service engagement, license, acquisition, partnership, training request, or controlled review, we may use the information you provide to evaluate whether and how to continue the conversation.

A Contact submission does not create a business relationship, grant controlled access, or establish that a transaction or engagement will occur.

Protecting the website

We process limited technical information to:

• reduce spam and abuse
• enforce request limits
• investigate delivery failures
• maintain website reliability
• identify operational or security problems

Maintaining your display preference

We use the locally stored theme preference only to remember whether you selected Light or Dark mode.

The PSC website currently uses Resend as its email-delivery service for Contact submissions when the production environment is configured for delivery.

When you submit a Contact inquiry, information included in the inquiry may therefore be transmitted to and processed by Resend so the message can be delivered to PSC.

A successful website response means that the email provider accepted the inquiry for delivery. It does not guarantee:

• final inbox delivery
• that the message has been read
• that PSC will accept the requested work
• that a transaction will proceed
• that controlled-review access has been approved

The PSC website does not currently write Contact submissions to a separate PSC application database.

Email copies or related metadata may still be retained by PSC's mailbox provider, Resend, hosting providers, or other infrastructure providers according to their applicable systems, policies, and retention practices.

PSC limits Contact requests to help reduce spam and automated abuse.

The website may temporarily process:

• the request IP address
• the submitted email address

These values are used to create rate-limit identifiers.

Where durable rate limiting is configured, PSC uses Upstash Redis for this purpose. The application converts the relevant identifiers into hashed rate-limit keys before storing them in the rate-limit backend.

Hashing a rate-limit identifier is a security safeguard. It should not be understood as a guarantee of legal anonymity.

PSC may use an in-memory fallback when the durable rate-limit service is unavailable or not configured.

PSC application code currently uses browser local storage to remember your selected Light or Dark theme.

The current PSC application does not use that preference for:

• behavioral advertising
• cross-site tracking
• advertising profiles
• analytics profiling

PSC does not currently operate a marketing-cookie or advertising-cookie system through its application code.

Website hosting, security, network, or other infrastructure providers may separately use technical mechanisms necessary to operate their services. Their practices are governed by their own policies and service configuration.

If PSC later introduces analytics, advertising, authentication, embedded third-party tools, or other technology that materially changes these practices, this policy should be updated before or alongside that change.

PSC does not currently sell information submitted through the public Contact form or use it for targeted advertising.

Information may be disclosed in limited circumstances.

Service providers

We may provide information to companies that perform services necessary to operate the website or respond to inquiries.

Current or potential categories include:

• hosting and network infrastructure
• transactional email delivery
• abuse-prevention and rate-limiting infrastructure
• business email services

Current application source specifically integrates with Resend for email delivery and can use Upstash Redis for rate limiting when configured.

These providers process information under their own agreements, privacy terms, and technical controls.

Professional and transaction support

If an inquiry develops into a legitimate service, licensing, acquisition, or other business discussion, information may be shared with professional advisers or relevant transaction participants when reasonably necessary for that purpose.

This does not authorize unnecessary disclosure of sensitive third-party information.

Legal and safety reasons

We may disclose information when reasonably necessary to:

• comply with applicable law or valid legal process
• protect our legal rights
• investigate fraud, abuse, or security incidents
• protect the security or integrity of our services
• protect people where disclosure is legally permitted and reasonably necessary

Business changes

If all or part of Prosocial Coding or a relevant software asset is sold, transferred, reorganized, or otherwise changes ownership, legitimate business records associated with that activity may be transferred as part of the transaction, subject to applicable law and relevant agreements.

PSC does not currently apply one universal retention period to every type of information described in this policy.

Retention depends on the information and its purpose.

Contact correspondence

Contact messages and resulting email correspondence may be retained while the inquiry is active and for a reasonable period afterward for follow-up, business records, dispute handling, legal obligations, or a resulting commercial relationship.

Information that is no longer reasonably needed should be deleted or archived according to applicable operating and recordkeeping practices.

Service-provider records

Email, infrastructure, hosting, and other providers may retain records according to their own service configuration and policies.

PSC should not be understood as promising a provider-specific deletion period unless that period is expressly stated here.

Rate-limit information

Rate-limit information is used for temporary abuse-prevention windows rather than as a customer profile.

Where Upstash is used, the application assigns expiration behavior to the rate-limit keys used by the Contact workflow.

Theme preference

The theme preference remains in your browser until you change it, clear browser storage, or the browser otherwise removes it.

You may contact PSC to ask about personal information associated with an inquiry.

Depending on applicable law and the circumstances, you may be able to request:

• access to information associated with you
• correction of inaccurate information
• deletion of information that no longer needs to be retained
• a portable copy of certain information
• information about how your data has been used or disclosed
• review of a decision concerning a privacy request

PSC may need to verify your identity before fulfilling a request.

Some information may need to be retained where required or permitted for legal obligations, security, fraud prevention, disputes, transaction records, or other legitimate purposes.

Because PSC does not currently sell personal information or process it for targeted advertising through the public website, there is currently no separate sale or targeted-advertising opt-out process.

If you believe a privacy request was incorrectly denied or limited, you may reply to the decision and ask PSC to reconsider it.

The PSC website is intended for professionals, organizations, potential buyers, partners, and others evaluating software or professional services.

It is not directed to children under 13.

PSC does not knowingly seek personal information from children under 13 through the Contact form.

If we learn that personal information from a child under 13 has been submitted through the site, we will take appropriate steps to delete it when required.

A portfolio application intended for a different audience may require its own child-privacy assessment and privacy notice.

Prosocial Coding operates from the United States.

Information submitted through the website may be processed in the United States or in other locations where PSC's service providers operate.

Privacy and data-protection laws vary by jurisdiction. Where applicable law gives you additional rights, PSC will address valid requests as required by that law.

The PSC website may link to third-party websites, platforms, documentation, software providers, or other external resources.

PSC does not control the privacy practices of independent third parties.

Review their privacy policies before providing information to them.

This section does not eliminate PSC's responsibility to accurately describe service providers that process information on PSC's behalf.

PSC may update this Privacy Policy when the website, providers, information practices, legal requirements, or business processes materially change.

Examples of changes that should trigger review include introducing:

• user accounts
• authentication
• analytics
• advertising technology
• payment processing
• persistent customer databases
• public file uploads
• AI processing on the PSC website
• mailing-list subscriptions
• new Contact fields
• CRM integrations
• additional data processors
• automated diligence or transaction systems

The revision date at the top of this page will be updated when the policy changes.

If a change materially affects how previously collected personal information is used, PSC will take additional steps when required by applicable law.

For privacy questions, requests, or concerns:

Prosocial Coding LLC Austin, Texas, United States hello@prosocialcoding.com

Please do not include sensitive third-party records or confidential case information in an initial privacy request.