Skip to content
Billion

Billion · Private pilot

Privacy policy

Draft updated

Who is responsible

This notice covers the Billion presentation website and the invited Billion workspace. The operator below manages account access and the service. A business or agency using Billion also decides what client and team content it puts into its workspace.

Billion LLCOperator address awaiting confirmationKosovoContact [email protected].

Information used by Billion

  • Account access: the identifier returned by your chosen sign-in provider, or your invited email account and a salted password hash. Provider email information may be checked to admit an invited account. Billion stores session hashes, expiry and revocation records, together with temporary sign-in proofs.
  • Workspace content: organization and brand details, descriptions, colours, logos, team access, invitations, post captions, images, videos, dates, versions, review notes and the identity of the person taking an action.
  • Connected accounts: selected Facebook Page or professional Instagram account identifiers, display details, granted permissions, token expiry and encrypted access tokens. These are separate from signing in to Billion.
  • AI and publishing records: prompts, the saved brand context used in a request, generated results, usage and authorization records, publishing instructions and provider receipts. Failed or uncertain requests can retain a recovery record to prevent duplicate actions.
  • Service requests: your browser sends network and request information to the server delivering a page or file. Contacting the operator also provides the details you include in that message.

Why this information is used

Billion uses this information to sign you in, enforce organization and brand permissions, keep your saved work, support team review and recover interrupted requests. Connected-account credentials support the publishing actions you explicitly authorize. AI requests use the prompt and saved brand context to create material for your review.

The operator must confirm the applicable legal bases and any additional processing purposes before this notice is published as a final policy.

You remain responsible for having permission to put someone else’s personal information, photographs or other content into your workspace. Avoid submitting information the service does not need.

Who receives information

Authorized members of your organization can access content according to their brand permissions. The hosting and storage services selected by the operator process the information needed to run the service.

Using a sign-in provider sends the sign-in request to Google, Meta or Microsoft, according to the option you select. When live AI is enabled and you choose generation, the relevant prompt and saved brand context are sent to the configured AI provider; the implemented text and image adapter uses OpenAI. When you explicitly publish or schedule supported content, the selected caption and media are sent to Meta. A publishing provider may temporarily retrieve the exact media needed for that request through a restricted link.

Free local simulation does not contact AI or publishing providers. A provider’s own terms and privacy notice apply to its processing.

Hosting locations, service recipients and any international-transfer arrangements are awaiting operator confirmation. This draft does not state that information stays in a particular country.

Cookies and browser storage

The presentation pages do not include advertising pixels or analytics tags. Their sample calendar runs in memory. The signed-in app uses essential session and temporary sign-in cookies. It can store your selected brand preference in browser storage; provider access tokens are not put there. Hosting infrastructure may have its own necessary request handling, described in the confirmed hosting details above.

Keeping and protecting information

Account sessions expire or can be revoked. Signing out ends the current session; it does not delete saved workspace content. Access controls separate organizations and brands, and selected Meta credentials are encrypted in storage. These measures cannot remove every security risk.

The operator must confirm retention periods or criteria, including backups, recovery receipts and security or financial records, before final publication. There is no automatic account-erasure process in the current pilot.

Your choices and requests

You can edit content where your role allows, sign out and disconnect a selected social account. Disconnecting removes that brand’s local credentials and pending authorization; it does not erase your Billion account or posts, or remove the app authorization from Meta.

Depending on applicable law, you may ask for access, correction, deletion, restriction or portability, object to particular processing, or withdraw consent where consent is the basis. Contact [email protected] so the operator can verify the request and explain any limits. See Data deletion for the current manual process.

Where applicable, you can also complain to the data protection authority competent for your situation.

Changes to this notice

The date above identifies this version. The operator should update this notice when the service’s data uses or providers change and give any additional notice required by applicable law.