Privacy, in plain sight.
A clear view of the information behind a document view, and how we handle it.
Effective November 6, 20261. Who we are
AnyShare is a document sharing service operated by Anysoft LLC. This notice describes how we handle information when you use our website, application, document viewer, and assistant connections. The sharing organization decides which files to share, with whom, and which available viewer checks to require. Anysoft LLC operates the application and processes information needed to provide it.
For privacy questions and requests to access, correct, or delete your information, email hello@anysoft.ai. You can also write to Anysoft LLC, 3293 Sleeping Meadow Way, San Ramon, CA 94582, USA.
Anysoft LLC is responsible for deciding how account administration, billing, support, security, and its own product measurement use personal information. For files and viewer information processed on a sharing organization’s instructions, that organization is responsible for its purposes, lawful basis, and notices to viewers; Anysoft provides the service on its behalf. Contact us if you need help identifying the organization responsible for a shared document.
2. Information the service handles
| INFORMATION | WHY IT IS USED |
|---|---|
| AI assistant connections | When you connect an assistant, AnyShare stores the approved organization, permissions, connection dates and hashed access credentials. The assistant can receive document metadata, share links and, with your analytics permission, aggregate engagement. Session details are returned when requested; recorded viewer emails and verification status require an explicit viewer identity request. Files you choose to upload are stored in your organization. Temporary file transfer URLs are used to transfer the original file and are not sent to product analytics. Your assistant provider handles information it receives under its own privacy terms. You can revoke a connection in Settings; revocation stops future access but does not erase information already sent to the assistant. |
| Feedback and support messages | Messages you submit, your account name and email, organization, and the workspace page you submitted from are stored in Supabase to investigate issues, respond, and improve AnyShare. Feedback text is not sent to product analytics or error tracking. |
| Account details | Authentication identifiers, email, and profile details supplied through Clerk are used to sign you in and associate you with your organizations. Membership records include your role, name, email, and join date. |
| Organization and invitation details | Organization names, membership roles, invited email addresses, invitation expiry dates, and trial start and end dates support team access and the 7-day trial. Invitation tokens are stored as hashes. Stripe processes subscription payments and stores payment details. AnyShare stores Stripe customer and subscription identifiers, plan status, billing dates, and payment outcomes; it does not receive or store your full card number or security code. |
| Documents and rooms | Uploaded files, converted previews, titles, versions, folders, share links, and access settings are used to store, organize, and deliver the content you choose to share. |
| Viewer details | Where required by a link, viewer email and its verification status are used to check access and identify visits. A captured email is not automatically a verified identity. |
| Viewing sessions | Session identifiers, visit times, document version, pages visited, completion, and active milliseconds displayed as seconds are used to provide document engagement analytics. When available, we also store approximate city and country derived by our hosting provider from the viewer’s IP address. We do not store the raw IP address or precise coordinates in viewing sessions. Location may reflect a VPN or proxy and may be unavailable for some visits. |
| Technical information | Browser or device information and service request logs help operate the viewer and investigate technical problems. PostHog receives sanitized error categories, application operations, route templates, software release identifiers, and known code locations, with an organization identifier where available. Error reports exclude raw messages, request contents, document contents, private links, and payment card details. Optional browser error reporting honors the browser analytics choice below; server reliability reporting is separate. Infrastructure providers may process IP addresses and other connection information to deliver the service. |
| Product usage | Unless you opt out or your browser sends Do Not Track or Global Privacy Control, selected website visits, trial buttons, pricing selections, sign-in and signup steps, account-setting categories, organization, upload, sharing, and team actions help us understand adoption and improve the service. Events use random browser journey identifiers, account and organization identifiers, route categories, file types, and counts. A browser journey can be associated with your account after sign-in. Public viewers use a separate random journey identifier to measure access steps, page rendering, qualified page visits, engagement milestones, and download requests. These events include opaque document, session, link, and organization identifiers, but not the recipient’s email. Document contents, names, email addresses, passwords, verification codes, access tokens, full URLs, and page-by-page viewing time are excluded from these events. We do not record your screen or automatically capture form contents or arbitrary button text. Server-side service operations, billing outcomes, and sanitized reliability events are separate from this browser choice and may still be recorded to operate and improve the service. Failed uploads and conversions may send operational reports to our support team with a failure category, file type and size, timing, and investigation identifiers. These reports exclude document contents, filenames, and signed URLs. |
3. What organization members can see
Members of the sharing organization can access its documents, rooms, links, and analytics, including visit counts, unique viewers, session details, pages visited, completion, active time, and approximate city and country when available. When a viewer provides an email, members can see it and whether it was verified. Anonymous viewing, where permitted, is labeled as anonymous. Members can export available analytics as a CSV. Viewers should contact the person or organization that shared a document about that organization’s use of their information.
Organization members can see the team directory. Owners and admins can see pending invitations and manage access within their role. Accepting an invitation requires the matching verified account email. Removing a member ends their organization access but does not recall any files or analytics they previously downloaded.
Active time is recorded while a page is in the foreground, using periodic activity updates. Hidden tabs and idle viewers pause timing. This measures a limited engagement signal, not proof that you read, understood, or agreed to content. The application does not record your screen or use advertising trackers for these insights.
4. Cookies and access
The service uses essential authentication and viewer-session cookies to keep team members signed in, remember the selected organization, and remember completed viewer access checks. Organization membership is checked on the server; selecting an organization does not grant access. Viewer-session cookies are set with HttpOnly protection and expire. Disabling essential cookies may prevent sign-in or protected document viewing. AnyShare does not include an advertising cookie or cross-site advertising analytics system.
We receive information from you, your organization, people who share or view documents, connected assistants you authorize, and the service providers listed below. We do not sell personal information or use it for cross-context behavioral advertising.
Optional website usage measurement uses a random identifier in tab session storage. It lasts for that tab session and resets on observed sign-out or account switching. A browser analytics preference is stored locally when you change it and remains until you change it again or clear browser data. Optional browser and viewer measurement are on by default. Existing saved opt-outs are preserved. You can turn optional measurement off using the control below. Clearing browser data removes the saved preference and restores the default, subject to Do Not Track and Global Privacy Control. Turning measurement off stops future optional collection; it does not erase events already collected. Optional viewer measurement uses a separate signed, HttpOnly cookie that expires after one day. Its journey and event-delivery records in AnyShare are scheduled for removal seven days after expiry; cleanup runs when the event-delivery worker runs. This does not remove the sharing organization’s document engagement records or events already delivered to PostHog. The browser preference, Do Not Track, and Global Privacy Control disable optional browser and viewer measurement; document engagement provided to the sharing organization, including approximate city and country, continues. That organization is responsible for its own required notices and permissions for engagement measurement.
Your browser analytics preference is off. Analytics are on by default; a saved opt-out keeps them off. You can change this preference here at any time. Global Privacy Control and Do Not Track disable optional collection even when this preference is on. Account access and the document engagement reports provided to sharing organizations are unaffected.
When you choose to apply a referral, we store its code and the time of your choice in a signed, HttpOnly cookie for up to 30 days to credit the organization that referred you. You can continue without applying it or remove the saved referral below. When you sign up, we retain the attribution, account and organization identifiers, a keyed hash of your verified email for duplicate prevention, and payment/reward identifiers needed to administer the program. The referring organization sees signup and reward status, but not your email, organization name, or payment details. Referral codes and email hashes are excluded from product analytics.
Removing this browser cookie does not erase referral or payment records already created when you signed up.
5. Service providers
The configured service uses providers to perform specific functions. Providers receive the information needed for their function. Some also handle their own account, fraud-prevention, and legal records under their privacy terms. An assistant provider receives the information you authorize through its connection.
- Clerk: account authentication and profile services.
- Supabase: application database and private document storage.
- Vercel: application hosting and request delivery.
- PostHog: selected product usage events when enabled. Our own browser instrumentation sends allowlisted events through AnyShare before forwarding them to PostHog. We do not load PostHog’s browser script or enable session recording. Customer-facing document engagement remains in our application database.
- Resend: viewer verification emails and organization invitations. Signed delivery-status callbacks help us identify failed or delayed mail. We forward delivery categories and random correlation identifiers to product analytics, excluding email addresses and message bodies.
- Stripe handles checkout, subscription billing, and payment management. Render hosts the private document conversion worker and Gotenberg service that prepare Office previews. The worker uses private storage and processes the files needed for conversion.
6. Retention, deletion, and your choices
Content and related engagement records are retained to provide the organization and sharing features. Revoking a link stops future access through that link; it does not itself delete the underlying document, previous analytics, downloaded copies, or provider backups.
Deleting a document removes its document and version records, direct share links, data-room attachments, and associated viewing sessions and page engagement from the application database. Original files and converted previews are queued for removal from private storage. That cleanup runs in the background and retries failures; it is not immediate. Deletion remains available when an organization’s trial or subscription has ended.
Removing a team member or deleting a sign-in account does not automatically delete the organization’s documents and engagement records. Document deletion also does not recall copies already downloaded, exported, or sent to an assistant, or automatically erase separate product analytics, service-provider records, or database backups.
Supabase makes daily backups of our database. Its Pro plan provides access to the last seven days of daily backups. These backups can contain previously deleted database records until the backups expire; expiry is managed by Supabase. Original files and converted previews in private storage are not included in these database backups.
Until the automatic schedule below takes effect, we keep workspace content and engagement to provide the sharing service unless an authorized person deletes it or requests closure. Account and support information is kept while needed to provide access, resolve a request, or meet a specific legal or security obligation. Separate provider records follow the provider’s applicable retention and deletion processes. You can request deletion now; you do not need to wait for automatic expiration. We assess the request across the application and relevant providers and explain any retained exception. Backup recovery windows do not guarantee physical erasure on a precise date.
We have selected the following retention schedule for rollout. Automatic expiration under this schedule is not yet enabled; we will announce its effective date before applying it to existing workspaces.
- Workspace documents and previews: while access remains active, then 90 days after usable trial or paid access ends. Existing inactive workspaces will receive a new 90-day window from the effective date. Owners will receive notices at least 30 and 7 days before deletion. Reactivation cancels pending expiration; delayed notices or unresolved billing postpone it.
- Detailed viewer identity and engagement: 12 months from the visit, or earlier when the related document is deleted.
- Our operational delivery and diagnostic payloads: 90 days, subject to a documented, limited investigation hold. Minimal duplicate-event prevention records may remain separately.
- Support, feedback and privacy-request records: 12 months after resolution, unless a documented legal requirement needs longer retention.
- Billing and referral payment records: only as needed for accounting, disputes and applicable legal obligations. We determine retention by the record’s purpose, applicable tax or claims period, and any unresolved dispute or legal hold. A limited retained financial record does not authorize retaining unrelated documents or viewer data.
We will verify identity and authority before fulfilling deletion requests. Our internal target is 28 days from receipt, subject to any earlier applicable deadline. Deleting an individual account does not authorize deleting a shared workspace. An owner must arrange ownership transfer or explicitly request workspace closure. We will explain any necessary retained records or unresolved provider handling.
Depending on applicable law, you may request access, correction, deletion, a portable copy, restriction, or objection to processing. Where we rely on consent, you may withdraw it without affecting the lawfulness of earlier processing. You can complain to your local data protection authority and contact us to review a refused request. We will explain a refusal or extension and any available appeal route. Send account and privacy requests to hello@anysoft.ai. Requests about a sharing organization’s collection of viewer information should first be directed to that organization.
We do not discriminate against you for exercising applicable privacy rights. An authorized agent may contact us on your behalf; we may verify the agent’s authority and your identity. Please avoid sending identity documents or sensitive information unless we explain why they are needed. The service is intended for adults and organizations, not children. Contact us if you believe a child has provided personal information so we can investigate and take appropriate action.
7. Security and permitted use
Documents are held in private storage and served after the applicable access checks. Organization members can choose available email verification, passwords, allowlists, expiry, downloads, and watermark controls. No displayed content can be guaranteed against screenshots or copying. Learn more on our security page.
8. Purposes and legal bases
Where a legal basis is required, we use information needed to provide a service you contract for, including account access and subscriptions. For an organization’s staff contacts and service administration, we rely on our legitimate interests in operating the requested business service. Security, fraud prevention, support, and limited service reliability measurement serve those interests, subject to your rights and reasonable expectations. Optional browser and viewer product measurement helps us understand adoption and improve the service. It is enabled by default and follows the browser opt-out, Do Not Track, and Global Privacy Control settings described above. Required financial records and responses to lawful demands rely on applicable legal obligations. Providing necessary account or access-check information is required to use the relevant feature; optional analytics are not.
Our use of information supplied by a sharing organization follows its instructions. That organization must identify its own basis for collecting viewer information and provide any required notice or consent mechanism. The browser analytics control above governs AnyShare’s optional product measurement, not that organization’s processing.
9. International processing
Anysoft LLC is based in the United States. AnyShare is a US-focused service that may also be accessed from other countries. It uses US-hosted application, database, document-storage, conversion, email, and analytics infrastructure. Provider support and subprocessors may operate in additional countries. Using AnyShare from another country can therefore involve an international transfer; it is not an EU-only or UK-only storage service.
Privacy laws in the United States may differ from those where you live. If your organization requires a data-processing agreement, specific transfer safeguards, or a particular storage location, contact hello@anysoft.ai before uploading information subject to those requirements. Contact the same address with questions about where your information is processed and the arrangements applicable to it. This notice does not represent that every jurisdiction-specific transfer arrangement is in place.
10. Changes and contact
We will update the date above when this notice changes and provide additional notice of material changes where required. The retention schedule above will have a separately announced effective date. Questions or privacy requests can be sent to hello@anysoft.ai.