Security and permissions
Know who can see your data, choose website access, and recover safely.
Use Palside's controls to choose what you share and where page features can run. Squad encryption, browser permissions and public payments protect different things.
Protect your account keys
The recovery phrase, local password and wallet private key are handled on your device, not uploaded. The service receives public identity and address proofs, signatures and operational records.
Store the phrase offline. The 6-digit password encrypts the phrase in this browser; it cannot defeat someone who controls the device or can copy and attack its stored data. If you forget it, make sure you have the phrase before signing out. Signing out clears local message keys and drafts. A new login does not restore old message keys.
In account security, check the device list and remove unused or lost devices. Closing the browser does not sign out. If every copy of the phrase and usable login is lost, Palside cannot recover the account.
An account can have up to 10 devices. An 11th is refused until you remove one; older devices are not removed automatically. Five wrong local-password attempts lock access, escalating from 15 minutes to 1 hour to 24 hours. A correct entry resets the count; unlocked failures reset after 24 hours. Online status changes to away after 5 minutes without keyboard or mouse activity.
Know who can see what
| Data | Visibility |
|---|---|
| Squad messages, images, viewing and saved page notes | Encrypted for authorized members; the service does not hold content decryption keys |
| Danmaku, its token and opinions | Public, not encrypted; the service also knows which token an account participates in |
| Recruitment | Published squad profile, captain profile information, member count and public ranking labels; not the chat, full member list or viewing |
| Account, membership and connection information | The service processes identity, membership and necessary connection/security metadata |
| Wallet | Public address binding, orders and payment status are processed by the service; chain addresses, amounts, contracts, hashes and times are public |
| A report you submit | Selected report content is intentionally sent to official reviewers, including private messages you choose to report |
Quotes and notes include limited surrounding text for anchoring and the page address alongside the selected passage. Locating text temporarily traverses readable page text and builds a task-local index on the device; it does not persist a full-page text archive. Sent quotes and saved notes reach authorized members as encrypted squad content.
Participation in danmaku can send token names, image URLs and source websites to the service for public room profiles and trending lists.
Alchemy, RPC and indexing providers process submitted transactions and public chain data. Loading public token images can disclose connection information to their image provider. Encryption does not hide every account relationship, IP address or connection time.
Grant only the access you need
The build declares the permissions needed to run its side panel and local encrypted client. Optional tabs / favicon, website access and notifications are requested when needed. activeTab is declared with the extension and grants temporary access through a toolbar click or the screenshot shortcut. The manifest has no static content scripts or blanket required website access; this is not a promise that the extension uses no permissions.
| Chrome permission | Purpose | Your control |
|---|---|---|
Read your browsing history (tabs / favicon) | Current-page share viewing and site icons | Enable share viewing; revoke it to stop share-viewing observation |
| Read and change site data | Page interactions and supported token metadata | Add selected websites or explicitly allow all websites; revoke in website settings |
| Notifications | Desktop message alerts | Enable in notification settings; off by default |
| Current-tab access | A scoped page action or screenshot | Granted by clicking the Chrome toolbar icon or the screenshot shortcut, not by a click inside the side panel |
Chrome uses broad wording for browsing access. Palside uses only the frontmost window's active page for share viewing, not a history export. Ordinary websites share only the site identity; token pages can share token identity and its public source.
Add websites together
Open Settings › Web › Websites › Add websites, select the sites you want, then choose Add N websites. One Chrome request covers that selection, using each exact origin, not every website, other protocols or unselected subdomains. If you decline, the selection stays and nothing is added.
Website settings also offer Allow all websites, which requests broad access. Removing one site cannot exclude it while a broad grant exists; revoke broad access first, then retain or add the individual sites you need.
Granting website access does not turn on share viewing. Chrome does not offer a read-only website permission, so reading supported token names and logos uses “read and change.” Palside does not automatically extract balances or holdings, or read input values. Visible text you select may include account or trading information; check it before sharing. Quotes, notes and signals exclude input controls, editable areas, invisible content, scripts and templates, canvas/iframe and Palside’s own page layer, without filtering by area names or keywords.
Stop sharing or revoke access
Turn off the relevant composer button to stop that feature. In Settings › Privacy & data, choose Revoke on a permission to disable its dependent features and remove it. Revoking all effective access to a site stops its page layer; disabling web interactions removes website permissions and remembers the sites for a new request if re-enabled. Chrome's own site-access controls also apply.
These actions stop future access; they do not delete messages or notes already shared. Messages and notes follow squad retention; viewing state and danmaku follow their own storage rules. Other people's saved copies cannot be recalled.
Desktop notifications are generated locally after decryption. They are off by default, with body previews separately off by default. Muting a squad suppresses its desktop notifications. Delivery is not guaranteed while Chrome is fully closed. Local records contain the account, message and squad IDs and preview setting for notification clicks; they are cleared when notifications close or become invalid. Displayed text may remain in operating-system notification history, whose copies Palside cannot guarantee to erase.
Squad retention is 1 / 7 / 30 days or Forever, defaulting to Forever. Images last at most 30 days after sending, then show “Image expired”. Local content cache is limited to 300 MiB. Expired content becomes inaccessible immediately; related metadata is cleared within 7 days. Report evidence lasts at most 90 days while unresolved or 30 days after closure; report and case records are deleted one year after closure. Operator audit records last one year and service logs 7 days. There are no server backups.
Account deletion retains only the public key and deletion time, removes reporter links, wallet bindings and local account settings, and reconciles pending chain orders before removing account links and retaining only amounts and hashes. The same phrase can register again without restoring old account data. Bans tied to the public key still apply.
Retained reports have no link to the deleted reporter. Payment and claim records with cleared account associations have no link to the original account. Public chain addresses and transactions still exist.
Payment safety
Before signing, the device checks the chain, token, recipient, amount and approval scope. Wallet does not offer unlimited approvals, Permit, arbitrary transactions or ETH payments. This does not make transactions reversible: follow Wallet when a result is unknown.
Report a vulnerability
Report security issues privately to palside@pm.me. Do not include a recovery phrase, private key, local password or device token. Public source code is not the same as an independent audit; deployment and review status are in PALS.