Privacy Policy

1. Scope and contact

This policy describes information handling for apedin’s feed, accounts and community features at apedin.family. “We” refers to the service operator. For requests or complaints, email [email protected]. It also applies to people whose public information appears in imported content, even if they have never registered.

This is a launch draft. The operator’s legal disclosures, production storage locations and retention schedule still require final confirmation before public release. It is not a claim that the service complies with every privacy law worldwide. Independent services you visit or use for sign-in have their own policies.

2. What we collect and where it comes from

• Account and authentication data: an identifier from Dynamic, email when supplied by the chosen provider, display name, profile preferences, timestamps, session information and connected identity or verification details needed for supported features. Google, X or a wallet provider supplies information through the sign-in method you choose.
• Content and interactions: posts, thesis labels, images, comments, revisions, token identifiers, likes, saves, shares, follows and associated account identifiers and timestamps. Information comes from your submissions and other users’ interactions with your content.
• Progression and identity claims: eligibility evidence, provisional or awarded XP where enabled, levels, prestige, achievements, founding status, showcase choices, and source-profile claim or verification records. Reviewed claims also store a verification code, submitted public proof link, expiry and review decision. These records are available to the claimant and authorised reviewer as appropriate; submitting a claim does not publicly link the accounts.
• Safety and support records: reports, reasons and supporting information, blocks, AI assessments, human decisions, appeal correspondence, account restrictions and audit records. This may include material another person reports about you.
• Imported public information: handles, profile images, public wallet and token addresses, callouts, replies, trade context, holdings or other profile information and engagement counts, where supplied by Pump.fun, FOMO, GMGN or another identified source. We receive these through source feeds, APIs and enrichment services; availability varies.
• Technical information: network requests expose information such as IP address, browser or device details, requested resource, time and errors to the systems handling them. Authentication and infrastructure providers may keep security or diagnostic logs. This does not mean every request field is retained in apedin’s application database.

Public wallet addresses, handles and transaction history can identify a person when combined with other information. “Public” does not mean free of privacy protections. We do not ask for wallet private keys, recovery phrases or a payment-card number for the current account features. Do not include confidential documents or other people’s sensitive information in a post or support message.

3. Required and optional information

You can read the public feed without creating an account. Sign-in and a valid session are needed for posting and supported account interactions. Without the information required to authenticate or verify a profile claim, those features may be unavailable.

You choose whether to add a post, image, profile detail, additional sign-in method, showcase selection or support information. An email address may be supplied by a social provider; using a display name does not make all associated activity anonymous. You can decline to claim an imported profile and still request a correction or privacy review.

4. What other people can see

Published posts and comments, author display names, public profile identifiers, selected achievements, relevant progression information, timestamps, token details and aggregate engagement can appear publicly. Edit history can expose earlier versions of a published post. Imported profiles and source data may also be visible without sign-in.

Your account email is not displayed as a public profile field. Private research note text is not included in public posts or engagement events unless you separately publish it. A save can contribute to a count even though the saved research note remains private.

Public information may be indexed, copied, screenshotted, linked or redistributed by other people. Removing content from apedin cannot guarantee removal from their copies, search caches or the original source. An imported profile does not itself indicate registration, identity verification or endorsement.

5. Why information is used

• Deliver and organise the feed, token information and source discussions.
• Authenticate users, maintain sessions and preferences, and verify supported account or profile claims.
• Publish content and provide comments, follows, saves, sharing and profile displays.
• Calculate engagement, apply reward rules where enabled, prevent duplicate credits and correct invalid awards.
• Detect spam and security issues, assess reports, review appeals and enforce community rules.
• Respond to support and privacy requests, diagnose faults, maintain records reasonably needed for disputes, and comply with applicable legal duties.

These purposes do not authorise unrelated use merely because you visited the site. Where a particular use requires consent, we must obtain it separately. The current app has no dedicated advertising-tracking integration or marketing mailing-list feature; any future change would require appropriate notice and any legally required choice.

6. Automated processing and moderation

