Makerkeep Privacy Policy
Effective October 19, 20261. Your shop, your information
Makerkeep is provided by NIXA Inc., a corporation incorporated in North Carolina, United States. This policy covers the Makerkeep website, app, accounts, optional cloud and shared-workspace services, and support. It does not govern unrelated NIXA products. For Makerkeep information, this product policy takes precedence over inconsistent general NIXA privacy wording.
We collect information necessary to provide the functions you choose, protect accounts and the service, answer requests, and meet legal obligations. We do not sell or rent your personal information or shop records, use them for targeted advertising, or disclose them for another organization's independent marketing. Makerkeep shows no advertisements on any plan, free or paid. We do not use your records to train AI models or supply another NIXA project. Necessary service-provider processing and the sharing you expressly choose are explained below.
2. Device storage and optional cloud protection
A Makerkeep account is required, including for Sketchbook (free) and the 14-day Studio trial. Creating an account does not itself upload your shop records. On Sketchbook your shop is kept on your device only. We record which of your devices holds it (its platform category and the hashed installation identifier described below), so your other signed-in devices know where it is; you can move it to another device at any time. On Studio, new shops are kept in your account's private cloud storage unless you untick that during setup, so your signed-in devices can use the same records; the complete saved shop is uploaded to your account. You can switch private cloud off in Backup & restore. With cloud storage off, your account-specific shop data is kept in this app installation or browser, and local business calculations do not send those records to NIXA. Staff and other users do not gain access to that private shop. Sharing with other people is a separate action through a shared workspace and invitations. First sign-in requires internet. The installed app can later open its previously saved account and shop offline. A signed access permit, account profile and necessary clock-check information are cached to verify offline use; iOS protects the service trust key and clock checkpoint in Keychain. Cached permits do not contain your readable password.
Saved changes synchronize while Makerkeep is open, online and authorized to save. Offline changes remain queued on your device until connectivity and access return. Unsaved form edits are not uploaded. Interrupted transfers and conflicting saved versions can require your review; a change has reached the cloud only when the app confirms synchronization. Sync keeps a current copy and is not a historical archive or a guarantee of independent disaster recovery. An accidental edit may synchronize too. The app also keeps automatic recovery points locally at startup and after saved changes, limited to 20 distinct copies, 32 MiB and 30 days per workspace; older copies are removed when that recovery storage is next accessed. These copies stay on the same device and cannot protect against its loss. Portable exports provide a separate copy under your control.
Supported business forms keep unfinished edits on the device as you work. These drafts do not create business transactions until you review and save them, and are not uploaded to NIXA. They are limited to 512 KiB per form, removed on save or discard, and expire after seven days when next accessed. Account passwords and provider tokens are excluded. Account deletion clears the initiating device's account-specific recovery points and drafts; if device storage cannot complete cleanup, the app may require you to remove the remaining local copies. Your operating system, browser or backup provider may keep app data under its own controls. NIXA cannot remotely erase exports you downloaded, copies someone else exported, or backups controlled by you or your device provider.
3. Account and cloud-service information
Account information includes your email address, display name, password verification hash when you use a password, and an optional profile image. We do not store readable passwords. Security and access records include account/session identifiers, session creation and activity times, a device or browser description, hashed session and recovery credentials, and account/workspace security events. To administer device limits, we keep a platform category and a hash of a random identifier created for the app installation or browser. We do not obtain a hardware serial number or advertising identifier, or create a device fingerprint. Reinstallation or cleared browser storage can change the identifier. Switching devices invalidates the prior online session for that category; an offline device learns about revocation when it reconnects. When you start a plan, Stripe, our payment processor, collects and stores your card details; Makerkeep never receives your full card number. We keep the Stripe customer and subscription identifiers, plan, status, trial and renewal dates, card brand and last four digits, and a record of the billing terms you agreed to and when, to administer your plan, meet tax and accounting duties and show you your billing. Stripe also processes your billing address to calculate tax and may use payment information to prevent fraud under its own privacy policy. If you subscribe in the iPhone app, Apple processes the payment. Apple gives us a signed record of the purchase: the product, dates, renewal status, storefront, price and currency, and a random purchase token we create for your account so a purchase can only unlock the account that made it. We do not receive your Apple Account details or payment method. We also record whether you have used your free trial, a trial extension or a welcome-back offer, so each is used once. Restoring shop records does not reset a trial or create paid access.
If you turn on two-step sign-in, we keep its secret encrypted and your recovery codes only as hashes. If you add a passkey, we keep its public key and identifier, never the private key, which stays on your device. If you allow notifications in the iPhone app, we keep that device's push token encrypted until you turn them off or sign out. Makerkeep staff can see account details needed to give support and run billing (name, email, sign-in methods, plan status, shop names and sizes), never the contents of your shops; every staff action is logged.
When you accept Makerkeep's terms, we keep the account identifier, accepted document version and acceptance date/time needed to document that agreement. These are account-service records, not advertising or behavioral analytics. They follow the account retention and deletion rules below, except for specific information a law requires us to retain.
A private cloud shop or shared shop stores the business records you choose to upload or enter, workspace and shop identifiers, revisions, member roles, invitation addresses, and optional shop logos. Business records may include sales and costs, cash balances, stock, production activity, product and material descriptions, plans, and notes. Free-text fields can contain personal information if you enter it; avoid buyer details, government identifiers, card numbers, bank credentials, health records, or other unnecessary sensitive information.
Support stores the subject, topic, message, replies, status, account identifier, and timestamps of a request you send, and any screenshots you choose to attach (up to 3 images per message; location and other photo metadata are removed). Basic app/browser/viewport diagnostics are attached only if you choose the diagnostic option shown before sending. A saved draft stays on your device until you send it. Closing a support request changes its status; it does not delete it. You may request its deletion.
Crash and performance reports. If the iPhone or iPad app crashes or freezes, it may send us a technical report (app version, iOS version, device model and where in the app the problem happened). These reports aren't linked to your account, don't include your shop's data, and are deleted after 90 days.
Getting-started steps. To learn whether Makerkeep is easy to start, we record the date an account first reaches a few steps: adding its first product, seeing its first profit figure, recording its first sale, using the Etsy X-ray, and coming back after its first week. We record only the step and its date, never what’s in your shop. We look at these steps in total, not to profile you, we don’t share them, and they’re deleted with your account.
Shop history. For cloud shops, we keep a 90-day history of changes: who made each change, when, on which kind of device, what changed, and earlier copies of the shop's data so the owner can restore it. The shop's owner and any co-owner can see this history, including teammates' names and changes, and can restore the shop to an earlier copy; teammates are told when their changes are undone. History older than 90 days is deleted automatically. Deleting a shop deletes its history; deleting your account removes your name from changes you made in other people's shops, which then show as "a former teammate".
If you choose an available Google or Apple sign-in option, we receive the provider's stable account identifier, verified email address, and any basic display name you authorize. We use this information to create your account or connect the provider to an account you have confirmed. A matching email address alone does not link accounts. Sign-in options vary by platform; an unavailable option is not required to use email/password access. Apple private relay addresses are supported when Apple sign-in is offered. We do not request your contacts, calendar, shop accounts, advertising activity or payment information from sign-in providers, and do not send them your shop records or plans.
Short-lived sign-in request and completion records are encrypted on the server to protect state, nonce and verification information. Requests expire after ten minutes and completion proofs after five minutes, and are removed during routine cleanup. We do not persist Google access, refresh or identity tokens for ongoing access to Google services. When Apple sign-in is offered and connected, encrypted Apple verification/revocation tokens are retained for that connection. Disconnecting a method or deleting the account removes the related Makerkeep identity and retained token records. If automatic Apple revocation cannot finish, Makerkeep still removes the applicable account data and tells you to remove the remaining authorization in your Apple Account settings.
4. Files, photos, and optional connections
Sales files are parsed on your device. Makerkeep saves the supported financial fields and product/order references needed for reporting and reconciliation, rather than a copy of the entire uploaded file. Supported importers exclude buyer names, buyer email addresses, and delivery addresses. Review free-text product descriptions before importing. Workspace backups contain your entered business data and should be kept private. A .makerkeep backup contains the saved workspace and integrity metadata, not account passwords, sign-in access, staff memberships, connection credentials, or support threads. A backup saved with Download a backup is encrypted with a password you choose (AES-256-GCM, with a key derived from the password using PBKDF2-SHA256) and can be opened only by restoring it in Makerkeep with that password. NIXA never receives or stores that password and cannot recover it or open the file without it; if you lose it, the backup cannot be opened. Older unencrypted .makerkeep files can still be restored. Emergency downloads of an unsaved change, recovery copies made when something fails to save, and the CSV data export are not encrypted; anyone who has one of those files can read it, so keep them private. Restore validates the file, previews merge or replacement, and does not grant account or subscription access. A local copy made before restoration can be exported for recovery and is cleared with this account’s device data.
A photo or camera choice is used only when you explicitly add a profile picture or shop logo. The app uses the selected image, not a scan of your photo library. File selection, clipboard actions, and export/share actions happen when you invoke them. Makerkeep does not request your contacts, precise location, microphone recordings, or background browsing activity.
Connections to sales platforms are optional and do not make Makerkeep exclusive to any platform. If a supported connection is enabled and you authorize it, the service stores authorization credentials and the minimum financial/product references needed to retrieve and review sales. Provider access tokens are encrypted on the server. Disconnecting removes the saved connection credentials and its unaccepted import inbox; previously accepted shop records remain until you delete them or the workspace. You may also revoke access with the provider. The provider processes information under its own policy when you authorize or use its service.
5. Why information is used
We use account information to authenticate you, recover access, and administer access and the cloud or shared features you request. We use workspace records to synchronize your shop, calculate the estimates and reports you ask for, and apply access rules. We use support information to answer your request and diagnose the reported issue. Necessary security information protects accounts and the service. We may send essential account, support, security, or legal notices; these are not advertisements. If your plan or trial ends, we may send you one email with a welcome-back offer. It is the only promotional email we send. It identifies NIXA Inc. as the sender and includes our mailing address and an unsubscribe link; unsubscribing takes effect promptly and always within 10 business days. You can also turn it off in Notifications under Offers. Turning it off does not stop essential notices.
Makerkeep does not use an advertising SDK, session replay, cross-app advertising tracking, or behavioral marketing analytics. The getting-started steps described above are counted in total to improve the app, not to market to you. On the public makerkeep.app website (not the app), Cloudflare Web Analytics counts page visits without cookies, using the page address, the referring site, the browser type and an approximate country; it doesn’t identify you or follow you to other sites. Essential cookies and local storage maintain sign-in, preferences, drafts and your shop data. We do not use advertising cookies. Hosting and network providers process necessary traffic/security information and connectivity diagnostics as described below. Your own marketing-cost entries are business records, not advertisements delivered by Makerkeep.
6. Who can access information
Members you invite can read the shared shop's business and financial data. The owner, who pays for the shop, chooses what each member may change (Plan, Make, Sell, Money, or Manager for all of these) and manages membership and deletion. Hiding the Money pages from a member limits what the app shows; it does not make the shop's records unreadable to that member. Your display name and optional avatar identify you to members; workspace owners can see member email addresses. Share only with people who should have that access. Members may export records, and removing their access cannot recall copies already exported.
Authorized NIXA personnel access information only when needed to operate or secure Makerkeep, respond to your request, or meet a legal obligation. We use OVHcloud for the hosted service, Cloudflare for domain, network delivery, HTTPS and security services, Stripe for payments, billing and tax calculation on the web, Apple for purchases made in the iPhone app, and Resend to send account emails. Resend receives the recipient address and the message, and tells us whether it was delivered, bounced or marked as spam; we stop emailing an address that keeps bouncing. These providers necessarily process information involved in hosting and delivering requests, including network addresses and request details and, where relevant, the data carried by a request. Communication or support providers may also process information you send to NIXA. We limit service-provider access and purposes to the service they provide and require appropriate protection of Makerkeep information. This processing does not authorize advertising use, sale of your records, or training AI models on them.
Cloudflare may receive browser network-error reports used to diagnose connectivity problems. They can include the requested address, timing, protocol, error details and network information. Cloudflare can derive a country or network area from an IP address for this operational processing. Makerkeep does not request GPS location or build an advertising location profile. These reports are infrastructure diagnostics, not a recording of your screen or a replay of your actions. Cloudflare processes its own network/security information under its applicable privacy terms; contact NIXA for information about the providers used for your service and their processing.
We disclose information when you direct us to do so or when legally required. We assess legal requests and limit disclosure to the necessary information, providing notice when permitted by law. We do not use a possible future dispute, product research or commercial convenience as a reason to retain deleted shop records. A change in company ownership does not authorize a use of your information inconsistent with this policy; if a legal restructuring requires transfer of service records, these protections and applicable privacy obligations continue to apply.
Apple and Google process their own sign-in and consent flows under their own privacy terms when you choose those methods. Makerkeep sends the minimal sign-in request and public application/return address needed for that choice; it does not send your shop records, sales, materials or production plans to the sign-in provider.
7. Retention and deletion
Account, access and security records are used while your account remains open; cloud/workspace records are kept to provide the storage and sharing you select, and support records to handle your request. We limit retention to those purposes and legal requirements. Closing a support conversation does not itself erase its messages; you may ask us to delete them. If you joined someone else's shop as a teammate and your access ends because their plan got smaller or ended, and your account has nothing else (no shop, plan or team of its own), we close it and delete it 30 days later unless you sign in and choose to keep it; we tell you by email first. You can delete your account in Settings → Profile → Delete account. Your password or an available connected-provider verification and an explicit confirmation protect against accidental deletion. A successful server confirmation removes the account record, profile, sessions, recovery codes, memberships, your support requests and associated invitation/security records from the active service. Your private cloud shop is removed with the account and does not require transferring ownership.
If you are the only owner of a shared workspace, you may transfer ownership first or expressly include deletion of that workspace when deleting your account. Workspace deletion removes its server business records, memberships, invitations, workspace activity, and connected-provider credentials and inbox. This affects every member and cannot be undone. A workspace with another owner remains that business's workspace; deleting your membership does not instruct us to erase records the other owner continues to manage. Your account/profile and identifying account history are removed. If personal information about you remains in a shop's notes or records, request its removal through the privacy contact; we will assess the request with the responsible business and apply the law, rather than retain it automatically.
Deletion removes an account rather than merely deactivating it. Once identity and the requested scope are confirmed, we remove data from the active service and address any remaining NIXA-controlled or service-provider copies without undue delay, subject to applicable legal deadlines and the technical steps necessary to finish erasure. We do not keep deleted shop or personal records for advertising, analytics, training, indefinite troubleshooting or possible future commercial use. If a law or binding order requires retention, we retain only the specific information necessary for that obligation, restrict its access and use to the legal purpose, and delete it when the obligation ends. Legally required incident records or records needed to exercise a statutory privacy right may be such limited exceptions; they are not permission to retain an entire deleted workspace. Where permitted, we explain what must remain, why and for how long.
Accounts closed by Makerkeep. If we close an account (for example, for a breach of the Terms), access stops right away: sign-in is refused, card subscriptions billed by Makerkeep are canceled, and shared shops it owns become read-only for their members. So that a mistaken closure can be undone, we keep the account and its shops unchanged for up to 30 days. If it isn't restored in that time, it's deleted the same way as a deletion you request in Settings → Profile, and service backups age out as described below. This is separate from deleting your own account, which takes effect immediately. App Store subscriptions are billed by Apple; cancel them in your Apple account settings.
Service backups: to recover from an outage, we keep encrypted copies of the service database for up to 30 days with secure third-party cloud providers. Deleted accounts and shops leave these backups as the copies age out, within about 30 days. Backups are used only to restore the service. If we ever restore one, we delete again anything that had already been deleted.
On successful account deletion, the app clears the initiating device's account-specific shop data, cloud/shared caches, pending changes, recovery copies and support drafts. Other offline devices, user-controlled backups and exports may retain copies until you remove them. If your device cannot finish local cleanup, follow the app's notice and remove remaining app/browser data. Turning cloud storage off requires account confirmation, preserves the latest synchronized device copy and removes the private cloud copy from the server; other devices then stop syncing it. Export records you need before deletion or replacement. If you separately purchased an App Store subscription, deleting your Makerkeep account does not cancel Apple's billing; manage that purchase through Apple subscription settings.
8. Security and incident response
We use HTTPS for account/workspace transfers, password hashing, session protection, access controls and restricted server database files. Sign-in proof material and retained connected-provider tokens are encrypted. Shop records are not end-to-end encrypted, and the complete service database is not encrypted at rest by Makerkeep. NIXA and necessary service providers can access records when needed to provide, secure or support the chosen service. A backup saved with Download a backup is encrypted with your password; the CSV data export, emergency downloads of unsaved changes and recovery copies made when saving fails are not. Your device's protection, account credentials and invited members also affect confidentiality. No system can guarantee absolute security.
If a privacy or security incident affects your information, we investigate, contain it, and provide notices to affected individuals and authorities as required by applicable law. Legally required incident records are limited to their required purpose and retention period. Contact us promptly if you suspect unauthorized access; do not send passwords or recovery codes in a support message.
9. Your choices, access, and privacy rights
An account is required for Sketchbook, trial and paid access. Private cloud storage (a Studio feature, on by default for new Studio shops, and you can switch it off), optional photos, diagnostics, workspace sharing, and sales-platform connections are separate choices. You can correct profile and workspace records, download a password-protected backup file, export all your saved records, restore validated files, disconnect providers, remove members where authorized, and delete your account or workspace. Withdrawing a choice may stop the feature that needs it; it does not authorize a new use of your information.
NIXA is responsible for handling Makerkeep privacy requests. Email [email protected] with the subject 'Makerkeep privacy' to request access, correction, a portable copy where available, deletion, withdrawal of an optional choice, details of service providers/processing locations, or review of a privacy concern. You do not need to ask us for a portable copy of your records: Export my data in the app gives you one at any time, on every plan, as CSV spreadsheet files of all your saved records, including Studio records kept after a plan ends. This contact is available without an account, including if you cannot sign in. We use proportionate information to verify identity and locate the relevant records; do not send passwords, recovery codes or unnecessary identity documents in an initial message. We can help you make an understandable request or access information in an appropriate format.
We respond within the deadlines required by the law applicable to your request. Where PIPEDA applies, an access request normally receives a substantive response within 30 calendar days; any legally permitted extension is explained within the original deadline, including its reason and your complaint rights. If access must be limited to protect another person's information or meet another legal requirement, we explain the permitted reason and available recourse. We do not penalize you for exercising privacy rights. US state and Canadian federal/provincial rights vary, and this policy does not reduce them. Canadians can contact the Office of the Privacy Commissioner of Canada or the applicable provincial regulator, including Québec's Commission d'accès à l'information.
10. United States and Canada
NIXA is based in the United States. The hosted service and its network/support providers may process information outside your state, province or country, including in the United States. Foreign laws may permit government access to information processed there. We remain responsible for information processed on our behalf and require appropriate safeguards for those services. We do not promise storage only in Canada or a particular province. Ask the privacy contact for current provider and processing-location information. Changes to processing that materially affect your choices are communicated as described below.
Makerkeep's calculations compare your entered business assumptions. They do not automatically make legally significant decisions about you, approve credit, or set your prices. You decide whether and how to act on an estimate. We do not profile users for advertising.
11. Age, changes, and contact
Makerkeep is intended for adults who can enter a binding business-service agreement, and is not directed to children. We do not knowingly collect children's personal information. If a child has provided information, contact us so we can remove it as appropriate.
We update the version and effective date when this policy changes. Material changes are communicated in the app or by an essential account notice before taking effect. A broader use of previously supplied information requires a valid legal basis and any required fresh permission; continuing to use the app does not silently authorize unrelated advertising, sale, or training.
Provider: NIXA Inc., incorporated in North Carolina, United States. Privacy and support contact: [email protected]. Company website: https://nixainc.com. This product policy applies equally to Sketchbook, free trials and paid Studio subscriptions.
App Store license: Apple Standard EULA.