KeiApps · Privacy

Your information, explained

Privacy policy

How Kei handles information in Socials and the services that explicitly link to this policy.

Effective and last updated: 13 November 2026 · Operated by Kei / kei.kyoto

Scope. This policy covers Kei Socials, a private publishing workspace for its owner, and this public policy website. Another Kei app is covered only when it expressly links to this policy and its data practices are described here. Portray, Northlight and Family Hub have separate policies; this policy does not replace them.

1. Information handled by Socials

Socials is an owner-only tool, not a public social network or an open registration service. Connecting a platform gives Socials only the access granted through that platform’s authorization or a credential supplied by the owner.

2. How information is used and shared

Information is used to authenticate the owner, manage approved connections, organize drafts and media, publish or schedule reviewed content, verify delivery, display requested metrics, troubleshoot failures, and protect the service. Saving a draft alone does not authorize publication.

Content and the information required to deliver it are sent to the selected platform when the owner authorizes publishing or scheduling. The platform determines who can see a published item according to the account and post settings. Some platforms fetch media through a time-limited link to a selected private file.

Socials uses Cloudflare for hosting, access control, databases and file storage, and Notion for the owner’s connected workspace of drafts, campaigns and media metadata. Connected social platforms process API requests and published content under their own policies. Service providers may process data in countries outside the owner’s country.

We do not sell Socials data, use it for advertising targeting, or supply connected-platform data to train general-purpose AI models. Socials does not automatically send drafts or credentials to an AI provider. If the owner chooses to export content or use a separate assistant or integration, that chosen tool’s data practices also apply. Information may be disclosed where legally required or necessary to address security incidents or protect rights.

3. Connected platforms

Pinterest

When connected, Socials uses the authorized account’s identity, boards and Pins to select destinations and create reviewed image or video Pins. The intended use is the owner’s own account. Socials does not request access to other Pinners’ private data or manage advertising campaigns. API availability and publishing visibility depend on Pinterest’s approved access tier.

Google and YouTube

When authorized, Socials uses Google account and YouTube channel information to identify the chosen channel, upload reviewed videos, and check their processing or publication state. A Google Business Profile connection, if separately enabled and approved, uses the owner’s managed business locations to publish reviewed updates. These are separate authorizations.

Socials’ use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google API data is used only for the authorized features described here, not for advertising or general-purpose AI training.

Other platforms

Connections such as X, Bluesky, Instagram, Facebook Pages, Threads, LinkedIn, Mastodon, Discord and Telegram use the identity, destinations, credentials and publishing information needed for their enabled features. A listed integration is not a claim that an account is connected or a platform has approved the app. Optional analytics access is distinct from permission to publish.

4. Storage, security and retention

The private dashboard requires authentication and is restricted to its configured owner. Connections are stored with application-level encryption on the server. Media is held in private storage. Credentials are excluded from drafts and normal workspace exports. HTTPS protects information in transit; no system can guarantee absolute security.

Credentials are retained while the connection is needed. Drafts, media, workspace metadata and delivery records remain until removed by the owner or through an administrative deletion request; Socials does not currently apply a universal automatic deletion period to that content. Operational and backup retention can differ between service providers. Records may be retained when needed for security, resolving a delivery dispute, or applicable legal obligations.

This policy website has no application database, advertising tags or analytics scripts. Its hosting service can process standard network and security information such as an IP address, request time and browser details. Authentication and connected-provider sites may use cookies for sign-in or security.

5. Access, disconnection and deletion

The owner can review and edit workspace content and use the available export features. To stop a connection, cancel its queued posts and resolve uncertain delivery results, then disconnect it in Socials. Disconnection deletes the credential from Socials’ active connection store; it does not delete existing drafts, delivery records or content already published on the platform.

Access can also be revoked in the provider’s account settings. Google access can be revoked through Google Account connections. Published posts or videos must be removed through the relevant platform. For deletion of retained Socials media or records, or to request access or correction, contact us below. We may verify the request and explain any records that must be retained. Rights available under applicable privacy law are not limited by these instructions.

6. Children and policy changes

Socials is a private administrative tool and is not offered to children. We do not knowingly solicit personal information from children. Contact us if information has been submitted in error.

We will update this page and its revision date when these practices change. Material new uses or permissions will be explained before enabling them where required. Other Kei apps keep their own policies unless explicitly included here.

7. Contact

For privacy questions, access requests or deletion requests, email hello@kei.kyoto and identify the app concerned. Please do not include passwords, access tokens or verification codes.

Kei · kei.kyoto