Privacy Policy

Version: draft-0.4

Effective date: TBD

Last updated: 2026-09-18

1. Who we are

Prism is a consumer AI companion app operated by Multisys Technologies Corporation (“we,” “us,” or “Multisys”).

If you have questions about this Policy or your personal data, email [email protected].

2. Scope

This Policy explains how we collect, use, store, share, and delete personal data when you use:

• the Prism mobile app;
• Prism customer APIs and related web surfaces that create or manage a Prism account.

Admin portal staff accounts are a separate identity space. Staff privacy tools live under the admin Privacy center; this in-app Policy is written for end users (customers).

We process personal data in line with the Philippine Data Privacy Act of 2012 (RA 10173) and its implementing rules, and other laws that apply. Where we operate in other countries later, we may update this Policy (other markets: TBD).

3. Data we collect

3.1 Account and authentication

Depending on how you sign in, we may process:

We store account fields such as email, display name, account status, plan, and login-related timestamps. Federated logins keep a provider row (provider, providerUid, providerEmail).

Tokens: We issue short-lived access tokens and rotating refresh credentials. Refresh records may include IP address and user-agent for security.

3.2 Chat, projects, and AI content

When you use Prism chat, agents, projects, or image tools:

• Your prompts, conversation history, and related usage metadata are sent to our platform and to the configured AI provider so we can generate replies and images.
• We persist conversations, chat messages, and usage (including credit usage) in our databases.

Configured providers may include our AI Gateway (prismai.ph / Multisys-operated, legal naming TBD) and/or OpenRouter (including image generation when that path is enabled). Exact provider for a turn depends on configuration.

Provider training: Whether prompts or completions are used by upstream providers to train models is TBD (depends on Gateway / OpenRouter contracts). We will update this section once DPAs confirm the rule. Until then, do not assume “never used for training.”

3.3 Web search (when enabled)

If web search runs for a turn, the search query (and result snippets used in that turn) are sent to our search provider. Live provider today: Tavily (when configured). You may be able to control web search via product settings when that toggle ships.

3.4 Entitlements, credits, and payments

We store plan / entitlement state (for example trial, free, or paid tiers), credit balances, feature caps (such as chat or image limits), and related grant records.

Payments: Live payment processors are not wired in production as of this draft (checkout may be mock). UI may mention wallets such as Maya/GCash; Apple/Google In-App Purchase is not in the mobile app yet. When real payments ship, we will name the processor(s) and update this Policy.

3.5 Product analytics (part of the service)

On mobile, product analytics are used to operate, secure, and improve Prism. They are not optional and are not offered as an opt-in / opt-out product feature under this Policy.

• Implemented with PostHog (default host in the US: https://us.i.posthog.com).
• After login we identify with an internal customer id only, not your email as the analytics id.
• Session replay is off.
• We aim to block chat content and other PII from analytics properties; geo-IP enrichment is disabled.

Using Prism includes this processing as described here. Analytics help us understand feature use, reliability, crashes/errors at a product level, and overall product quality, without sending chat message bodies as analytics properties when our filters work as intended.

PostHog runs on the mobile app; it is not part of the Prism API/admin codebase.

Other crash/error tools (for example Sentry): TBD.

3.6 Device permissions and local data

With your OS permission, Prism may access:

• Photos / Camera: attach images to chat or ask about an image; save generated images to your library when you choose.
• Notifications: product/push preferences in Settings; OS notification permission may be requested when “notify when AI finishes” (or similar) ships.

We do not request microphone permission in the current mobile build.

On-device storage includes session tokens and app preferences. Chat history is server-backed (not a durable offline archive). Attachments for a turn are handled in memory unless you save to the gallery.

3.7 Logs and security records

We keep structured server logs and security-related records (for example login attempts, email delivery logs, audit records). We aim to avoid secrets in logs. Retention windows used on the admin side today include examples such as: refresh tokens cleaned up after expiry windows; login attempts ~90 days; email logs ~90 days; longer audit anonymization horizons. Customer-facing retention for chat after deletion is TBD.

4. Why we use your data

We do not sell your personal data.

5. Who we share data with (subprocessors)

We use service providers (“subprocessors”) to run Prism. As of this draft we can name:

Providers only receive what is needed for their function. Upstream AI and search providers process content you submit for that feature.

6. Where data is stored

Infrastructure includes PostgreSQL, Valkey, and object storage.

Production region / Philippine data residency: TBD (infra). Product analytics events are sent to PostHog’s US host by default.

We will update this section when production regions are locked.

7. How long we keep data

• Account and chat content: kept while your account is active and as needed to provide the service.
• After deletion: Admin tooling supports a deletion request with a 30-day grace period before hard-delete for admin accounts. Customer-app hard-delete scope and chat retention after customer deletion are TBD.
• Security / ops logs: see examples in §3.7; final customer schedule is TBD.
• Analytics: governed by PostHog retention and our operational needs; we will update this when a customer schedule is locked.

8. Your choices and rights

8.1 In-app controls (mobile today)

• Open Terms / Privacy from login footer and Settings → About once links are wired (stubs today).
• Manage notification preferences in Settings.
• Log out (clears session UI state).

Product analytics are not controlled by an in-app opt-out under this Policy. They are part of how Prism works when analytics is configured.

8.2 Access, correction, deletion, portability (DSAR)

Under the Data Privacy Act you may have rights to be informed, object, access, correct, erase, and data portability, subject to legal limits.

Launch expectation (product): before public beta, customers need either in-product export/delete or a clear “how to request” path with an SLA. Until that ships, email [email protected] and we will process the request under applicable privacy rules.

We may need to verify your identity before fulfilling a request. Some data may be retained where law requires (for example fraud, disputes, legal holds).

8.3 Marketing / product updates

Push / product-update toggles remain user-controlled in Settings. Product analytics are part of how Prism works and are not offered as an optional / opt-out feature.

9. Children

Prism is aimed at adults. Proposed minimum age: 18+ (or 13+ with parental consent if we ever allow minors). No age gate in the app today. Minimum age remains subject to company confirmation before public launch. We do not knowingly collect personal data from children below the locked minimum age. If you believe a child has used Prism, contact us to delete the account.

10. Security

We use industry-standard controls appropriate to an online service (encrypted transport, tokenized sessions, access controls, logging). No method of transmission or storage is 100% secure. Please protect your device and sign-out on shared devices.

11. International transfers

Some providers (for example PostHog US, global AI/search vendors) may process data outside the Philippines. Where required, we will use appropriate contractual and organizational safeguards. Details: TBD once regions and contracts are confirmed.

12. Changes to this Policy

We may update this Policy as Prism changes. We will revise the “Last updated” date and, for material changes, provide additional notice in-app or by email when appropriate. Continued use after the effective date means you acknowledge the updated Policy.

13. Contact