We know that privacy can be an issue when dealing with stack traces. The stack trace tells information about the technology stack you use, the internal architecture of your modules, and the message can contain schema of your database tables, user names or worse. If your business consider these data sensitive, Samebug is ready to handle them respectively.
For every content you create on Samebug (at the moment there are crashes and solutions), you can specify three visibility level: Public, Searchable and Private.
At the moment there are two kind of data you create on Samebug: crashes and solutions.
Crashes are the stack trace searches you paste on the site or you submit from the IDE plugins. If your search is Public, everybody will be able to check the stack trace of the crash, find you as a bugmate for similar stack traces and your experience with the related libraries will be displayed on your profile. On Private level, none of these will be visible for unprivileged users, while on Searchable your stack trace will be private, but the rest of the data is public.
Solutions are the tips you can attach to stack traces. If your solution is Public, everybody will be able to check the stack trace you wrote the tip for, the tip itself and your experience with the related libraries will be displayed on your profile. On Private level, none of these will be visible for unprivileged users, while on Searchable your stack trace will be private, but your tip and your experience is public.
Any content you create will inherit the visibility of the workspace where it was created. Changing the visibility of a single content is not possible currently; in case you want to do this please contact us
Chosing which visibility level you should use depends on your situation. The more open you are, the more you give to the Community, and the less compensation we ask.