Effective date: 1 January 2026
This Privacy Policy explains what information StikiLinks collects, how it is used, how it is shared, and the choices you have.
1) What StikiLinks is
StikiLinks is a public, transparent bulletin-board style application. Activity is recorded in a public database and is visible to all users. StikiLinks does not support direct messages, push messaging, or private posting. Users pull information from the database; the app does not “send” content to other users.
2) Identity and pseudonymity
StikiLinks does not collect or maintain user identity. Users are represented within StikiLinks by a public key pseudonym. Public keys are generated, held, and controlled by third-party applications that function similarly to digital wallets. StikiLinks does not control your key material, and does not have access to your private key.StikiLinks does not provide a feature to exchange public keys or to link a public key to a real-world identity. If a user’s identity becomes associated with a public key, that association occurs outside of StikiLinks (“out of band”) and is the responsibility of the user(s) involved.
3) Information we collect
StikiLinks collects and processes only what is necessary to operate the service:
A. Public Key Pseudonym
Your public key pseudonym, used to attribute your activity to your pseudonymous identity.
B. User-Initiated Payload (Limited Scope)
A limited, structured payload initiated by you through the app.
StikiLinks does not accept free-text posts.
C. Timestamp
A timestamp associated with activity, used for ordering, auditing, and integrity of the public database.
D. Authorisation Signature
A cryptographic signature that proves the user-initiated payload was authorised by the private key controlling the public key pseudonym.
4) Information we do not collect
StikiLinks is designed to minimise data collection. We do not collect:
- Real name, email address, phone number, physical address, government identifiers
- Date of birth, age verification information, or identity documents
- Device identifiers (IDFA/GAID), IMEI, MAC address, advertising identifiers
- IP address logging for tracking purposes, precise location, contacts, address book
- Browsing history, keystroke data, clipboard contents, photos, microphone recordings
- Usage analytics, behavioural profiling, ad targeting data, cross-app tracking data
- Third-party analytics or crash-reporting SDK data (we do not integrate these)
5) How we use information
We use the information described above to:Create and maintain entries in the public database
- Verify that submissions were authorised by the controlling private key
- Display, query, and retrieve public entries in the app
- Maintain integrity, abuse prevention, and operational reliability of the service
- Enforce our rules and remove illegal or harmful content
We do not use your data for targeted advertising or behavioural profiling.
6) Public database disclosure and visibility
By design, submissions are recorded into a public, transparent database available to all users. Entries are associated with public key pseudonyms, not with real-world identity. Because StikiLinks does not provide key exchange or identity linking, entries are not identifiable unless a user has been informed out of band of the identity behind a public key.
7) Data sharing and “selling data”
StikiLinks does not sell personal data without user consent or without transparent visibility.If StikiLinks introduces a feature in the future that enables data licensing or sale, it will operate under the following principles:
Explicit opt-in: Participation will require clear, affirmative consent.
High-granularity controls: Consent will be specific (e.g., by data type, time range, scope, counterparty class, and intended use).
Transparent visibility: Users will be able to see what categories of data are eligible, what has been authorised, and the terms that apply.
User contractual rights: Users who opt in will have contractual rights to a defined portion of proceeds attributable to the authorised use of their data, as specified at the time of consent.
No retroactive inclusion: Data will not be included in any licensing or sale program unless and until the user opts in.
8) Content moderation and enforcement
We reserve the right to remove and, where appropriate, report content that is illegal, harmful, or otherwise violates our rules. Because the database is public, we take moderation seriously to protect users and comply with applicable laws.
9) Security
We apply reasonable technical and organisational safeguards to protect the service and prevent unauthorised access, tampering, or misuse. However, no system can be guaranteed 100% secure. The public nature of the database means that information you submit is intended to be visible to others.
10) Changes to this policy
We may update this Privacy Policy from time to time. When we do, we will update the effective date and provide notice within the app where reasonable.
Effective date: 1 January 2026
This Data Deletion Policy explains how deletion works in StikiLinks, what deletion means in a public database context, and what limitations apply.
1) Core principle: user-controlled deletion
StikiLinks is designed so that users have direct, immediate control over deleting their contributions through basic app functionality. There is no email-based deletion request process because deletion is built into the product.
2) What you can delete
You can delete, at any time, the StikiLinks entries that were created under your public key pseudonym, including associated payloads and related metadata required for the entry to exist as an item (e.g., linkage data necessary to represent the entry).
3) How deletion works
When you delete an entry through the app:
- The entry is removed from active display and retrieval pathways in the StikiLinks service.
- Your public key pseudonym is no longer associated with that deleted entry in the live database.
- The entry becomes unavailable to users through normal StikiLinks functionality.
4) Accessing all data for a public key pseudonym
StikiLinks provides in-app functionality for users to access and review all data stored against their public key pseudonym. This includes the set of entries attributable to that pseudonym that remain present in the live database at the time of access.
5) Operator-initiated deletion
StikiLinks may delete content without user action if we determine it is illegal, harmful, abusive, or otherwise violates our rules. We may also take steps to prevent repeated misuse, including limiting access or blocking certain activity patterns.
6) Important limitations (public database realities)
Because StikiLinks entries are public by design:
A. Third-party copies: Other users or third parties may have viewed, recorded, or copied public entries before deletion (e.g., screenshots, exports, independent archives). StikiLinks cannot control or delete copies made outside the service.
B. Out-of-band identity disclosure: If you share your public key or identity relationship out of band, StikiLinks cannot reverse that disclosure.
7) Backups and technical retention
StikiLinks may maintain short-term backups for reliability, security, and disaster recovery. If backups exist, deleted entries may persist in backup storage temporarily but will not be restored to active service except as required for system recovery. Where feasible, backups cycle and expire on a routine schedule.
8) No deletion verification process
StikiLinks does not require identity verification to delete entries because deletion is authorised by cryptographic control of the relevant public key pseudonym. If you lose control of your private key, you may lose the ability to delete entries associated with that public key.
9) Policy updates
We may update this Data Deletion Policy from time to time. Updates will be reflected by revising the effective date and providing notice within the app where reasonable.
.svg)
.svg)