Privacy Policy
Effective date: 2026-11-02.
Document version: 2026-10-20. Publication URL: https://www.getblessed.fun/privacy.
1. Who is responsible
Suntendo, of CO Services Cayman Limited, PO Box 10008, Pavilion East, Cricket Square, Grand Cayman, KY1-1001, Cayman Islands, is the operator of the website and the app. Email: hi@suntendo.com. Privacy contact: hi@suntendo.com. Website: https://suntendo.com/.
We are the controller of the information we decide how to use, including support requests and the application records described below where those functions are enabled. We do not operate our own chain indexer. Where enabled, the website's positions page and the app's Balances ask a third-party hosted index, Goldsky, through our server, which coins may be linked to the wallet address, as described in sections 3, 5 and 6. Sign-in and wallet links are handled through Privy. Our consent and deletion-request records use the Privy sign-in identifier; those records are separate from Privy's account and wallet records. Privy describes circumstances in which it is a controller and circumstances in which it processes information on behalf of its customers. Its own privacy policy applies to processing for its own purposes: https://www.privy.io/privacy-policy.
2. The short version
- We process sign-in and wallet information through Privy, and make the chain reads needed for the functions a version offers. The first iOS release offers a live Discover catalogue, search, status filters and coin details, as well as an address and quantities. A displayed stock target is not an actual stock-reserve balance or proof of company ownership. The app does not submit transactions, send assets, or offer market charts or transaction history.
- Blessed never asks for your private key or seed phrase to sign you in, provide support, or delete an account. Enter a sign-in code only in the sign-in provider's verification flow; support and deletion requests never ask for it.
- The chain is public. Deleting an account does not erase it.
- We do not sell personal information for money, and we do not use it for cross-app advertising.
- We do not publish a fixed number of days. We keep personal information for the purposes in this policy and for as long as the law requires a record.
- The services do not include a fiat purchase. We do not collect card numbers or identity documents for one.
3. Information we process
The rows distinguish the first iOS release from website functions that are offered only where enabled. The account-deletion page shows whether authenticated website requests are currently available. When enabled, signing in with the same Blessed account and explicitly confirming a request creates the receipt described below. The receipt is a request record, not confirmation of completed deletion. Document-confirmation records are created only when the configured service accepts your confirmation. Account-deletion availability is explained in section 8.
| Information | Where it goes | Why |
|---|---|---|
| Name, when supplied by the sign-in provider; email address, Apple, Google or X (Twitter) account identifier, Privy user id | Privy, the sign-in provider you choose, and the interfaces that consume the authenticated session | To sign in and restore the existing app wallet; if none exists, creation requires explicit document confirmation. A provider profile name is optional and depends on the sign-in method. We do not use Sign in with Apple data for advertising, sell it to a data broker, or combine a private-relay email with another identifier for advertising |
| Wallet address and chain id | Our interfaces and host; the RPC provider for chain reads | To show the address and quantities. The native portfolio request carries the address to the server in its request body; it is not an exhaustive scan of every asset at the address. The address is not anonymous once linked to a sign-in |
| Wallet address, for the website's positions page and the app's Balances, only where the hosted index is enabled | Our host; Goldsky, the third-party hosted blockchain index provider | To find coins that may be linked to the address through past public on-chain events. The page or app sends the address to our server in the request body, not in the URL, and our server sends only the address as the query to Goldsky. It does not send a signature, key, sign-in identifier or your IP header with it. Goldsky returns a list of coins; the result only helps choose which coins to show; balances and rights shown are read from the chain, and the result is not used to decide or approve a transaction. We use the address only while handling the request: we do not store it in our application database, and our server code does not log it. iOS app versions that include this function use it for Balances |
| Search text, for Discover search on the website and in the app, only where the hosted index is enabled | Our host | To find matching coins. The page or app sends the search text and any stock filter to our server, which matches them against the index's coin list. Your IP address and user agent reach our host as with any request. Because the search text is part of the request URL, it may appear in host request logs. The search text is never sent to Goldsky |
| Wallet-asset balances and snapshots; verified contract state; transaction hashes, calldata, and events for website functions that use them | Our interfaces, host, and RPC provider; Privy for its wallet-asset analytics; the chain for transactions actually submitted | To show verified reads and support the actions a version offers. Privy may process wallet-asset balances and snapshots for its wallet analytics. The first iOS release does not send transactions. The website may use bounded RPC reads and sampled state; this is not a dedicated chain index or a promise of complete history |
| Pending-action and fee inputs for website transactions | Browser session storage; the server and Privy when an enabled relay action is prepared or submitted | To review and submit an explicitly requested action. The relay does not maintain a transaction database; hosting or provider logs are separate. The first iOS release has no such transaction actions |
| IP address, user agent, request logs, and host-side request performance information such as function duration | Our host receives connection, request and performance information; Upstash, or our hosted database as a fallback, receives the keyed hash used for request limits; Privy receives connection and service information; the RPC provider receives the RPC call payload | To operate and secure the interfaces, diagnose failures and assess request performance. Our host receives your IP address. To apply per-IP request limits on the index-based functions, our server can write a keyed hash (HMAC-SHA256 with a server secret) of your IP address, or of its /64 network prefix for an IPv6 address, with the function name, the one-minute window and a request count, to a shared counter. The counter is kept at Upstash (Redis, hosted on AWS in N. Virginia, United States), where each record expires automatically within about two minutes. If Upstash is not configured or does not answer, the same record is written to our hosted database instead; those rows are normally deleted about two minutes later, when later requests arrive. The raw IP address is not stored at Upstash, in our database or in our logs. The server also keeps the unhashed IP address or prefix in memory for the current window to apply the limit; it is not written anywhere. The keyed hash is pseudonymous, not anonymous: whoever holds the secret can match it to an IP address. When the secret is not configured, nothing is stored at Upstash or in the database and the server counts in memory instead; it does the same while neither is available. Memory entries are cleared when later requests arrive. Our proxy does not forward your IP header to the RPC provider. A provider may derive location from connection information as described in its own privacy policy |
| Privy software diagnostics and analytics | Privy | The installed SDK includes request paths for event names, a persistent client identifier and event payloads. These are distinct from a separate advertising kit. Privy describes its processing purposes and handling of service information in its privacy policy |
| Support mail and deletion requests sent by email | Cloudflare Email Routing, the Gmail mailbox receiving the forwarded message, and any request records actually maintained | A person reads the support mailbox and handles deletion requests. Opening a draft sends no email and creates no automated deletion receipt. Do not send keys or sign-in codes |
| Website deletion request | Our application database hosted by Render in Virginia, United States | A random receipt identifier, verified Privy sign-in identifier, receipt/update/completion times, request status, and an individual processing estimate, for accepting and handling the request. No reason, wallet address, email, IP, key, sign-in token, or provider token is stored in this table. This does not describe host or provider logs |
| Deletion handling record | Our account-records database and the operator's restricted case records | The case reference, internal revision, verification/contact checks, processing and notification outcomes, confirmation times, and random references to restricted evidence. The database journal contains no evidence text, email address, wallet address, key, or sign-in/provider token. A case reference remains linked to the request; it is not anonymous |
| Push token | No app-level push function or selected push provider in the first iOS release | The first iOS release does not offer app-level push notifications |
| Website gas-sponsorship counters, only where configured and enabled | The application's configured Postgres: HMAC of the Privy user id, UTC day, and count | To apply published limits and detect abuse. The counter table does not store the raw Privy id, address, IP, or transaction payload. HMAC does not establish anonymity. The first iOS release sends no transactions and uses no sponsorship |
| iCloud or CloudKit recovery material | Not offered by the first iOS release | The first iOS release does not offer iCloud or CloudKit wallet recovery |
| Card data, government id, MoonPay customer data | No fiat on-ramp | The service does not provide a fiat purchase or collect card numbers or identity documents for one |
| Document confirmation | Our application database hosted by Render in Virginia, United States; interface session state for the current confirmation | Verified Privy sign-in identifier, Terms and Privacy URLs, document version, interface, random receipt identifier, and server receipt time. To record explicit confirmation before requesting a new wallet. The receipt does not prove that wallet creation succeeded. The table does not store email, IP, wallet address, keys, or sign-in/provider tokens |
| App sign-in/session storage | Privy SDK-managed device storage, including SecureStore on native | To retain or restore the sign-in session. Storage is handled by the SDK and operating system. Signing out of a device is not account deletion |
| Receive QR and Copy address | QR generated locally; the device clipboard receives the displayed public address on Copy address | To receive funds and copy the same address. No external QR-generation service is used. Device clipboard access and retention depend on the OS |
| Creator images, CIDs, and signed image versions, when website image upload is configured | Our host, the pinning provider/IPFS and gateway, and configured application Postgres | To verify the registered creator, process and pin the image, and retain accepted image versions. Records include the coin identity, creator address, CID, signature, version, verification block, and acceptance time. Image metadata is removed during re-encoding; that does not make the image anonymous. Public IPFS copies may remain |
| External links, such as the block explorer | The external site, when you open it | Opening an external site discloses connection information, including IP address, to that site, which has its own data practices. The website does not embed third-party market charts |
The first iOS release does not offer a separate advertising or crash-reporting product. Authentication, session and SDK diagnostic information are distinct from those products.
Coin names and transactions can be public on-chain. Creator images use off-chain signed metadata and IPFS when configured. Treat both as public; hiding an image in our interface does not erase IPFS copies. A dedicated chain index is not used for either path.
Where offered on the website, you can sign in with X (Twitter) through Privy. Privy and the sign-in provider process your X account identifier and the profile information supplied for authentication. The website uses the authenticated session to restore your app wallet or, if none exists, request its creation after recording the required document agreement. X sign-in is not offered in the native app.
4. Why we use it
We use the information above to:
- authenticate you and reopen the same wallet;
- display quantities and verified state, and provide the website views that the deployment offers;
- send a transaction you request through an enabled website function and show its result; the first iOS release does not send transactions;
- secure the interfaces, limit abuse, and debug a failure;
- answer support and emailed account requests; and record document confirmation and authenticated deletion requests where those services are enabled;
- meet a legal duty.
We do not use this information to advertise third-party products, and we do not allow a data broker to use Sign in with Apple data.
5. Who else processes it
| Party | Role | What they receive |
|---|---|---|
| Privy (https://www.privy.io/privacy-policy) | Sign-in and app-wallet provider; a processor or controller according to the processing described in its policy and the applicable agreement | Sign-in identifiers, wallet data, and device or service information its software transmits |
| Apple | Sign in with Apple, and distribution of the iOS app | The Apple account identifiers the sign-in returns. Push only if we later use APNs |
| Google sign-in; Gmail receives and stores support mail forwarded by Cloudflare. Android distribution only if we ship Android | The account identifiers the sign-in returns; support messages and attachments you choose to send | |
| Vercel | Hosts the product website and server API | Connection and request information, including IP address and user agent; hosting logs are separate from account-record tables |
| Render | Hosts the configured account-records PostgreSQL database in Virginia, United States | The consent and deletion-request fields described in section 3; database backups can contain those records |
| Upstash | Hosts the shared request-limit counter and short-lived server caches (Redis) on AWS in N. Virginia, United States | The keyed hash of an IP address or IPv6 /64 prefix described in section 3, with the function name, the time window and a count; these records expire automatically within about two minutes. A cache of public chain checks kept for at most 10 seconds, which contains no personal data. Upstash receives our server's connection information, not your raw IP address |
| QuickNode | Provides the configured mainnet RPC endpoint | RPC call payloads, which can include wallet addresses and transaction data. The proxy does not forward your IP header |
| Configured image pinning provider and IPFS gateway | Off-chain coin-image storage and delivery, where the website image function is enabled | Processed images and CIDs; accepted signed image metadata is also stored by the application. IPFS copies can remain outside our control |
| Linked external sites | Their own sites, when you open them | Connection information disclosed by the navigation is processed under that site's own practices |
| Goldsky | Hosted blockchain index queried by our server for the website's positions page and the app's Balances, where enabled | The wallet address being looked up, sent as a query from our server, and our server's connection information. Goldsky keeps and handles query records under its own policies |
| Cloudflare | Forwards incoming support and emailed account requests to Gmail | Messages and delivery information for mail you choose to send to the published address; do not send keys or sign-in codes |
| A push vendor | None selected | Nothing today |
Providers can process information on our behalf or for their own purposes, according to the service and applicable agreement. A provider's own policy applies where it acts for itself. A provider's records are separate from our application database.
We do not sell personal information for money.
6. On-chain data and application records
A wallet address, a balance, a transaction, and a contract right are written to Robinhood Chain. Anyone can read them. We cannot edit or delete the chain.
Before you send a transaction, the interface shows what you are about to publish. A purchase amount and the sending address will be public. A whitelist proof is tied to the address. If we publish a list of whitelisted addresses, that list is personal information.
We do not maintain our own chain index. Where enabled, the website's positions page and the app's Balances ask a third-party hosted index (Goldsky), through our server, for coins that may be linked to the wallet address; it narrows which coins are read and does not replace the chain reads. Our interfaces make RPC reads, and the website can read bounded events or sample reserve state for specific views. The website does not embed market price charts. Our server also keeps verified public coin state, such as coin-detail snapshots, history points and the Total treasury figure, in a hosted database. These coin-state records hold no viewer's wallet address, IP address or sign-in identifier (the rate-limit rows described in section 3 are kept separately); a page view records only a per-coin time, used to decide which coins to refresh. This does not mean that we hold no off-chain personal information: support mail, configured consent and deletion-request records, conditional sponsorship counters, signed image metadata, and host or provider records are separate from public chain data. A public chain record and a record held by us or a provider are different copies. Deleting a sign-in does not erase the chain or public IPFS copies.
7. How long we keep it
We do not publish a fixed number of days. We keep personal information for the purposes in this policy, and for as long as the law requires us to keep a record. When those reasons end, we delete it or de-identify it. Backups can retain earlier copies during the provider's backup cycle. The chain is not deleted.
The criteria are:
- sign-in and account links we actually hold, if any: for the life of the account, and after that only while a security reason, a dispute, or a legal duty lasts;
- server logs: while the security purpose lasts;
- application records we actually hold, including signed image metadata and records linked to a sign-in: retain only while the purpose or a legal duty requires;
- document-confirmation records: while needed to establish what was confirmed, resolve a dispute, or meet a legal duty;
- support and deletion records: for the time needed to complete the request and to show that we did;
- index lookups for the positions page and Balances, where enabled: we do not store the queried address in our application database; Goldsky's retention follows its own policies;
- rate-limit records holding a keyed hash of an IP address or network prefix: at Upstash, they expire automatically within about two minutes; in our hosted database, used as a fallback, they are deleted when later requests arrive, normally within about two minutes;
- sponsorship counters, where enabled: only while we need them to apply the published limits and investigate abuse;
- the chain: not deleted.
8. Account deletion
The page at https://www.getblessed.fun/delete-account shows whether online requests are currently available. When enabled, sign in with the same account you use in Blessed and explicitly confirm the request to save an authenticated receipt. A person handles the request. You can also contact hi@suntendo.com about your account. A message or an opened email draft does not by itself verify a request, save an authenticated request receipt, or complete deletion.
Our deletion policy does not require a reason, reinstallation of the app, a zero balance, or prior key export. It covers the website and app sign-in sharing the same Privy user. It does not delete an unrelated external wallet you connected on the website.
The policy separates four parts:
- Our off-chain account information and any sign-in/address links we actually hold. Privy's records are separate.
- A request to Privy to delete its user, and the result of that request. Privy may retain archives; this is not a guarantee of instant or total provider erasure.
- Records retained while a specific security purpose, dispute, abuse-prevention purpose or legal duty requires them. Backup copies can remain during the provider's backup cycle.
- Public chain records, assets and rights. Those remain with the address, including coins, Genesis claims and refunds.
Required Apple or Google revocation is separate from a Privy user-deletion request. These revocation steps have not been verified end to end. Deleting a Privy user does not by itself confirm either revocation. We process our records and the Privy deletion request, check applicable provider steps, and report completed and outstanding steps separately. No statement here guarantees automatic revocation or reports that your account or provider credentials have already been deleted or revoked.
The handler provides an individual processing estimate, updates and the result. A saved receipt means a request was saved, not that deletion is complete. A failed or unresolved step is not completion. There is no fixed account-deletion completion period, and the statutory response periods in section 9 are separate.
Support and account-deletion requests do not ask for a private key, seed phrase or sign-in code. Sign-in-provider verification is a separate flow. Where export is offered, you can use the dedicated website key-export page, which the iOS app opens in the system browser. Export is optional. Without an exported key, deletion can leave you unable to reach the old address through Blessed. It does not transfer or forfeit the assets or contract rights at that address.
Browsing offered without an account remains separate from account sign-in.
9. Your rights
Depending on the law that applies, you can ask for access to personal information, correction of inaccurate information, deletion, or restriction or cessation of a particular use. You can complain to a regulator. Write to hi@suntendo.com. The reader of that mailbox handles data-rights requests. We may need information reasonably necessary to verify your identity or locate the information. That does not include a private key.
Under the Cayman Islands Data Protection Act, access requests are subject to a 30-day response period, including the Act's verification rules and exceptions. Requests to stop or restrict processing are subject to the applicable 21-day period and statutory exceptions. These are legal response periods, not a promise that every account-deletion step will be completed within the same period. We will explain an applicable reason why a request cannot be fulfilled.
You may complain to the Cayman Islands Ombudsman about the handling of your personal data. Information and complaint forms are available at https://ombudsman.ky/data-protection.
You can stop using Sign in with Apple or Google from those accounts and stop using Blessed. Neither action erases public chain records.
10. Age
The services are for people who are 18 or older. If you believe we have personal information about someone under 18, contact hi@suntendo.com.
An unknown age does not, by itself, erase an existing wallet, prevent key export or an account-deletion request, or forfeit on-chain assets or contract rights.
11. International processing
Suntendo is established in the Cayman Islands. Our account-records database is hosted by Render in Virginia, United States. Providers including Privy, Apple, Google, Vercel, Upstash, QuickNode and, where enabled, Goldsky can process information in the United States and other countries in connection with their services.
A database region is not a promise that every provider record, support record or backup is kept only in that region. Countries can have different data-protection laws. For information about the processing of your personal data and applicable rights, contact hi@suntendo.com.
12. Security and breaches
We use access controls, encrypted transport where supported, and separation between our interfaces and the key-export frame served by Privy. No security measure is absolute. A security control cannot reverse a transaction the chain has accepted.
Send privacy or security concerns, including reports of a personal-data breach, to hi@suntendo.com. The reader of that mailbox handles these reports and escalates an incident immediately to the person responsible for Blessed. That person handles the report if the usual reader is unavailable.
Where section 16 of the Cayman Islands Data Protection Act requires notification of a personal-data breach, we notify affected individuals and the Ombudsman without undue delay and no later than five days after we should, with reasonable diligence, have become aware of the breach.
13. Advertising and browser signals
We do not use personal information to advertise third-party products or allow a data broker to use Sign in with Apple data. We do not operate a separate advertising kit. This does not make sign-in identifiers, wallet addresses or SDK client identifiers anonymous. Privy's software diagnostics and analytics are described in section 3 and its own policy.
We do not respond to browser Do Not Track signals.
14. Changes
We will post the new policy with a date. A material change states when it takes effect. Continued use after that date is not how we will obtain consent where the law requires a separate consent.
15. Contact
Suntendo CO Services Cayman Limited PO Box 10008 Pavilion East, Cricket Square Grand Cayman, KY1-1001 Cayman Islands https://suntendo.com/ hi@suntendo.com
Document version 2026-10-20. Effective date 2026-11-01.