Rules can count eligible interactions and calculate progression or provisional profile credit. Results can be affected by unique-user limits, daily caps, delays, deleted content and confirmed abuse. These measures describe participation, not a prediction of financial success, creditworthiness or investment suitability.

We use a dedicated authenticated Cloudflare Worker with Workers AI to review submitted text. Content text, its type and an optional report reason may be sent for classification. Review currently covers posts and comments created on apedin, including comments on imported callouts, as well as reported imported content. It is not a claim that every provider-supplied item or image has been reviewed.

AI may flag content or temporarily hide suspected spam and can make mistakes. A flag or report alone does not deduct XP or permanently ban an account. Human review handles confirmed penalties and appeals. Contact us to challenge a moderation or progression result and explain why it is wrong. Cloudflare describes its own handling of inference data in its Workers AI data-use documentation.

7. Cookies and storage on your device

apedin uses a session cookie to keep you signed in and browser storage for local features. Session cookies expire; the duration can depend on the sign-in session. Temporary browser state supports the authentication flow. Dynamic and the social or wallet provider you select may use their own cookies, storage and diagnostic services.

Saved callout copies, research notes, follows, watches, mutes, alerts and some interface preferences are stored in your browser. Some signed-in actions, such as a save or follow, also create a server-side engagement record; private note text is not part of that event.

Browser data can remain until you reset it or clear site data. It is not automatically removed by logging out or deleting your server account, and can be accessible to anyone using the same browser profile. Settings has separate browser export/reset controls. Blocking required cookies or storage may prevent authentication or local features from working. We do not describe all third-party storage as strictly necessary without assessing its actual use.

8. Who receives information

• Other users and the public: the published information described above.
• Authentication providers: Dynamic and your selected Google, X or wallet service process the information needed for their login and linking functions. See Dynamic’s Privacy Policy; its practices are distinct from our own.
• Infrastructure and moderation providers: Hetzner hosts the application and its database in Falkenstein, Germany. Cloudflare provides network delivery, security and AI moderation. Relevant requests and data may also be processed by these providers and their subprocessors in other countries. Operational backups are maintained separately from the running application.
• Data and image providers: token or profile lookups send identifiers needed for the request to the relevant source. Provider-hosted images may load directly in your browser, revealing ordinary request information, including your IP address, to that host.
• Support services: email to our Outlook address is handled through Microsoft. Telegram or X processes communications made through those services. Avoid sending sensitive requests in public social posts.
• Authorised review or legal recipients: the service operator can access relevant information for support, moderation and security. Relevant information may be disclosed where required or permitted by law, to respond to a valid legal process, protect against serious harm or establish or defend legal claims.

In a complaint, we may share the allegations or relevant content with the affected person to obtain a response. Reporter contact details are not public report fields; confidentiality cannot be guaranteed against a lawful disclosure requirement. We should disclose only what is reasonably necessary for the purpose.

Any future business transfer involving personal information would need a lawful basis, appropriate safeguards and notice where required. This policy does not provide an unrestricted permission to sell or repurpose personal information. External links are governed by the destination’s own practices.

9. International processing

Service providers operate internationally, and information may be processed outside the country where you live. We do not promise Australian-only hosting or storage.

The production hosting region, relevant overseas recipients and processing countries, and any required transfer safeguards have not yet been fully confirmed. Those details must be assessed and this section completed before public release. Contact us for the current information about a particular provider. An international provider’s headquarters alone does not identify every processing location, and use of the service is not blanket consent to waive transfer protections.

10. How long information is kept

Active account, content and interaction records support the service. Safety and reward records also support investigations, corrections, duplicate prevention and dispute handling. Relevant factors for retention include whether an account or contribution remains active, an unresolved report or appeal, a legal preservation requirement and whether the information is still reasonably needed for its purpose.

In the current build, expired sessions are pruned during account operations, but there is no fixed automatic expiry for every category of posts, revisions, imported snapshots, reports or audit records. Those records may remain until deleted or otherwise purged. A general retention schedule and backup expiry process are still launch requirements; this draft does not claim they are implemented.

