There are advantagas and disadvantates to using Auto-incrementing integer vs GUID. Its difficult to advise based on your description. You can go with either, I've used both. For small DB implementations, with regard to peformance, its negligible, but that's a vague statment on my part again as other factors can affect performance (specifically storage design). Will the DB be mainly experiencing reads or writes?
Here's some pros and cons to GUID:
The GUID will be/should be unique within the DB, even accross different servers.
The GUID is more object ID–like datatype
You can generate GUIDs anywhere, even in the business layer outside of your DB. That's good for some scenarios.
If you are replicating your DB, some scenarios require GUID.
A GUID will not mean anything to the users. Increase security through obscurity.
GUID is larger than INT. How will this affect indexing?
Difficult to debug, think about a querystring usch as userid='BAE7DF4-DDF-3RG-5TY3E3RF456AS10')
For best performance, GUIDs may not be the best choice depending on the overall design. Do some testing and research on your own.
If you're in one of those predicaments where cls.__private attributes just aren't enough since they can easily be accessed through inst._cls__private, and you need something a little more secure, here's ...