Inactivity Policy

1. Purpose and scope

This policy explains how prolonged inactivity may affect an account, workspace, reserved identifier, hosted project, or stored data on a service operated by SqueHub.

It does not apply to source code you downloaded, an application you operate yourself, or an account held with GitHub, Discord, LinkedIn, X, a hosting provider, or another independent service. Those operators control their own inactivity and retention practices.

The current public SqueHub website does not offer ordinary visitor accounts. Its editorial accounts are restricted operational accounts. This policy becomes directly relevant when a SqueHub-operated service expressly provides an account, managed workspace, hosted Package or Kit record, reserved name, or similar ongoing resource.

2. What inactivity means

Inactivity is an extended period without a meaningful signal that an account or resource remains in use. Depending on the service, signals can include:

• successful sign-in or authenticated API activity;
• a publication, release, update, support interaction, or administrative action;
• a valid paid or organizational relationship;
• response to an ownership or inactivity notice;
• use of a managed resource in a way visible to the service; or
• another service-specific indicator described when the resource is created.

Automated requests, abusive traffic, failed logins, passive receipt of email, or activity unrelated to the resource may not count. SqueHub may require a stronger ownership signal before preserving a security-sensitive namespace or account.

3. Inactivity periods

There is no single inactivity period for every present or future SqueHub service. Before inactivity alone results in deletion or release of a resource, the applicable interface, service terms, order form, or direct notice should identify the relevant period.

Different periods may apply to free and paid resources, personal and organizational accounts, temporary previews, unverified registrations, abandoned uploads, security records, public packages, or contractual services. Legal retention, security risk, storage cost, public dependency, and recovery requirements can also affect timing.

SqueHub may act before an ordinary inactivity period where a resource is compromised, fraudulent, unlawful, malicious, materially unpaid, technically harmful, used for impersonation or dependency confusion, or subject to a valid legal or security requirement. Such action is based on the separate risk, not inactivity alone.

4. Notice before inactivity action

When practical and not prohibited by security or law, SqueHub will provide advance notice through the latest verified email address, the affected service, or another established contact channel. A notice may explain:

• the account or resource at issue;
• the relevant deadline;
• the action needed to demonstrate continued use;
• available export or recovery options;
• the possible outcome if no action is taken; and
• how to request assistance.

You are responsible for maintaining current contact information, monitoring official notices, and keeping independent backups. Failure to receive a notice because contact information is outdated, filtered, inaccessible, or controlled by a former team member does not create an indefinite retention obligation.

5. Possible actions

Depending on the service and risk, SqueHub may:

1. send one or more reminders;
2. mark the account or resource inactive;
3. disable sign-in, publishing, automation, or API access;
4. archive data or move it to lower-cost storage;
5. make a public listing unavailable;
6. cancel an unused reservation or preview environment;
7. release an identifier after security review;
8. delete stored data under the applicable retention process; or
9. preserve limited records required for law, security, attribution, or project integrity.

Suspension, archival, unlisting, release, and deletion are different actions. A suspended account may be recoverable. A deleted resource may not be.

6. Public identifiers and supply-chain safety

Names used for Packages, Kits, repositories, organizations, accounts, domains, or namespaces can affect users who depend on them. SqueHub will consider more than inactivity before releasing an identifier, including:

• active downstream dependencies and download history;
• the risk of impersonation, phishing, or dependency confusion;
• trademark and project identity concerns;
• security advisories and update channels;
• historical significance and public attribution;
• ownership disputes or organization succession; and
• whether redirection, reservation, or archival is safer than reuse.

SqueHub may permanently reserve official, security-sensitive, high-risk, or historically important identifiers. An inactive identifier is not automatically available to another person, and a former holder has no guarantee that a released identifier can be restored.

7. Data retained after closure or deletion

Account closure does not necessarily erase every related record immediately. SqueHub may retain bounded information needed for:

• security, fraud, abuse, and incident investigation;
• financial, tax, contractual, or legal obligations;
• dispute handling and legal claims;
• copyright, license, contribution, and authorship attribution;
• public release and version-control integrity;
• preventing re-registration abuse or impersonation; and
• backup rotation and disaster recovery.

Retained information remains subject to purpose and access restrictions. Backups may persist until ordinary rotation completes and generally are not restored solely to retrieve one deleted account.

Public release metadata, commits, authorship, advisories, dependency records, and documentation can remain available even after an associated account becomes inactive because removal could damage attribution, licensing, security, or project history. Personal-information rights remain available subject to lawful exceptions described in the Privacy Policy.

8. Restoring access

If an account or resource has been suspended or archived, email hello@squehub.com with the subject Inactive account. Identify the service and public identifier, but do not send a password, token, or private key.

SqueHub may require evidence of control over a verified email address, organization, domain, repository, billing relationship, signing key, or another established identity signal. Additional review can be required where administrators have changed, ownership is disputed, or the resource is security sensitive.

Recovery is not guaranteed after deletion, release, expiration of a contractual recovery window, or loss of required evidence. Restored resources remain subject to current security requirements and may require credential rotation or updated contact information.

9. Organizations and team accounts

Organizations should maintain more than one current administrator where the service permits, use organization-controlled contact details, document ownership, and remove access promptly when roles change. SqueHub may contact another verified administrator before treating an organization as inactive.

An individual's departure does not automatically make an organization resource inactive. Conversely, activity by a former or unauthorized member does not establish current authority.

10. Authorized editorial accounts

Editorial accounts for the official website are operational and may be disabled when access is no longer required, a role changes, credentials are at risk, or the account remains unused beyond the operational need. Published attribution and audit records can remain after access is disabled.

Editorial users should not treat the site as personal storage. Media and drafts may be retained, archived, reassigned, or removed according to publication, legal, and project needs.

11. Your responsibilities

Keep exports and backups appropriate to the value of your work. Do not rely on a free or preview service as the only copy. Keep contact details and organization administrators current, protect credentials, respond to notices, and export information before a known closure date.

The open-source SqueHub framework includes portability tools, but an application backup must still account for project source, assets and uploads, live database records, configuration, dependencies, secrets, and restoration testing.

12. Changes and contact

SqueHub may update this policy as services develop. A service-specific agreement or notice can provide different periods or procedures and controls for that service.

Questions or recovery requests may be sent to hello@squehub.com with the subject Inactive account.