Keep the exit door maintained.

Socialize offers a managed product and a smaller self-hosted edition. The open edition gives developers a practical route to their own backend project and domain, without carrying the hosted service's accounts, marketing pages, or multi-user operations.

That promise creates ongoing work: dependency releases must be reviewed, setup paths need retesting, security guidance changes, and documentation needs to match the code. Sponsorship gives that work a budget even when it does not produce a paid-service feature.

Maintenance

Next.js, backend maintenance, and dependency updates

Security

Rule reviews, fixes, and coordinated disclosure work

Documentation

Setup checks, migration notes, and practical examples

Accessibility

Keyboard, contrast, semantics, and reduced-motion testing

• Reproduce and fix defects that affect the public template.
• Keep sign-in and database rules guidance aligned with the implementation.
• Test upgrade paths so owners can pull changes without rebuilding their profile from scratch.
• Maintain examples and deployment notes across supported platforms.

If sponsorship materially exceeds routine project needs, Socialize will publish a clearer funding plan before expanding how those funds are used.

Before sending code, open a focused issue for substantial changes so scope and direction can be agreed first. Never include user data, backend credentials, or unpublished vulnerability details in a public issue.

Recognition

GitHub can display your sponsorship publicly when you choose that setting. Any additional name or logo placement follows the benefit shown on the selected GitHub tier. Sponsors may ask to remain private or have a public acknowledgement removed.

Project access

Public releases remain available under the repository's license and every current hosted feature remains free. A sponsorship does not transfer copyright, unlock functionality, grant access to hosted user data, priority support, or create a service-level agreement.

Priorities

Security fixes are ordered by severity and user risk. Other maintenance is ordered by reproducibility, affected users, effort, and fit with the project. Sponsor feedback is welcome, but a contribution does not guarantee a feature or delivery date.

Conflicts

Socialize may decline or return support that creates a legal, safety, editorial, or independence conflict, subject to the payment platform's rules and technical ability to issue a refund.

Can I cancel a recurring sponsorship?

Yes. Manage or cancel it from your GitHub Sponsors settings. Cancelling never changes access to Socialize because there are no paid features or sponsor-only service tiers.

Will I receive an invoice or receipt?

GitHub provides payment records for GitHub Sponsors transactions. Organizations that want to discuss a voluntary contribution can email llewellynpaintsil34@gmail.combefore paying.

Is a sponsorship tax deductible?

Do not assume it is. Socialize does not represent contributions as charitable donations. Ask a qualified tax professional about your circumstances and jurisdiction.

Can my team sponsor a specific feature?

You can propose work by email, but feature funding requires a separate written scope. Ordinary sponsorship should not be treated as a purchase order or delivery commitment.