RACCAM Privacy Policy

RACCAM is a match-recording app for iPhone, with a web service that handles signing in and connecting the streaming destinations you choose. This policy describes the information that web service receives, what it is used for, and how long it is kept. It covers the RACCAM website and the RACCAM backend that the app talks to.

Recordings, highlights and photos you capture are produced on your device. RACCAM does not upload your recordings to our servers.

Your RACCAM account. You sign in with an email address and password, or with Google. Either way RACCAM receives the email address associated with that sign-in and creates an account record for you.

If you connect a Facebook Page. Connecting Facebook is optional, and only happens if you choose to stream to a Page. When you do, RACCAM asks Facebook for:

• your Facebook account’s identifier and name;
• the Facebook Pages Facebook reports you can act on — each Page’s identifier, its name, the tasks you are permitted to perform on it, and an access token for that Page;
• an access token for your Facebook account, which RACCAM uses to make the requests above on your behalf.

Streaming records. When you go live, RACCAM records which destination you selected and the identifier of the live video it created, so it can end the broadcast and show you the session afterwards.

Purchases. If you buy a paid feature, RACCAM receives confirmation of the purchase from Apple. RACCAM does not receive your payment card details.

To sign you in; to show you which Facebook Pages you can stream to; to start and end a live broadcast on the destination you chose; to keep a paid feature available to the account that bought it; and to operate and troubleshoot the service.

RACCAM does not use this information to build advertising profiles, and does not sell it.

An access token is the credential that lets RACCAM act on your behalf at a streaming provider. RACCAM stores the tokens it needs encrypted, using a managed key held by our key-management provider, and decrypts them only on the server at the moment a request is made. Tokens are never sent to your browser or to the iPhone app, and are never written to our diagnostic logs.

RACCAM’s website sets cookies for authentication and sign-in only: the session cookies that keep you signed in, and one short-lived cookie (raccam_oauth_actor) used to complete a streaming-account connection you have started.

There are no advertising or analytics cookies, and RACCAM’s website contains no analytics or advertising trackers, tag managers, pixels or third-party measurement scripts.

Providers you connect. When you stream to a Facebook Page, RACCAM sends Facebook the requests needed to create and end that broadcast. Facebook’s own terms and privacy policy govern what Facebook does with it.

Infrastructure we run on. RACCAM uses third-party services to host its database and to hold the encryption key described above. They process this information in order to provide that infrastructure to RACCAM.

Apple. The iPhone app is distributed through the App Store, and purchases are processed by Apple.

Your account record and your streaming history are kept while your account exists.

Disconnecting a streaming account deletes what RACCAM stored for it — the stored connection record, including the encrypted access tokens for that provider, is removed. This takes effect in RACCAM immediately.

Disconnecting inside RACCAM does not, by itself, withdraw the permission you granted at Facebook. To remove RACCAM’s access from Facebook’s side, remove the app in your Facebook account settings.

This policy does not state a fixed retention period for account records, because RACCAM does not currently operate one.

Connecting a streaming provider is optional, and you can disconnect it at any time in RACCAM. You can also withdraw RACCAM’s access from your Facebook account settings, as described above. You can choose not to connect Facebook at all and still record, keep highlights and review matches on your device.

Access tokens are encrypted at rest and handled only by server-side code. Administrative access to RACCAM’s internal tooling is restricted to authorised operators. No service can promise perfect security, and this policy does not make that promise.

If this policy changes, the updated version will be published at this address and the “Last updated” date above will change. Material changes will be described here rather than applied silently.

RACCAM does not yet publish a dedicated contact address for privacy questions on this site. That is a known gap, and it is recorded as an open item in RACCAM’s implementation record rather than filled in here with an address that would not reach anyone.