We answer every message within one business day.
Email support@digitalsummitlabs.com
Tell us what you were fixing and what happened. If something went wrong in the app, the make and model of your phone helps.
Want to delete your account? You can do it yourself in Profile, or follow the steps on this page.
Your first repair is free. After that you can buy repairs outright — one for $7.99, three for $19.99, or ten for $54.99, and credits never expire — or take a TinkrAI Pro plan: Monthly at $24.99 for 5 repairs each month, or Annual at $199.99 for 40 repairs a year, up to 5 in any month. Pro members pay less for extra repairs. The two plans renew automatically until you cancel them in your Apple Account settings or Google Play Subscriptions. Nothing is charged unless you choose it.
No. You can use Tinkr without signing in. Signing in with Apple, Google or an email address keeps your repair history if you change phones.
It is usually on a sticker or plate: inside the door frame on appliances, on the back or underside of electronics, and on the door jamb or firewall on vehicles. If you cannot find it, tell Tinkr and it will work from the symptoms instead.
Most answers come back in under a minute. A full repair plan takes longer because Tinkr is working through the whole procedure, the parts and the safety checks at once. Leave the screen open while it does.
No, and this is deliberate. Tinkr stops when a repair involves a hazard it cannot verify from a photo — mains electricity, gas, stored energy, refrigerant, airbags, or a load that could fall. It will not help defeat a safety interlock or guard under any circumstances.
Tell us at support@digitalsummitlabs.com and include what it actually turned out to be. There is also a report option inside each repair. Reports go straight into how the next version is tuned.
Open Profile, then Delete account and all data. It removes your account, every repair, and all photos, video and audio you uploaded, immediately and permanently.
Update to the latest version from the App Store. Builds before 1.0 could lose the signed-in session on launch, which looked like being signed out.