This policy explains what personal data Pulsar handles, why, for how long, and the choices you have. It covers this website, the dashboard, the API, the CLI and the React Native SDK.
Who we are
Pulsar is an over-the-air update service for React Native apps, operated by Novacraft Engineering ("we", "us"). You can reach us about anything in this policy at admin@novacraft.africa.
Two kinds of data, two roles
Your account data. When you or your team use Pulsar, we decide how that data is used, so we are its controller.
Telemetry from your users' devices. When you put the Pulsar SDK in your app, the SDK reports update activity from your users' devices. You decide to collect it and what it's for, so you are the controller and we process it on your behalf. Our Data Processing Addendum covers that processing.
What we collect about account users
Account details: name, email address, a hash of your password (never the password itself), two-factor authentication settings, how you heard about us if you tell us, and the page, referring site and campaign tags of your first visit.
Organization details: organization and app names, logos you upload, team members, roles and invitations.
Sign-in providers: if you sign in through a third-party sign-in provider or your company's single sign-on, we receive the account identifier, name and email that provider shares. If you connect a code repository, we store the access token needed to read it.
Billing details: your plan, billing interval, currency and payment references. Card and bank details are entered on our payment processor's pages and never reach our servers.
Security and activity records: an audit log of actions taken in your organization (who did what, and when), short-lived sign-in rate-limit counters keyed by IP address or email, a log of sign-in attempts with the IP address, approximate location and browser so you can spot sign-ins that weren't you, and trusted-browser records if you choose to skip two-factor prompts on a browser.
What you upload: release bundles, source maps, code-signing keys (stored encrypted), webhook addresses and CI tokens (stored hashed).
Support and email: messages you send us, and copies of the transactional emails we send you, which we keep as records.
What the SDK collects from app users' devices
When an app built with the Pulsar SDK checks for or installs an update, it sends:
A random install identifier that the SDK generates. It is not an advertising ID and is not linked to the person's identity by us.
The app's store version and release label, the deployment, and whether an update downloaded, installed or failed.
Device model, brand, operating system and its version.
For a failed update, the error message and stack trace the app recorded, so the developer can fix it.
A user identifier, only if the app developer chooses to set one for release targeting.
The device's IP address, which we use to deliver the update and protect the service. For usage counting we keep a one-way hash of it, not the address itself.
An approximate location (country, region and city, rounded to about 10 km) worked out from the IP address, so the developer can see where their active devices are. We never ask the device for its GPS location.
We do not collect names, contacts, precise location, photos or any content from inside the app. Developers must not send sensitive personal data through the user identifier field.
How we use data
To run the service: deliver updates, apply rollouts and targeting, show adoption and health dashboards, and roll back failing releases.
To keep accounts and the platform secure: authentication, two-factor checks, rate limiting, abuse prevention and audit trails.
To bill you and count usage against your plan.
To send service email: verification codes, invitations, release and failure alerts, and weekly digests if you turn them on.
To support you and improve the product, using aggregated statistics wherever we can.
We do not sell personal data, and we do not use it for advertising.
Legal bases
Where data protection laws require a legal basis for processing, we rely on:
Contract: to provide the service you signed up for.
Legitimate interests: to secure the platform, prevent fraud and improve the product, balanced against your rights.
Consent: for optional things such as weekly digest emails. You can withdraw it at any time.
Legal obligation: to keep billing records and respond to lawful requests.
Who we share data with
Service providers that help us run Pulsar, such as hosting, email delivery and payment processing. They may only use the data to provide their service to us, under contracts that require them to protect it.
Sign-in and identity providers, when you choose to sign in or connect with them.
Members of your organization, who see the apps, releases and activity they have access to.
Authorities, when the law requires it, or to protect the rights and safety of our users and the public.
A buyer or successor, if the business is reorganized or sold, under the same protections described here.
International transfers
We and our service providers may process data in countries other than the one you live in. When data moves between countries, we rely on recognized safeguards such as standard contractual clauses.
How long we keep data
Device-level telemetry: 30 days by default. Each app owner can set this from 7 to 365 days. Daily totals with no device identifiers are kept for the life of the app.
Store-build device records: removed on the same schedule as device telemetry.
Live activity (approximate location of active devices): 48 hours.
Account and organization data: for as long as the account is active, then deleted within 30 days of a deletion request, except what we must keep by law.
Audit log: for the life of the organization, so admins can review past changes.
Billing records: for as long as tax and accounting law requires.
Traffic is encrypted in transit. Passwords are hashed, signing keys are encrypted, and tokens are stored as hashes. We offer two-factor authentication and single sign-on, enforce role-based access inside organizations, rate-limit sign-in attempts and record administrative actions in an audit log. No system is perfectly secure, so please report anything suspicious to admin@novacraft.africa.
Your rights
Depending on where you live, you can ask to access, correct, delete or export your personal data, object to or restrict some processing, and withdraw consent. Email admin@novacraft.africa and we will respond within 30 days. You can also complain to the data protection authority where you live.
If you are a user of an app that uses Pulsar, contact that app's developer first, since they control your data. Developers can delete a user's telemetry by user ID from the dashboard, and we will help them handle your request.
Children
Pulsar accounts are for developers and businesses, not children. You must be at least 16 to create an account.
Cookies
We use a small number of cookies and browser storage items to keep you signed in and remember your settings. We count page visits with Cloudflare Web Analytics, which sets no cookies and does not follow you to other sites; Cloudflare receives the page address, the referring site, your browser details and your IP address to do this. We do not use advertising trackers. Our Cookie Policy lists each cookie and storage item.
Changes to this policy
If we make material changes we will update the date above and, where the change affects you, tell you by email or in the dashboard before it takes effect.