Get K256

Your privacy.

Who this policy covers

Perfroute Inc operates K256. This policy covers the K256 iPhone app, its supporting services, and this consumer website. Contact support@k256.xyz with privacy questions or requests.

K256 is self-custodial: your account keys stay on your device. You do not need to give us your email or phone number to use the app’s core features. If you choose social, support, notification or funding features, we process the information those features need, as explained below.

Information you share with us

Public profiles, follows, posts and public financial activity may be seen by others. Messages and shared expense pictures are available to their intended participants. Do not put private information into a public post or a public blockchain record.

Messages are stored for delivery and use by their participants; do not assume they are end-to-end encrypted. We also read public blockchain information to show supported balances and activity. We do not keep a separate database of your current balances or private balance amounts.

Information collected when you use K256

Network and security records may include IP addresses, device or browser information, request identifiers, timestamps and errors. We use these to operate the service, prevent abuse, investigate failures and protect accounts. Apple supplies diagnostics and beta feedback according to your Apple and TestFlight settings.

This consumer website does not use advertising trackers or set application cookies. Your browser requests public market data and images from K256. K256 obtains this data from tokens.xyz through shared server requests and briefly caches it on Cloudflare. We do not send your browser IP address or session to tokens.xyz. Visiting TestFlight or another linked service is subject to that service’s practices. Infrastructure providers may process connection information, such as IP addresses, to deliver and protect the website.

What stays on your device

Apple handles Face ID and other system passkey verification. K256 receives the authorization result, not your biometric data. The app derives and protects your account signing key on your device. K256 does not receive your recovery phrase. We do not read your phone’s address book or build an advertising profile.

Private amounts are read on your device. This does not make public blockchain activity private: public funding, account addresses, transfers and other public records can remain visible. Restoring private balances can require recovery material beyond a synced passkey.

How we use and share information

We use information to provide account access, social features, payment requests, notifications and support; personalize the feed you choose; secure and improve the service; and meet legal obligations. We do not sell personal information or use it for targeted advertising.

Service providers help us host the service, store account and social information, read public market and blockchain data, deliver notifications and email, and provide funding when enabled. These include Cloudflare for hosting and delivery, Neon for application data, Apple and Google Firebase for notifications, and the funding provider presented during checkout. We disclose information needed for the relevant service, rather than giving these providers access to your account keys.

Information is shared with the audience you select and with third parties you authorize. We may disclose information when legally required, to protect people and the service, to professional advisers, or as part of a business transfer subject to applicable protections. Providers may process information in countries other than yours.

Our service operations and providers may process information in the United States and other countries whose privacy laws differ from yours. Transfers are subject to applicable data-protection requirements. Contact us for information about the locations and safeguards that apply to a transfer affecting your data.

Adding money through a partner

A funding partner handles its own checkout, payment processing, eligibility checks and any required identity verification. The Coinbase Apple Pay flow requires a phone number and receipt email, plus acceptance of Coinbase’s terms. When you use that flow, K256 passes those details, your connection IP address, the destination account and order information to Coinbase. K256 saves the email and phone as contact records when you submit the request, including if the partner later refuses the order. Contact details are optional for general app use, but this funding method cannot proceed without them.

K256 receives order identifiers, status and settlement references, not your full card number or Apple Pay biometric data. Coinbase handles information it collects under its own privacy policy. Other partners, if made available, are identified before checkout. Availability, including any demonstration mode, is explained in the app and on our Support page.

Receipt reading, when you choose it

When you ask K256 to read a receipt, the receipt pictures go to Google LLC’s Gemini service. If that reading is insufficient, they may also go to Anthropic, PBC’s Claude service. You can type the details instead. The app asks before the first read on each device and removes image location and camera metadata before upload.

The request includes the receipt pictures, reading instructions, date and selected currency. It does not include your K256 name, handle, account or expense participants. A receipt picture can itself contain personal information. Check the returned items and amounts before using them.

K256 does not retain the model’s raw reading. A receipt picture you attach to an expense is stored with that expense. A confirmed expense can also retain reading configuration and correction information, such as edits, additions or deleted items. Request deletion in the app or by email.

Notifications

Apple and Google Firebase use installation identifiers linked to your account to deliver generic alerts. Those delivery payloads contain no message text or amounts. If you enable sender previews, your device reads the sender’s name and picture and shares them with Apple for the notification, including on your lock screen. Turning previews off requests removal of saved interactions.

You can choose alert categories in K256 and disable notifications in iPhone Settings. Signing out retires that phone’s notification registration when it reconnects.

Retention, removal and your choices

We retain information while needed to provide the service, handle your requests, prevent abuse, resolve disputes or meet legal obligations. Retention depends on the information and purpose; a support or security record may need to be retained after you stop using the app. We use technical and organizational safeguards, but no system can promise absolute security.

In the app, you can edit your profile and contact details, manage notifications and sharing preferences, and choose “Remove your name and handle.” That removal erases your personal profile, posts, message text and reachability records. Account associations, revoked device records, preferences, favorites, price watches, shared-expense memberships and shares, shared group and index metadata and covers, and funding and receipt references remain. Ownerless username reservations and aggregate counts also remain. Passkey deletion is controlled separately by your credential provider. It does not move your money, erase public blockchain records or guarantee deletion of copies others have received. Keep your recovery material before removing access.

Deletion applies to the records described above; it is not a promise that every service record disappears immediately. Information may remain where needed for security, resolving a dispute, complying with law, or maintaining a shared record. Blockchain records and copies held by other people or independent providers are outside our deletion control. Ask us about a particular record if you need help.

Privacy requests and regional rights

For other deletion, access, correction or privacy requests, use support in K256 or email support@k256.xyz. We may need to verify that the request concerns your information using a method proportionate to the request. Do not send a recovery phrase, private key or identity document by email.

Depending on where you live and which laws apply, you may have rights to know or access the personal information we process, obtain a copy, correct it, request deletion, restrict or object to processing, withdraw consent, and complain to a privacy authority. Where required, an authorized agent can make a request after we verify their authority. We respond within the time required by applicable law, explain any permitted limitation, and do not discriminate for exercising a right. If a request is declined and an appeal right applies, reply to our response with “Privacy appeal” or contact support.

We do not sell personal information or share it for cross-context behavioral advertising, including as those terms are defined under California law. There is no advertising sale or sharing for a Global Privacy Control signal to turn off. The information categories, purposes and recipients described in this policy also explain our practices for California residents; rights and exceptions apply where the relevant law covers the service.

Where a legal basis is required, we process information as needed to provide the service you request, for legitimate interests such as security and support where those interests are not overridden by your rights, to meet legal obligations, or with your consent when required. Withdrawing consent does not affect processing already lawfully done.

Children and updates

K256 is intended for adults who are at least 18 and legally able to use the service. We do not knowingly collect personal information from children under 13. If you believe a child has provided personal information, contact us so we can investigate and delete it as required. We may update this policy as the service changes. The effective date identifies the current version. We will give notice of material changes and obtain consent where applicable law requires it, before using information for an incompatible new purpose.