1. Scope
This policy applies to:
- visitors to the SSDC website
- people who contact SSDC
- prospects who submit intake information
- clients and counterparties in active or completed scopes
- information SSDC creates during delivery, including notes, working materials, and final artifacts
SSDC is currently operated by one person. Access to records is therefore limited to a single operator unless and until this policy is updated.
2. Governing rules
SSDC handles information under five operating rules:
Minimum necessary. SSDC asks for the smallest amount of information needed to classify fit, issue an artifact, perform a bounded scope, or maintain continuity.
No hidden dependency. Information handling should not create a new secret-bearing dependence on SSDC.
No secret custody. The wrong information should not be sent to SSDC in the first place.
Short-lived working material. Temporary evidence, screenshots, raw notes, and verification scraps are not meant to become a growing archive.
Human judgment remains in charge. If tools assist analysis, final judgment remains with SSDC, not an automated system.
3. What SSDC collects
3.1 Information you choose to provide
Depending on the stage of contact or engagement, SSDC may collect:
- name, alias, or pseudonym
- Nostr public key, handle, or other Nostr contact detail
- organization or formation name
- country, region, or time zone where needed for coordination
- the reason for your inquiry
- scope-relevant intake answers
- attachments or evidence you choose to send
- project-related communications
- billing and invoicing details when a paid scope begins
You can and should contact SSDC under a pseudonym at the early stage so long as the information provided is sufficient to classify fit and safety.
3.2 Information collected automatically from the website
The website or its host may automatically collect basic technical data such as:
- IP address
- browser type
- operating system or device class
- referring page
- requested pages or files
- timestamps
- server, security, and abuse-prevention logs
SSDC does not use advertising trackers, data-broker style profiling, or cross-context behavioral advertising.
3.3 Information created during delivery
During a scope, SSDC may create:
- internal notes
- control and dependency maps
- draft findings
- redacted working excerpts
- final written artifacts
- closeout notes
- minimal records showing what was delivered and when
4. Information you should not send
Do not send any of the following unless SSDC explicitly instructs you to use a narrowly defined and safer method:
- seed phrases
- private keys
- password-manager exports
- passwords
- TOTP seeds
- recovery codes
- wallet backups containing spend authority
- undisclosed admin credentials
- long-lived SSH keys
- long-lived API keys
- full secret-bearing configuration files
- unrelated legal, medical, tax, or identity-document archives
If information of this kind is sent anyway, SSDC may isolate it briefly for secure removal, delete it, decline to process it, and, where appropriate, instruct you to revoke, rotate, or replace the affected secret or credential. SSDC does not want permanent possession of secret-bearing material, and the service model is not built on it.
5. What SSDC uses information for
SSDC uses information only for limited purposes tied to the actual relationship, including:
- responding to inquiries
- classifying fit and safety
- delivering intake and pre-engagement review
- performing Triage, Blueprint, or later bounded scopes
- coordinating scheduling and communication
- issuing invoices and maintaining accounting records
- maintaining basic site and communications security
- preserving continuity of active or recently completed work
- complying with bookkeeping, anti-fraud, or dispute-handling obligations
SSDC does not sell personal information. SSDC does not share personal information for cross-context behavioral advertising.
6. AI-assisted processing
SSDC currently uses only a small set of third-party AI tools for limited internal assistance:
These tools are used only on a minimized, abstracted, or redacted basis. Before information is submitted to a third-party AI tool, SSDC strips out names, direct identifiers, exact addresses, account numbers, credentials, and other details reasonably likely to identify a person.
As a rule, SSDC does not intentionally submit to these tools:
- names
- email addresses
- phone numbers
- exact physical addresses
- government identifiers
- financial account credentials
- seed phrases
- private keys
- passwords
- raw private message archives
- other secret-bearing or directly person-linked material
For the most sensitive of these limited de-identified workflows, Maple AI is preferred.
These tools are used to assist internal reasoning, drafting, organization, or pattern review. They do not make final decisions. Final engagement, scope, and judgment decisions are made by SSDC.
Because these are third-party systems, any data sent to them is still processed on infrastructure SSDC does not own. SSDC reduces that risk by sending only minimized, non-secret, non-directly identifying fragments.
7. Communications and channel discipline
SSDC keeps public first contact to one channel: Nostr.
Use Nostr for early classification only: fit, unit form, pressure lane, current choke point, and likely next step. Do not use first contact to transmit secrets, credentials, private archives, or unnecessary evidence.
Other channels, if ever needed for a paid scope or administrative requirement, are introduced only after fit, trust, and scope are established.
8. Cookies, analytics, and website measurement
If the website ever uses cookies or similar technologies, they are limited to functions such as:
- security
- abuse prevention
- load balancing
- session continuity
- basic privacy-respecting performance measurement
SSDC does not use advertising trackers, behavioral profiling, or sale/share tooling for targeted advertising.
If privacy-respecting analytics are later added, this policy will be updated to reflect the actual tool and collection behavior.
9. When SSDC shares information
SSDC shares information only in narrow cases.
9.1 Service providers
SSDC may use third-party providers for functions such as:
- hosting
- domain and DNS services
- email delivery
- secure communications
- invoicing and payment processing
- bookkeeping
- limited AI-assisted internal analysis
Those providers receive only what is reasonably necessary for the function they perform.
9.2 Specialist or referral handoff
If a narrow specialist or outside provider is the right next step, SSDC does not automatically transfer your information. Any handoff is deliberate and limited to what the handoff requires.
9.3 Fraud, dispute resolution, or security necessity
SSDC may disclose information where reasonably necessary to detect or address fraud, resolve disputes, or protect the security of SSDC, clients, or others.
9.4 Business transition
If SSDC is reorganized, sold, or transferred, relevant business records may transfer as part of that change, subject to materially similar privacy handling.
10. Retention and deletion
SSDC does not use one indefinite retention bucket. Different categories of information have different clocks.
10.1 Website and security logs
Basic server, security, and abuse-prevention logs may be kept for as long as reasonably necessary to secure the site, diagnose incidents, and maintain service integrity.
10.2 General inquiries with no engagement
If you contact SSDC but no engagement begins, basic inquiry records are ordinarily kept for up to 90 days after the last meaningful contact, then deleted unless a shorter or longer period is justified by safety, anti-abuse, or continuity needs.
10.3 Intake materials and declined leads
If you submit intake information and SSDC declines the work or no scope proceeds, those materials are ordinarily kept for up to 180 days after the decision or last meaningful contact, then deleted unless a longer retention period is required for fraud prevention, dispute handling, or legal reasons.
10.4 Active project records
For an active scope, SSDC may retain:
- the final artifact
- essential scope communications
- the minimum underlying notes needed to support the artifact
- invoicing and payment records
- closeout records
10.5 Working materials
Working screenshots, temporary logs, transient verification materials, redaction drafts, and raw notes are ordinarily deleted within 14 days after artifact issuance or scope closeout unless:
- the scope is still active
- a separate corrective scope requires short-term preservation
- you specifically request temporary preservation for continuity
- law or dispute handling requires retention
10.6 Final deliverables and core continuity records
Final deliverables and core scope records may be retained for up to 24 months after closeout so SSDC can preserve continuity, answer follow-up questions, document what was delivered, and avoid forcing clients to resubmit the same context. After that period, they may be deleted unless law, accounting, dispute, or an ongoing relationship requires longer retention.
10.7 Billing and accounting
Invoices, payment confirmations, and bookkeeping records may be retained for as long as reasonably required for accounting, tax, audit, fraud prevention, and legal compliance.
10.8 Temporary access and credentials
If a later bounded scope ever requires temporary access, that access must be explicit, time-limited, and removed or rotated at closeout. SSDC does not retain long-lived secret-bearing access as an ordinary practice. A non-secret audit note that access existed, what it was for, and when it ended may be retained as part of the project record.
10.9 Backups
Deleted records may remain in encrypted backups for a limited period until those backups rotate out under the ordinary backup cycle. Backups are not maintained to resurrect deleted working material except where disaster recovery genuinely requires restoration.
11. Security and access
No system is perfect, but SSDC uses a minimization-first security model.
That includes:
- one-operator access
- collecting less at intake
- using lower-exposure channels where possible
- stripping identifiers before third-party AI use
- avoiding secret custody
- removing temporary access at closeout
- deleting working materials on schedule
- limiting records to what the scope actually needs
The strongest security control is often refusal to collect the dangerous thing in the first place.
12. Sensitive information and third-party information
Do not send sensitive information or third-party information unless it is genuinely required for the decision at hand.
That includes information about:
- spouses or partners
- children or dependents
- employees, cofounders, or contractors
- health status
- precise location
- legal disputes
- intimate or highly personal communications
If a scope requires reference to another person, provide only the minimum detail necessary. Abstract descriptions are preferred over over-identifying disclosure.
SSDC is not a health-data service. Do not send medical records, diagnostic histories, treatment files, or other detailed health records unless SSDC explicitly says that a tightly limited exception is necessary for a specific scope.
13. Children
SSDC is not directed to children. SSDC does not knowingly collect personal information directly from children except where a parent, guardian, or responsible adult provides a strictly necessary minimum as part of a legitimate household or continuity issue. If child-related information is ever relevant, it should be minimized aggressively.
14. Your rights and requests
Depending on where you live and which laws apply, you may have rights to request access to personal information, correction of inaccurate information, deletion, or limits on certain uses of sensitive information. If SSDC receives such a request, SSDC may need enough information to verify that the requester is the right person, and any verification information will be used only for that purpose.
To make a privacy request, use the contact method listed at the end of this policy and include enough detail to identify the relevant records. SSDC may deny or narrow a request where verification is not possible, where the request is manifestly excessive, or where retention is required for accounting, legal, fraud-prevention, dispute, or continuity reasons.
If SSDC does not sell personal information or share it for cross-context behavioral advertising, SSDC will say so plainly rather than offering a fake opt-out mechanism.
15. International visitors
If you access SSDC from outside the country where SSDC operates, your information may be processed in other jurisdictions depending on the channels and service providers used. By using the site or contacting SSDC, you understand that your information may be transferred accordingly.
16. Changes to this policy
This policy may change as SSDC’s site, tools, service model, or legal obligations change. If the changes are material, the updated version will be posted with a new effective date.
17. Contact
For privacy requests or questions, contact SSDC through Nostr:
- Sov Stack Dev. Co.
- npub1ad0h4776rf2eh2swdz6dxw5upxk963g52g3yyh83e99z8dvu6g4q09c7zj
Channel note: do not send seed phrases, private keys, passwords, recovery codes, or other secret-bearing material.
18. Short version
- SSDC collects less by design.
- SSDC is currently operated by one person.
- SSDC does not want your secrets.
- SSDC uses only limited third-party AI assistance, and only on stripped, non-directly identifying inputs.
- SSDC does not sell personal information or share it for behavioral advertising.
- Working materials are deleted quickly.
- Final artifacts and core records are retained only for bounded continuity and then removed on schedule.
- If a law gives you privacy rights, SSDC will honor them to the extent required and operationally possible.