Information that must be kept for a specific lawful reason should be limited to that reason and period. A retention exception is not permission to keep everything indefinitely. A deletion request can be reviewed separately from the ordinary in-app controls.

11. What deletion does—and does not do

• Deleting a native post: removes it from normal public display and blocks its image from the public upload route. A discussion placeholder can remain. The current system retains the post text and revision records internally after this action; it is not complete erasure. Physical image cleanup is separate.
• Deleting your account: removes the active account, sessions, preferences and related account-owned records; blanks native post/comment text and removes native post revisions. It removes upload references, with file cleanup handled separately. Deleted-post placeholders and inactive interaction records with replacement identifiers may remain.
• Limited deletion records: a deleted authentication-identity identifier and deletion time are retained to prevent unintended restoration. Some replacement identifiers support prevention of replayed rewards. These are not a promise of irreversible anonymisation.
• Other people and sources: account deletion does not delete another person’s independent replies, imported provider history, public blockchain records, copies held elsewhere or accounts with Dynamic, Google, X or a wallet provider.
• Your device and backups: browser-saved copies and notes require separate reset or browser clearing. Existing backup copies are separate from the active database; immediate erasure from every backup is not guaranteed. Backup retention still needs a defined production schedule.

Deleting an account is more extensive than deleting a post. For a specific erasure request, including text retained after post deletion, email us. We will assess what can be removed and explain any lawful reason for retaining information. Do not assume a blockchain transaction can be erased by an account request.

12. Access, correction and other choices

Use account controls to update supported profile information, export account data or delete the account. The export is an application export; it may not contain every provider-held record or every record available through a formal access request. Settings separately exports or resets browser data.

You can email [email protected] to request access, correction, erasure or review of imported information, even without an apedin account. Identify the account, source or content and the change sought. We may request proportionate proof of identity or authority before disclosing private information or changing someone’s profile. Do not send a recovery phrase, private key or identity document unless a suitable verification process has first been agreed.

Depending on the law that applies, you may also have rights to object to or restrict processing, receive portable data, withdraw consent for a consent-based use, or challenge certain automated decisions. Withdrawal does not undo earlier lawful processing. These rights can have lawful limits; where a request cannot be fully met, we will explain the applicable reason and review options, unless prohibited by law. Requests will be handled within applicable legal time limits.

We can review our copy of imported information, but cannot correct or erase the original provider’s records. You may need to contact that provider separately.

13. Security and incidents

The app uses authenticated sessions, access controls and request protections. These reduce risk but do not guarantee that information will never be accessed, lost or disclosed without authorisation. Public contributions are not confidential communications. Keep your sign-in accounts and devices secure.

Report a suspected data exposure or compromised account to our email with enough detail to locate the issue, without sending secrets or accessing other users’ records. Where an incident triggers notification duties, we must assess it and notify affected people or regulators as required by the applicable law. Do not rely on social messages for an urgent emergency.

14. Children and age restrictions

apedin is intended for adults aged 18 and over. This statement does not mean we have independently verified every user’s age. Do not create an account for a child or publish personal information about children.

If you believe a child has supplied information or appears in imported material, contact us with its location so we can review the information, account and any applicable removal or safeguarding obligations. Age-assurance and social-media regulatory obligations are being assessed before public release.

15. Privacy complaints and policy updates

Email [email protected] with your concern, relevant identifiers and preferred resolution. We will acknowledge the complaint, seek any necessary details and provide a response explaining our assessment and next steps. We may need to verify identity before sharing private records.

You can contact the privacy regulator with jurisdiction over your complaint. In Australia, this may be the Office of the Australian Information Commissioner, subject to its eligibility and complaint process. Your legal rights and ability to seek an independent remedy are not limited by this policy.

We will date revisions and provide appropriate notice of material changes. New purposes, optional tracking or uses requiring consent must be addressed before they begin. An updated policy does not retrospectively authorise unlawful collection or remove accrued rights.