Privacy Policy
Last updated: 9 November 2026
This Privacy Policy explains what information 8Bit Technologies ("8Bit", "we", "us") handles, why, and what choices you have. It covers our public website at 8bittechnologies.com and Orbit, the work-management application that our staff and our clients use to plan, review and approve content, including Orbit's connection to Facebook and Instagram through Meta. It also covers the Orbit mobile app for Android, which our clients use to follow their work and respond to approval requests.
1. Who we are
8Bit Technologies, BE 61, Salt Lake Rd, BE Block, Sector 1, Kolkata, Bidhannagar, West Bengal 700064.
Email: [email protected] · Phone: 092331 11777
2. Information we handle
Website visitors
- Technical information that web servers record by default: IP address, browser and device type, the pages requested, and the date and time. We use it to operate and secure the website.
- Anything you choose to send us, for example your name, email address and message if you email or phone us.
Orbit accounts
- Name, email address, role, account status and time zone for staff and client users. Passwords are stored only as salted hashes, never in readable form.
- Sign-in session data, and a record of important account and work actions (who did what, and when).
Orbit mobile app
The mobile app is for existing client users. Accounts are created by 8Bit; you cannot create an account in the app. When you use it:
- Sign-in. You sign in with your Orbit email address and password. The app receives a sign-in token, which it keeps in your phone's secure storage (backed by the Android Keystore) for up to 30 days. It is removed when you sign out, when your password is changed, or when your access ends. The app also remembers which business you last selected, in the same secure storage.
- Approval notifications. If you are an approver and allow notifications, the app registers your phone so that we can alert you when a creative needs your approval. We then store a push notification token issued for your phone by Expo, an identifier the app generates for its installation, the platform (Android), the phone model name and the app version. A notification contains only a generic message ("Approval needed") and technical identifiers used to open the right approval; it never contains the creative itself. We also keep a short record of each notification sent (which approval, to which registration, and whether it was accepted) so that no alert is sent twice.
- What the app shows. Your clients' work, approvals, comments, schedule, activity and package details, and the creative images and videos for approval, are fetched from Orbit over an encrypted (HTTPS) connection when you open them. Pictures are kept only in the app's memory while it is in use, and unsent comment drafts are not saved to your phone's storage.
- Crash and error diagnostics (version 1.0.2 of the Android app and later). To find and fix crashes and technical problems, these versions of the app use Firebase Crashlytics, a diagnostic service provided by Google. When the app crashes, or runs into a technical error such as a failed notification set-up or a failed app update, it can send a report to Crashlytics. A report can contain: the type of crash or error and the technical trace of where it happened in the app; the phone's make, model, Android version and general device state at that moment (for example available memory and whether the app was in the foreground); the app version and build; a short technical code that we define for the step that failed (for example, which stage of notification set-up); and a Firebase installation identifier, a random identifier that Firebase generates for this installation of the app and that is not your name, email address or Orbit account. We do not attach your name, email address, user ID, sign-in token, push notification token, or any client or work content to these reports, and we do not put the text of error messages or the content of requests into them. We use this information only to keep the app stable and reliable and to troubleshoot problems. The app does not currently offer a setting to turn crash reporting off.
- App updates (version 1.0.2 of the Android app and later). These versions can receive small updates to the app's code from Expo's update service, without a new download from Google Play. To check for an update, the app contacts that service and sends the app version, the update channel, the platform (Android) and a technical identifier of the update it currently runs, together with the information any internet request carries, such as your IP address. Expo handles this under its own terms and privacy policy.
- Saving approved creatives (version 1.1.0 of the Android app and later). At your request, the app downloads an approved image or video from Orbit and saves it to your phone's photo/video library. The app only asks for permission to add media; it never reads or accesses your existing photos or videos. Saved files stay on your phone and are managed by you.
- Report PDFs (version 1.1.0 of the Android app and later). At your request, the app downloads your business's monthly report as a PDF to temporary storage on your phone so you can open or share it using your phone's share options. Nothing is uploaded anywhere new.
- Connection type (version 1.1.0 of the Android app and later). Before a large download, the app checks on your phone whether you're on Wi-Fi or mobile data, to warn you about data usage. This information is not sent to us.
- What the app does not use. It does not use advertising identifiers, location, contacts, the microphone or advertising or behavioural analytics services, and it does not set cookies. In version 1.1.0 of the Android app and later, the camera is not used either, and the app does not read or access your existing photos or videos — it can only add media you choose to save, as described above. The only diagnostic service it uses is the crash and error reporting described above, and only in the versions stated there.
Client and work information
- Client business names and codes, the people linked to each client, and the work being done for them.
- Social media drafts: captions, hashtags, scheduling dates, creative files (images and video), approval requests and decisions, and comments.
Google Drive and Google Sheets
Orbit can read, read-only, the Google Drive folders and the content-planning spreadsheet that have been shared with a Google service account we operate. It reads file names, folder structure, file contents needed to import creative material, and spreadsheet rows. Orbit does not create, change or delete anything in Google Drive or Sheets, and it stores references (such as file names and IDs) and the files that are imported into a work item.
Facebook and Instagram (Meta)
An authorised 8Bit administrator can connect one 8Bit agency Meta account to Orbit by signing in with Facebook. When this is done, Orbit receives and stores:
- the name and Meta ID of the Facebook account that authorised the connection, and which permissions were granted;
- the Facebook Pages that the account is able to manage: Page ID, Page name, and the tasks the account may perform on each Page;
- for each Page, an access token that lets Orbit act on that Page;
- the Instagram professional account linked to a Page, if there is one: its ID and username;
- which Orbit client each Page belongs to (a mapping chosen by an 8Bit administrator); and
- when content is published through the integration, the identifiers and status that Meta returns for that post.
The integration does not read private messages, and it does not collect the personal information of a Page's followers, fans, commenters or customers. Client users never sign in to Meta through Orbit.
3. Why we use Meta data
We use the Meta permissions that are granted to Orbit only for the following purposes:
- pages_show_list and business_management: to list the Facebook Pages that 8Bit's account manages, including Pages that are managed through a Meta Business portfolio, so that each Page can be matched to the right client.
- pages_read_engagement: to read the basic Page details Meta requires in order to identify a Page and publish to it.
- instagram_basic: to identify the Instagram professional account linked to a Page (its ID and username).
- pages_manage_posts and instagram_content_publish: to publish to a client's Facebook Page and linked Instagram account content that has been prepared, reviewed and approved in Orbit. Content is published only to the Page and Instagram account that an administrator has mapped to that client.
We use information we receive from Meta only to provide these features. We do not sell it, we do not use it for advertising or for profiling people, and we do not give it to data brokers. Our use of Meta data follows Meta's Platform Terms.
4. Other ways we use information
- To run Orbit: sign-in, roles and permissions, work planning, approvals, comments and notifications, including alerts sent to the mobile app.
- To keep Orbit and the website secure, detect misuse and fix problems, including using crash and error reports from the mobile app to keep it stable and reliable.
- To communicate with you about your account, your work, and your requests.
- To meet legal obligations and to protect our rights.
5. How access tokens are protected
- Meta access tokens are encrypted before they are stored, using the application's encryption key.
- Tokens are not shown in Orbit's screens, are not written into activity records or logs, and are not placed in web addresses.
- Tokens are sent only to Meta, over an encrypted (HTTPS) connection.
- When the Meta connection is disconnected in Orbit, or a Page stops being accessible, the stored tokens are removed.
- The same care applies to the mobile app: push notification tokens are encrypted before they are stored, mobile sign-in tokens are stored on our servers only in hashed form, and neither is shown in screens, written into logs or placed in web addresses.
6. Cookies
Our website and Orbit use only essential cookies: a session cookie that keeps a signed-in user signed in, and a security cookie that protects forms from forgery. They are needed for the application to work. We do not use advertising cookies or third-party analytics on this website. The mobile app does not use cookies.
7. Who we share information with
- Within Orbit: staff see information according to their role. A client user can see only their own client's work, never another client's.
- Meta and Google: information is exchanged with Meta when you connect or use the Meta integration, and with Google when Orbit reads the Drive folders and spreadsheet shared with us. Each of them handles that information under its own terms and privacy policy.
- Expo and Google (Firebase Cloud Messaging): to deliver approval notifications to the mobile app, the push token for your phone and the notification message are sent to the Expo push service, which passes them to Google's Firebase Cloud Messaging for delivery to your Android phone. They process this information under their own terms and privacy policies, and we do not send them anything else about you for the purpose of delivering notifications.
- Google (Firebase Crashlytics): in version 1.0.2 of the Android app and later, crash and error reports (described under Orbit mobile app above) are sent to Google's Firebase Crashlytics service. Google processes them as a service provider for us, under Google's Firebase terms and privacy policy, and for the purpose of providing the diagnostic service to us.
- Expo (app updates): in version 1.0.2 of the Android app and later, the app checks Expo's update service for updates, as described above.
- Service providers: companies that provide the infrastructure we rely on, such as hosting, database and email delivery, who process information on our behalf to run the service.
- Legal and safety: where the law requires it, or to protect rights, safety and security.
We do not sell personal information.
8. How long we keep information
We keep information for as long as it is needed to provide our services, to keep an accurate record of work and approvals, and to meet legal and accounting obligations. We do not apply a single fixed period to everything. Meta tokens are removed on disconnection as described above. A phone's notification registration is removed when you sign out, when your password is changed or your access ends, and when the phone's token becomes invalid; the short record of notifications sent is kept for a limited period (about 30 days) and then deleted. Crash and error reports held in Firebase Crashlytics are kept for the period set by Google under its Firebase terms and the retention that applies to our Firebase project; we do not control or promise a different period, and we do not copy these reports into Orbit. Page and Instagram identifiers and the client mapping may be kept as a historical record unless you ask us to delete them (see our Data Deletion page).
9. Security
We use access controls that separate staff from client users and limit what each role can see or do, encrypted connections, hashed passwords, encrypted integration secrets and an audit trail of important actions. No system is completely secure, so we cannot guarantee absolute security.
10. Your choices and rights
- You can ask us for access to the personal information we hold about you, or ask us to correct it.
- You can ask us to delete information, including your account and information held through the Meta integration or the mobile app. See Data Deletion for how.
- Crash and error reports are not linked to your name, email address or Orbit account, so we may not be able to tell which reports come from your phone. If you want us to act on diagnostic information, contact us with the details of your phone and the app version, and we will tell you what we can and cannot do. Uninstalling the app stops it sending further reports, and a new installation receives a new Firebase installation identifier.
- In the mobile app you can sign out at any time, which removes your phone's notification registration, and you can turn notifications off in your phone's settings.
- You can stop Orbit's access to your Meta account at any time by removing the app in your Facebook settings under Settings and privacy → Settings → Business integrations, or by asking us to disconnect it.
- You can ask questions or make a complaint by contacting us as set out below.
Some information has to be kept where the law requires it or where it is needed to protect legal rights, and we will tell you if that applies to your request.
11. Children
Our website and Orbit are for businesses and are not directed at children. We do not knowingly collect personal information from children.
12. Changes to this policy
We may update this policy as our services change. The date above shows when it was last revised. If a change is significant we will make that clear on this page.
13. Contact us
8Bit Technologies
BE 61, Salt Lake Rd, BE Block, Sector 1, Kolkata, Bidhannagar, West Bengal 700064
Email: [email protected]
Phone: 092331 11777